7 ms·
What is the difference between a senior engineer and a staff engineer?
by davesmylie 2y ago
What is the difference between a senior engineer and a staff engineer?
- petesergeant 2y agoSalary bands
- i_am_a_peasant 2y agothey can overlap a lot across titles
- pockmarked19 2y agoThe staff title unlocks a new level of self-aggrandizement which is on display here and in certain published books. As for professional qualities, I don’t think there is one. It takes a staff engineer at FAANG to do what a senior can do at a smaller company, because of all the other self—important people not listening to you. (Dealing with that is a skill though, so having that skill might be it.)
- iLoveOncall 2y ago> It takes a staff engineer at FAANG to do what a senior can do at a smaller company This is beyond laughable. FAANGs are pretty much the only place where staff is actually hard to make. I see countless "senior" engineers with 3 years of experience in smaller companies. The truth is it would take a good entry-level FAANG engineer to match a senior engineer in a smaller company.
- soulofmischief 2y agoYou've missed the point. OP is discussing affordance, not skill. A senior engineer at a smaller company may have equal or less skill than a staff engineer at a larger company, but they have more affordance if there are less cogs in the bureaucratic machine that need oiling whenever they need to get something done. Experience in a variety of workplaces will give you the same intuition.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- i_am_a_peasant 2y agoi don’t see why the size of the company one works for has to be correlated with an engineer’s skill level. i’ve seen some of the best programmers i ever met cone out of 10 years working at a small company because it happened to be closer to his kid’s school route.
- almostgotcaught 2y ago> i don’t see why the size of the company one works for has to be correlated with an engineer’s skill level People have such weird delusions about this. Imagine saying the same thing about the NBA vs your local pick-up games. Literally untenable.
- i_am_a_peasant 2y agoSports and programming just aren't comparable. Some finnish student wrote the linux kernel my man, while living with his parents.
- almostgotcaught 2y agoHave you ever heard the expression "the exception that proves the rule"? Also I love how you think the Linux kernel is valuable because Linus started it and not because millions of hours have been invested in it by other engineers (most of whom are employed by big corps).
- jokethrowaway 2y agoI'm sure there are exceptions (and it's way more likely that the very top are in FANGs, maybe the distinguished engineers making millions per year?) but I was never particularly impressed with the level of skills of average FANGs people. The difference in compensation between NBA and local games is millions to nothing - between FANGs and other company there is a much smaller factor and there are way more perks in some small companies than in FANGs: less politics, no PIPs, remote, low tax / low cost of living locations, no 6m to prepare for an interview, riskier equities (if that's your thing), CTO path, etc. All my FANGs friends ended up in smaller companies after having marked their CV as ex-Apple or ex-Google. If I were younger and I was earning less and happy to sacrifice quality of life to live in some big city, I would spend the 6m prep-time and leetcode, just to have the FANG name on my CV and charge more to other businesses later on.
- stavros 2y agoThe GP is saying that FAANG companies need staff engineers to navigate the politics enough to achieve the same level of productivity as a senior engineer in a small company.
- icedchai 2y agoSo true. During the dot-com boom, I was a "senior" engineer 2 years out of school.
- deleted 2y ago[deleted]
- hivacruz 2y agoI guess a senior engineer might be "linked" to a single kind of tasks (backend, frontend etc) while a staff engineer has knowledge in a lot of domains and can be the "bridge" for projects that need people from many different teams
- throw5959 2y agoNonsense.
- jayd16 2y agoThe size of the company handing out the titles.
- deleted 2y ago[deleted]
- chollida1 2y agoDepends on the company. I've worked for companies where staff engineer is below senior engineer and for companies where the opposite is true. And I have worked for a company where everyone is just a staff engineer with no titles to differentiate, liked this setup the best. There is no industry standard, each company labels things differently.
- onion2k 2y agoScope of influence. A senior should be defining and building things within their team. A staff engineer or a principal should be influencing things more broadly than their team.
- sys_64738 2y agoCorrect. The old not what you know but who you know. Unless you've developed that influence and lived the role then most don't understand what it entails. Getting things done at a massive company can be very hard.
- likeabatterycar 2y agoThis is a trick question, because the only correct answer is "it depends". The definitions are arbitrary and vary - sometimes wildly or completely opposite - from company to company and industry to industry. Some companies don't use titles at all and use levels - which are also arbitrary and differ accordingly. If you never leave the incestuous Silicon Valley bubble, however, you may never learn this.
- Hamuko 2y agoDifferent spellings.
- epolanski 2y agoIt's company dependent but in general less coding, more management, more decision making power, more money, different responsibility. A senior in one org may have the responsibilities of the staff in another one, it depends.
- roncesvalles 2y agoWithin the same company? Money, that's about it. Between companies there is no standardization of levels, titles, and responsibilities. Fun fact: at IBM a "Staff" is actually junior to a "Senior". So it's all over the place anyway. The latest trend in new companies is to not assign named titles at all, just numbered levels.
- sys_64738 2y agoIt's like that in a lot of companies which were influenced by IBM way back.
- hshshshshsh 2y agoNothing. The manager reads the Phsycology of the engineer and gives them whatever title which makes them happy. Since vast majority of humans find meaning and purposes in random words this works.(Starts with identification with their own randomly assigned name when they were born). A better measurement of significance would be the amount of money one get paid. That has more correlation with reality than random titles. For example a mid experienced engineer at Nvidia is doing better than a staff engineer at a random tech company because of their millions of dollars gains in Nvidia stocks. Now you can write all day about being a "staff engineer" in LinkedIn or blog posts and how that is such a big deal blah blah blah. But all that is spam when we measure it with reality (your bank account).
- mattlondon 2y ago+1 They can call me "junior" or whatever they like, just give me more comp please.
- goalieca 2y agoI used to think like that, but having a title helps switching jobs.
- deleted 2y ago[deleted]
- torginus 2y agoIn my experience, staff engineer is an an alternate role to software architect - some companies have the former, others the latter. When doing something that requires serious design work, an architect typically does it by drawing diagrams, sitting in meetings, writing docs, but not doing coding that much. Staff engineers tend to be more coding and technically focused, they bootstrap features by designing and coding the skeleton and coordinate the work of oter engineers in building out the feature. It's a much more natural career path for people with a coding background but some companies, particularly enterprisey ones with lots of bureaucracy, prefer architects.