38 ms·
Stories of reaching Staff-plus engineering roles
- kh_hk 5y agoI found most times being offered a staff engineer position feels more like companies just massaging our egos to either hire or increase eng. retention. Title means nothing if everyone gets it. That, or impostor syndrome.
- lousyd 5y agoTitles are overrated anyway. Not useless, just overrated.
- walterbell 5y agohttps://twitter.com/zainrzv/status/1502550200396750851 https://twitter.com/zainrzv/status/1502550200396750851 Junior engineer: Take this tightly defined feature & build it Mid-level engineer: Take this vaguely defined feature & build it Senior engineer: Take this known problem & figure out how to solve it Staff engineer: Take this goal & find the problems we should be solving
- beckingz 5y agoSo staff engineer is Senior + Product Manager effectively?
- menzoic 5y agoThe technical complexity of your past projects are also considered. So it's not just PM skills, there's also a higher technical bar.
- walterbell 5y agohttps://twitter.com/ryaneccles/status/1502707481327255553 https://twitter.com/ryaneccles/status/1502707481327255553 Senior staff engineer: Define what good goals entail Distinguished engineer: Please don’t work for our competitors
- als0 5y agoFellow: Do what you want
- herodoturtle 5y agoBut please wear our t-shirts.
- asplake 5y agoThere is a parallel progression for product people also. Part of of it involves embracing this engineering one in others. And vice versa, in partnership.
- PebblesHD 5y agoHaving been on a pathway to this level of engineering for a few years at my previous company, I was very disappointed when new management came in and effectively said ‘we’ve heard great things about what you’re doing but we need you to start from scratch and impress us’, to the point that last week I left the company I’d been a part of for over 7 years over the effective reset of all progress towards that next level. No real point to my comment, just a message that if you are just using these roles as a retention strategy for your best engineers, make sure to follow through with it or you may find that your best talent actually leaves over how its managed… As an aside, I’m really liking the team at my new role as well as the increased breadth of the role to start with.
- juancn 5y agoYeah, sometimes it happens. Tech leadership roles are hard to grok to some managers. Sadly in many cases they notice the vacuum left behind instead of the work put in. On management change, you need to re-assert your value, it shouldn't be super difficult, but sometimes it's easier to just leave.
- staff357 5y agoAs a "staff-plus" engineer at one of the big tech companies, I find that much of this material is simply not true in practice. Staff promotions are of course given to some people with a good mastery of soft leadership skills, technical thought leadership and related qualities. They are also given out for a number of other reasons. For example, when someone is perceived as a flight risk, because it makes their manager look good to promote their team, because someone has been given a lot of responsibility, whether or not they're good at handling it, because it's good for team morale to show that promotion is achievable, or because it can make a headache go away for the manager. These reasons are all perfectly valid. But let's not overdo the Jedi-like "staff-plus" engineer trope.
- chrisseaton 5y agoYeah I don’t really get why some people in the community have decided that their staff titles mean they’re some kind of warrior monk caste, with these new conferences, books, websites, threads. It’s just another regular step on the ladder you make by doing a reasonably good job and growing regular skills as normal. I don’t think it requires this level of mythology or introspection.
- maybestaff 5y agoAbsolutely — the sudden lionization of the term "staff" seems to be a combination of a personal marketing push (from those selling the shovels) combined with being a useful recruiting strategy. At one big tech company I worked at, it was never mentioned even once for years and years, and then introduced very suddenly. All existing engineers were grouped into staff versus non-staff based on their existing level, and from then on it was used for recruiting purposes — a superior title to sweeten the offer pot for experienced engineers in a competitive talent market. I'm personally familiar with some of the people being interviewed on this list and they're fine engineers, but certainly no better than many non-staff engineers at their same companies. And to imply that they're some kind of rare, exotic special species that's totally apart from their non-staff counterparts is in total honesty, just weird. Nearest I can tell, the term "staff engineer" was an unusual one in use at certain shops, and was popularized big time around 2020. I've kept every recruiter email I've ever gotten since 2018. Prior to 2020, the term "staff" was mentioned in exactly two of them. Starting around Feb 2020, it's now mentioned in 20+ emails a year. Before it, we just used other terms like "principal" instead.
- misnome 5y agoThis sounds interesting, and something that apparently doesn't exist at my current company (Engineer, Senior Engineer, otherwise it's only management beyond that point). But am I the only one disappointed that as a book it's only available in paperback? The hardback of "An Elegant Puzzle" is _beautiful_ in both binding and print quality, it wouldn't be a hard decision to spend extra for this one.
- thex10 5y agoGood timing as I contemplate whether I want to go the Engineering manager vs. Individual contributor route. Being at the Senior engineer level now, I find this resource a nice counterbalance against the abundance of existing material aimed at engineering management and the vast ocean of material for Junior engineers.
- xcambar 5y agoI don't think it's a definitive choice. I've jumped from one to the other and vice versa based on opportunities and contexts, and it continues to serve me well. Really, it is only 2 different ways to contribute to a product and engage in a team. If you can be good at both, why force a career-long choice?
- Rafert 5y agohttps://charity.wtf/2017/05/11/the-engineer-manager-pendulum/ https://charity.wtf/2017/05/11/the-engineer-manager-pendulum... is a great read on this.
- juancn 5y agoI went the IC route (Sr. Principal or an IC7). It's difficult to get there but rewarding. In either route, you're still a leader. Managers have formal power, and deal with a lot of process (budgets, pay, promotions, etc.). Tech leads are influencers, we focus a lot more on technology and growth of the team in a different way. You forgo all the messy (boring for me) details of project management, and focus more on the technology and getting the right people to move projects forward, but this requires persuasion. There's not one way to do this job, you have to find your own. The hardest part is probably that of picking the right thing to delegate, to maximize growth and project success. There's some overlap with managers especially as you climb the ladder and your focus is more strategic than tactical.
- seanhunter 5y agoThese role level names are just nonsense of the highest order (Staff, Senior, L2, etc). People are given titles to fixate on as a substitute for things which actually matter: 1. The opportunity to have meaningful impact 2. Important, fulfilling work 3. Recognition of value (including good comp but not just that) etc
- kyawzazaw 5y agoMatters for the next job-jumping, compensation issues and honestly, even respect one gathers
- temporalparts 5y agoI think the recent "Staff-plus" fascination comes from the extreme dilution these past years of the "Senior" engineering role. Meaningless title inflation is real.
- jensensbutton 5y agoYup. When people are "senior" engineers with less than 5 years experience they need to have something to look toward.
- humanrebar 5y agoI also need to be able to quickly communicate with recruiters and managers which roles I would be a good fit for.
- throwaway984393 5y agoMy favorite is the kid on their first job out of college who after 3 years is now "Senior". Seen too many of these to be funny. I worry about hiring.
- gedy 5y agoThat was like the majority of my last company, ha.
- jakear 5y agoTo be fair, a kid after three years of high school is "senior". As is a kid after 3 years of college. Perhaps your word2vec("senior") is what needs recalibrating.
- ghiculescu 5y agoNot really, senior is meant to imply you are in the late stages of your career (or school or college or whatever) and have some wisdom to share. It’s reasonable to question if you can get that in a career - which could last 40 years! - when you are 3 years in.
- coldcode 5y agoMy last job before retiring last year there were virtually zero promotions in the greater department during my nearly six years there, besides a manager and a director who got multiple promotions. I had the same title (lead) I started with, yet my team and the greater department had high visibility in the (not FAANG but similar sized) company and was tasked with complex projects that affected company revenue. Other than one person made architect, the highest title any programmer had was lead despite there being several dozen employee programmers and nearly 100 contractors. The best improvement in status was a few contractors being offered employee. So while the work might meet the definition of whatever staff is (one of my responsibilities was being in charge of code that made 9 figures a year), and there being 3 levels of programmer titles above lead, no one ever was promoted any higher. Sometimes the work and the title do not match, if the company or department is uninterested in rewarding people with fancier titles. But I knew another org far removed from ours where the manager was a senior director and all of his (half dozen) team had the top programmer titles, yet did not do anything different than we did, and none of it was revenue related.
- pm90 5y agoI joined a company that IPOd somewhat recently and recruits lots of folks from Big Tech (esp Google it seems). Literally everything is driven by promotions and “expectations for your level”. I actually don’t mind having explicit minimum expectations for your job but when that’s all anyone cares about it becomes really dispiriting.
- newaccount2021 5y ago
- booleandilemma 5y agoI’ve met “staff” engineers who were just above “junior” at best, and architects who couldn’t actually write code but man, could they talk your ear off about design patterns that any good programmer should know anyway. Often titles are a reflection of who’s been at the company the longest or who toots their own horn the most. I have no faith in titles, they’re mostly meaningless.
- humanrebar 5y agoAgreed about horn tooting design astronauts. There's a flip side to consider, though. I've seen brilliant people waste years of their energy and talent on technology ideas that go nowhere due to a lack of ability to ship to a community and gain mindshare among relevant technologists. Folks should dismiss vanity and puffery, but broadcasting opportunities and successes (and interesting challenges that need solutions, even) is undervalued among certain engineers. And it's a critical part of "shipping" for certain kinds of projects.
- hiptobecubic 5y agoI think this is probably a small-company problem. I've literally never met a staff engineer at Google that wasn't clearly better than the average Senior.
- indymike 5y agoThis one is cultural, and a meritocracy is one kind of culture.
- aix1 5y agoI don't know how typical Google is, but it expressly tries to maintain a consistent bar for a given ladder/level[*] and L5 -> L6 SWE promos are pretty tough. It's often said that L6 SWE is a different job and not just L5++, and I think there's a lot of truth in that. [*] Consistency is a great goal, but is clearer getting harder and harder to achieve as the company is getting bigger and more diverse in terms of product areas, engineering and other skills etc.
- nfw2 5y ago
- ford 5y agoThere are many comments here about title inflation/the increasing interest in "staff" engineers/etc - I tend to agree with the arguments in this article [0] (from Gokul Rajaram) that argues titles distract from what you should actually care about, celebrate, and recognize at a company - scope and impact. [0] https://medium.com/@gokulrajaram/the-one-thing-ceos-should-delay-as-long-as-possible-ea28347714b0 https://medium.com/@gokulrajaram/the-one-thing-ceos-should-d...
- draw_down 5y ago
- tomerv 5y agoInteresting that almost all comments here are completely dismissive of the meaning of staff+ titles, to the point of not even discussing the content of the articles. Yes, it's true that your title is not your role, and your role is not your job, and your job is not your professional identity. But your title is part of your professional identity, and it's the best shorthand to communicate your status with future employers, or even just with a colleague in a distant branch of your company. Our profession is young, so it's still in the early phases of defining itself. I'm sure other professions have title bloat too. You still need to play the game, even if you don't like the rules.
- ghaff 5y ago>your title is part of your professional identity Sometimes. I don't even use my actual title. (Mostly because I don't really do what my title says I do so I use something more generic.)
- folmar 5y agoMy company makes me free to use any title of my choosing except CEO. It's up to me whether I use it to accurately describe my job or use it as promo pull when changing jobs, and I see people using it both ways, and I think both ways do work.
- kyawzazaw 5y agoMD and VP in finance companies
- thenerdhead 5y agoI have this book. I enjoyed the previous book by the author much more. This one in particular focuses around a title, but my take away is “how to be a better knowledge worker”. There are so many great tips in this book ranging from leading without role power, daily tactics to drive results, and even when you should make a push for the title whether that is staying or leaving. The stories are okay and are half the book, but no single story of getting the promo is similar enough. It does help you realize you may not need a “SNAP” project to obtain an prestigious position. If the book had another hundred pages of being more efficient and strategic, I think it would be a better read. Stories in most tech books are not very helpful at least to me. I find them hard to relate to, but every once in a while a story will match my situation and help me grow.
- civilized 5y agoWhat is a "SNAP" project? I have never heard this jargon and it's also impossible to Google.
- thenerdhead 5y agoSomeone needs a promotion. It’s work that isn’t meaningful, but has leadership buy in and visibility.
- civilized 5y agoWhat a depressing concept.
- thenerdhead 5y agoVery. It is why there are product graveyards though. Usually compelling ideas that never were validated with product market fit. https://killedbygoogle.com/ https://killedbygoogle.com/ https://killedbymicrosoft.info/ https://killedbymicrosoft.info/ The other side is internal initiatives that become priority number 1 for a team and then die over the next year or so.
- hiptobecubic 5y agoThis seems to be split pretty clearly down a "promotion criteria" line. At small companies, where basically everything is arbitrary, sample sizes are small and there's not enough data to be data driven, titles are perceived as mostly meaningless. At large companies that do a good job of standardizing how promotion works and what is required to get it, titles are not perceived to be meaningless.
- lifeisstillgood 5y agoThere is a tension here I want to explore. Basically I have a theory that coders are the new managers (goes with my software literacy idea). Look at books on management ala Drucker in the 60s. These people (big managers) are a special species bestriding the world, aligning corporations to build better world. Recently google published a book on how to be a great manager which boiled its eight points down to "be nice to your coders so they stay" Companies are becoming programmable - machines that are slow AI and slowly speeding up that AI and that needs control via code. And the coders build that. So my theory is that each release of code is effectively a new company (machine). And that the people we call software engineers are writing the rules for those companies - but the non coding managers are not going to let go without a fight. Staff engineering roles are the front line for this battle. If it's all influence and social respect (like say Linus) then the future of empire building managers is shaky.
- throwaway879080 5y ago
- nfw2 5y agoMy main frustration with IC levels is that the promotions often come down to questionable criteria like: - Have you worked on highly-visible, high-level, cross-org projects? Are these efforts really needed? Should your organization be reinventing the wheel? I've seen staff IC's get unreasonably attached to their own pet projects and keep pushing them despite universally negative feedback from the engineers that would be affected. The right level of high-level abstraction should come from the actual requirements of the business, not artificially pumped up by engineers because it's required to get promoted. - Do you mentor other engineers? Do the engineers on your team actually need mentoring? Most of the people on my current team are not senior (IC2) and the best group of engineers I've ever worked with. We all have 5-10 years of experience. But the IC4 recently assigned to our team feels the need to give use engineering 101 lectures on every single topic, and it's been extremely frustrating. - Have you led projects? This one makes sense I know. But it's also often just a proxy for your time at the company if you need to patiently wait your turn to wear the tech lead hat. Glacial promotion opportunities often lead to the best engineers leaving
- juancn 5y agoHigh visibility sometimes is confused with strategic importance. Tech leadership roles in a sane org. focus more and more on the strategic than on the tactical. Help keep focus on needed projects that cannot be delivered in a short time frame, but are nevertheless needed, sometimes even essential. The ability to deliver short-term value while not derailing long-term goals takes experience to hone, and is one of the tells of a true staff+ engineer. Mentoring is complex. It's not giving lectures (although, sometimes it may help). It's usually more subtle and is typically related to delegation: pick the correct thing to delegate, choose wisely what to do yourself. The trick is to maximize learning and accomplishment of more junior engineers while at the same time not risking team/company objectives. Besides that, providing emotional support and guidance in a way that most managers cannot. You walked the walk, so you help them think on how improve and get where they want to get (even sometimes help figure out what they want). Leadership can also be subtle. Managers tend to equate it with project management (i.e. scrum/whatever, task assignment). On a tech ladder role, leadership is much more about influence than actually telling people what to do. You nudge them in the right direction so the goals are met and they grow (see: mentoring). The best tech leads (staff+ or whatever), get shit done in a way that's sometimes non-obvious, until you miss them. Which makes promotion hard.
- lifeisstillgood 5y agoAlso - any pyramid has less jobs at top than below. By definition, you can have 100 people be as awesome as you like but if there is only one open position 99 will be disappointed. As such it's not about the qualities of the candidates it's about the internal politics of the organisation. Once "it's about the internal politics of the organisation" rules it's time to tear down the organisation.
- steelframe 5y agoStaff-level tends to happen if you are able to stay motivated to keep finding and fixing problems for a long enough time. You will naturally build expertise in whatever field you're in as you iterate on that, until eventually you just know all the ins-and-outs of the systems in which you're working that you can "see around walls" when more junior people waltz in and try doing stupid sh*t. Your proactive criticism of their ideas and code will be seen as technical leadership -- well, because it kind of is. The only people I know who got stuck at Senior as they got older were the ones who let themselves get to the point where all they wanted to do was pull a paycheck until they could retire. They stopped giving a fsck when they saw stupid sh-t happening around them and just let it happen.
- juancn 5y agoStaff is the entry level of the serious technical leadership ladder. It's a pivot point for many (i.e. a phase change if you like). As a technical leader, you don't have direct reports (if you have, you're a manager) and your job is one of leadership through influence rather than formal power (you're -in a sense- an "influencer"). You sell ideas, you nudge people in the right direction, you mentor and help others grow and you help people think clearly and relax in difficult technical situations. The higher you get on the ladder, the more strategic your work becomes. You look farther in the future, projects take years to crystallize, you build blocks that buy us something now, but work as a stepping stone for a larger goal in the future. With this type of leadership, comes a surprise to many tech-minded types: your work becomes a lot more about emotions than technology. You need to project calm, help people think things out. Guide them without giving them the solution so they can grow. Help them through crises and so on. This applies even to managers above you in the hierarchy. The relationship becomes different, you're no longer a subordinate, you're now a peer (even if the org chart says otherwise). As you may imagine, it takes a while to get there from just a strong technical background.