News for hackers. Stuff that matters.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by skizm on Sunday September 08, 2019 @01:45PM (#20912025)
What does "promoted" look like for an software engineer at large tech companies? In my company you're either an individual contributor or tech lead. There aren't really any other rungs on the ladder without going to manager.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by bt848 on Sunday September 08, 2019 @01:56PM (#20912111)
At Google there’s an IC ladder from level 3 (new grads) to 11 (Jeff and Sanjay). Basically it’s a pay scale. Half of engineers are below 5, and 90% are below 6.

Edit: pretty sure I was off by one originally. But you get the idea: it’s a triangular organization with a lot of people at the base.

Re:Ask HN: What Have You Learned at Google as a Software Eng... by zuhayeer on Sunday September 08, 2019 @02:10PM (#20912224)
For pay ranges check out some charts we’ve compiled at http://levels.fyi/charts.html
Re:Ask HN: What Have You Learned at Google as a Software Eng... by generatorguy on Sunday September 08, 2019 @02:48PM (#20912519)
I decided to focus on power engineering instead of software in the mid 2000s since I thought a lot of software jobs would be offshored. Big mistake in terms of compensation!!
Re:Ask HN: What Have You Learned at Google as a Software Eng... by skizm on Sunday September 08, 2019 @01:58PM (#20912135)
Ah, okay. Pay scale, got it. Yea we have similar. Just no actual titles.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by dvirsky on Sunday September 08, 2019 @02:05PM (#20912193)
It's not just about pay, it's also about scope and expectations.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by bt848 on Sunday September 08, 2019 @02:28PM (#20912366)
Sort of. I didn’t mention it because level doesn’t really limit your scope. If you have a way to make a big impact nobody is going to tell you to not do it because you’re too junior. It’s just that the higher levels are expected to operate at company-wide scope all the time.

You can hide your level such that other people don’t see it, which is another difference between Google and my current company where people introduce each other by their titles, which makes me want to quit every time. Nobody at Google has ever said “And now I’d like to turn the meeting over to Principal Engineer Jane Doe”. Most people don’t mention it.

Re:Ask HN: What Have You Learned at Google as a Software Eng... by dvirsky on Sunday September 08, 2019 @05:13PM (#20913452)
I've heard the phrase "well, a T7 said otherwise, who am I to argue" and similar from people.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by bt848 on Sunday September 08, 2019 @06:44PM (#20913864)
It’s up to each individual to make the most of an environment where the utterances of senior engineers are just advice. You don’t need their permission.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by dvirsky on Monday September 09, 2019 @06:45AM (#20916929)
Of course not, I'm just saying it _is_ part of the current culture to assign hierarchy to levels, probably more so with younger/more junior people. Hierarchy tends to look flat looking down.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by ithkuil on Sunday September 08, 2019 @01:58PM (#20912132)
Which sucks. Having a technical ladder is important to retain talent and ensure that you maximize the skills your talent pool has.

Pure engineering skills (even the thought leadership aspect of it) doesn't directly translate in management skills and often people get "rewarded" by promoting them to a position where they can no longer use the very skills they have been promoted for.

Related concept / good read: https://en.m.wikipedia.org/wiki/Peter_principle

Re:Ask HN: What Have You Learned at Google as a Software Eng... by joshuamorton on Sunday September 08, 2019 @02:30PM (#20912382)
The engineering ladder doesn't ever become a management ladder. You can transfer, but you don't have to.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by ithkuil on Sunday September 08, 2019 @03:36PM (#20912852)
I was referring to those companies where the only opportunity to e.g. make more money was to go to management.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by mytailorisrich on Sunday September 08, 2019 @02:10PM (#20912231)
It's very common to have a range of titles like: engineer, senior engineer, principal engineer, senior principal engineer, technical director.

This obviously goes hand in hand with higher pay and increased role and input. In general you might lead others from principal engineer upwards.

Re:Ask HN: What Have You Learned at Google as a Software Eng... by bitadder on Sunday September 08, 2019 @02:02PM (#20912167)
Check out levels.fyi to get an idea per company. At Google, we have "standardized" levels starting at L3 to L10, each with their own compensation range. Google allows you to climb this ladder while remaining an IC. Going to manager has a different progression and it's not an expectation.
Re:Ask HN: What Have You Learned at Google as a Software Eng... by aalhour on Sunday September 08, 2019 @03:29PM (#20912794)
How easy is it to transition into a manager if you're an IC?
Re:Ask HN: What Have You Learned at Google as a Software Eng... by verma7 on Sunday September 08, 2019 @04:03PM (#20913039)
It's easy to transfer to transition to the manager ladder by becoming a TLM (Tech Lead Manager) once you are L5 or higher.