9 ms·
I have seen this happen more and more in tech as well. Engineers join a company right out of college, are promoted to "senior" in a couple of years, and "staff"
by paxys 4y ago
I have seen this happen more and more in tech as well. Engineers join a company right out of college, are promoted to "senior" in a couple of years, and "staff" another two or three years after that. Now because everyone is staff you have to keep making up fancier titles – senior staff, principal engineer, technical lead, architect, senior architect, chief of staff, partner engineer, distinguished engineer, technical fellow...
I asked a higher up why this was the case, and the response was simply that people quit if they aren't promoted quick enough. Titles are free, and smaller companies have zero problems handing them out like candy to keep people happy.
- JSavageOne 4y agoPeople are getting promotions without pay increases? That's news to me. If you're getting promoted and being assigned greater responsibility, than your compensation should increase accordingly.
- wodenokoto 4y agoIf you are 2 years out of college you might not know what that compensation should be. You might not even know what the increased responsibility of the title should be. But you do appreciate the bragging rights of the title, and so that is all you get. E.g., senior means I'm officially leet. Not that I have responsibilities.
- thenoblesunfish 4y agoThe title change itself has real value to people. People love to feel a sense of progress, and they love to feel appreciated. Promoting the same person twicw over N years, instead of once, may cost the same but will make the employee happier. That's the free part.
- taneq 4y agoAnd just like monetary inflation, this inflation's cost is hidden in the devaluation of the inflated commodity. 'Senior Engineer' used to be a title that people valued highly, as a result of the years of work it took to earn. Now nobody's impressed by such a title.
- denton-scratch 4y ago> The title change itself has real value to people. Not to me. A "title promotion" without a pay rise would be demotivating, and lead me to wonder what I had to do to get a pay rise - like, leave, maybe.
- thenoblesunfish 4y agoThat's fair - my first sentence maybe isn't always true in isolation , but I think in the context of the second one it is. Obviously it'd be ideal to invent new ranks between the existing ones, instead of the inflation.
- bluGill 4y agoOf course you get a pay raise. Inflation means that you should get a 2-3% pay raise every year - and this past year you should have got a 7-8% raise. Most people don't index their raises to inflation, a few years of 2% raises against 0% inflation looks pretty good, and they have a nice new title along with the raise. Never mind their real income is now less than it was a last year, they got a title and a raise. I can't figure out how to get inflation through to whoever decides what raises should be - at any company I've ever been at. I would encourage everyone reading this to head into wage review discussions with the current yearly inflation number and make sure you boss knows it. Most companies seem to get slightly negative raises (measured against inflation), and then every 5-10 years a 10% across the board raise to bring everyone back in line with inflation.
- cratermoon 4y agoIt's not just tech companies. I've seen non-tech companies with internal engineering teams hire mid-level skill people at Principal Engineer. By their measure, actual Staff to Principal engineers would be something like Distinguished Engineer, Senior Distinguished Engineer, or Executive Distinguished Engineer. The heart of the problem is that most companies have no real path that isn't into management.
- oblio 4y agoI think banks are the canonical example of title inflation, where VP doesn't mean anything anymore.
- bluGill 4y agoVP in banks is one title that means something. A VP is able to sign off on your getting a loan from the bank. This is a legal thing, someone who isn't a VP cannot give you a loan. (the rules are a bit more complex, but close enough). Thus banks of lots of VPs with very little power: they need people all over who can give loans out.
- gorgoiler 4y agoIt’s even worse than just title inflation. Orgs lose the plot when they lose their calibration against the rest of the industry. These senior engineering roles have well understood requirements: cross org influence, leading a project independently from inception to completion, understanding business impact and keeping senior management in the loop. The problems come when your cross org engineering influence is “move our source code from shared drive to github” and keeping senior management in the loop means chatting about it over takeout with your roomies who are also the CTO and VP of Design.
- eastbound 4y agoSo, the fact that everyone is in a small startup instead of a bug corporate “is” the problem of job inflation (After all, when I started my product alone for 4 years, I sacred myself CEO). - Everyone-in-a-startup is a side-effect of incredible automation where every competent engineer can leverage dozens of automations, CI/CD, automatic accounting and SAAS products. It’s a real capacity of coordinating. - Titles will readjust. Titles will mean nothing. They should mean nothing. We’ve already given up reading the degree/diploma of programmers, skills matter more. Software development is so erratic and devspeed is so much due to individual talent that single founders with 50 employees can sell themselves to Facebook for 18 billions. When we can get predictable results out of software engineering, we’ll discuss how to position each one in a hierarchy.
- LAC-Tech 4y agoI'm not convinced that big organisations teach you more than smaller ones, given how hands on you have to be at a smaller shop and how sclerotic larger ones are.
- BigJ1211 4y agoYou learn a lot more about the process itself in smaller companies across the board. In larger companies that only happens in the higher level roles. In larger companies your secondary and tertiary skills also become significantly more important. Ultimately I prefer working with people that have experience in both. Engineers who've only worked in smaller companies tend to be harder to work *with*, on a social inter-colleague level. Engineers who've only worked in larger companies tend to be less capable when left to their own devices, they need more help if there is less demarcation. Engineers who've worked in smaller teams tend to pick up the slack proactively, from larger teams retro-actively. At least that's been my experience both from within as well as without. (Currently working for a small company that has large corporate clients, have worked for small and corporations before that)
- kgeist 4y ago>the response was simply that people quit if they aren't promoted quick enough Our company has grades instead: J0, J1, P1, S2 etc. So if someone is a junior, they can be "promoted" 2 times (J0 => J1 => J2) before becoming a "pro" (P1), and 2 more times before becoming a senior (P1 => P2 => S1). The official titles are still just "junior engineer", "senior engineer" etc. As a consequence, since in other companies they often promote just "junior => senior", when we hire someone who was previously a "senior", they are often assigned a junior grade (for example, J2) which often demotivates people
- paxys 4y agoThat's how Microsoft does it. Pay grades range from 59 (SDE) to 80+ (Technical Fellow), and your actual title only changes every 3-4 levels.
- emodendroket 4y agoI feel like this is easier to accept at Microsoft or another big name than some nobody.
- emodendroket 4y agoI don't see much issue for the same reasons you stated. What's the harm?
- thomc 4y agoOne issue I've noticed is in organisations that have staff in regions that don't have title inflation. For example in the UK orgs I've worked the majority of people were not particularly concerned about titles and didn't even put titles in their email sigs. When some offshore temp contractors came onsite and gave themselves grandiose titles in their email sigs that were far above the people they reported to it created a lot of confusion and consternation. I've also seen issues when UK colleagues who are senior enough to manage teams who manage teams, but are still below the "Director" role, then have to manage an entire team of "Directors" and "VPs" in NA who are the bottom rung and manage nobody. It seems like the job titles in NA can be totally meaningless? I suppose if you are used to how it works, it works fine, but if you are from a region with more conservative (and accurate?) titles it causes friction due to an imbalance in perceived power dynamic. I've even seen an org chart in a NA firm that has 3 CTOs stretching down the same reporting line, which just seems pointless.
- Foobar8568 4y agoBecause a big4 gave them their org structure used in their industry, and applied with people they had. That's how I am teaching what is an api gateway to the cloud integration team 2 years after their existence.
- denton-scratch 4y ago> When some offshore temp contractors came onsite and gave themselves grandiose titles Never seen that; in fact I've never seen a contractor with a job title. I would be predisposed to think less of a contractor with a grandiose title.
- AdamH12113 4y agoIt's worth noting that "engineer" itself is a bit of title inflation. "Software engineer" was supposed to involve training people to apply engineering methodologies to software development. Today it's just a fancy term for "programmer".
- nerdwaller 4y agoCan you define what a "programmer" is?
- codetrotter 4y agoA programmer is a person who writes program code. A software engineer applies engineering principles when designing and/or implementing programs. A computer scientist uses scientific methods and rigor when solving problems relating to computing.
- thriftwy 4y agoSoftware does not work like that. If I would to meet somebody who claims to apply engineering principles or, worse, scientific method, I will make sure to be on top of their PRs at all times.
- SlickNixon 4y agoWhy I always make a point to mention my preferred methods for determining architecture--bird signs, and throwing the bones.
- newaccount74 4y agoIt does. We are just not used to looking at it like this. For example, if you are changing labels or adding buttons to a web app according to detailed instructions from a manager, then I would call that "programming". If you are implementing an OAuth flow, or designing an API for some service, and doing so according to the current state of the art, you are "engineering". If you develop a novel algorithm to solve a specific class of problems, you are "computer sciencing". Obviously, there is some overlap between the tasks, and people will switch between the different parts depending on the stage of the project, but I don't think the titles can be chosen randomly.
- lumost 4y agoMany companies have a policy that you can’t give someone a real raise without a promotion. In tech, this means everyone good gets an annual promotion at some firms.
- shusaku 4y agoIronically, they probably quit because another firm is offering more compensation for people with such a title!
- epicureanideal 4y agoI think this phenomenon with "senior" happens because we don't have an equivalent to "apprentice", "journeyman", and "master", and several of these terms would be considered inappropriate if we did. Senior has effectively become "journeyman", and Staff has become "master". And then Senior Staff, Principal, etc. are higher levels of mastery of the craft. It sort of makes sense. Some people with 1-2 years of experience really are significantly qualitatively different than others with that few years of experience. Some people with 5 years really are able to run teams and build large systems independently. It shouldn't be about the years alone. Edit to add: Also, after 4 years intense studying it could be said that every software engineer with a Bachelors degree has already passed through the apprentice phase, their first 1, 2, or 3 years might legitimately be their journeyman phase, and so after a couple of years they might legitimately be "senior" in the sense of being an independent expert practitioner. Remember that we're talking about a person who has now spent 5-7 years of their life developing these skills, and possibly more before they attended university. (And it then makes sense that the next step up would either be Staff or Architect as their skills grow to handle more complex organizational matters or even more complex software systems respectively.) Now obviously that is NOT true of a large number of people who don't apply themselves in school or in their jobs, and so just sit in their chairs watching the clock until they have enough years of experience to be "senior", but a person who applies themselves can achieve a level of capability in a couple years that the person who does not apply themselves might never achieve in their entire career.
- lazyasciiart 4y agoThere is supposed to be a gap between "journeyman" and "senior". The place where competent workers who don't need supervision but aren't going to design a system or coordinate a project are. The programmers/software engineers/default-noun-for-job.
- denton-scratch 4y ago> "apprentice", "journeyman", and "master" My last boss used to appoint "apprentices". They would stay as apprentices for all of 6 months (I think they got a tax-break for having apprentices). Traditionally, an apprentice in a trade would be indentured for several years, studying/serving under a master. After completing his apprenticeship, the new tradesman would be kicked out, and barred from working in the same city as his master; he was expected to travel around and broaden his experience. That might last a decade. He'd then have to convince his trade guild that he now qualified as a master, often by presenting an exceptional piece of work (a "masterpiece"). It's often said that it takes a decade to learn anything really well. I think that applies equally to programming. So the "journeyman" stage fits in with that, as a way of designating someone's skill level. But the "apprentices" I worked with were doing exactly the same work as everyone else; we were all fungible programmers. In 45 years in the industry, I worked with approximately two people I'd designate as "master".
- SCUSKU 4y agoA friend at Visa worked there straight out of college after completing a 5 year BS/MS program, and on his resume it says he went straight from "intern" to "senior engineer" because an MS degree apparently automatically makes you senior.
- torginus 4y agoIn a world where 2 years of experience can make you 'senior', I could understand that someone who went for a 2 year MS instead of BS + 2YOE would think they are on the same level.
- BeFlatXIII 4y ago> Titles are free, and smaller companies have zero problems handing them out like candy to keep people happy. It’s in everyone’s best interest except for the industry as a whole. It’s why a “distinguished fellow” has to do the same inane leetcode grind as a fresh grad or someone with no degree who really likes computers.
- mejutoco 4y agoIMO the main reason for this is that a title promotion is cheaper for the company, and it is often in place of a salary increase.
- pfortuny 4y agoIt is totally unbelievable how many “vice-presidents” a company can have. It distorts the meaning of the word to the point that it really is not vice in any way. Much less president…
- denton-scratch 4y agoAm I right in believing that US vice presidents are officers of the company, and can sign contracts on the company's behalf? I was once told by a VP of Marketing that because he was a veep and could sign contracts, he had a fiduciary duty to his employer, and was constrained in the kinds of thing he was allowed to say.
- bluGill 4y agoYes, a VP can legally make decisions on behalf of a company that normal people cannot. As such some industries will have more VPs than others. When you get a loan (ie for a normal house) a vice president is probably required to sign off on it. Thus banks have vice presidents at most/all branch locations. Their pay, responsibility, and influence is pretty small in the company, but they are a vice president because that title is legally required to make the routine decisions they make every day. The top salesmen in most companies also get a vice president title because customers fell important customers if a vice president is assigned to talk to them. Of course a vice president is allowed to make some decisions so they should (but may not) avoid promising things as it could be legally binding.
- dhosek 4y agoNot necessarily. In the financial world, VP is a title that they hand out like candy. I worked at Bank of America as a Senior Software Engineer but my title was VP. I almost turned down the job because I thought they’d made a mistake and were hiring me into a management role.
- iNerdier 4y agoI still don’t understand how ‘architect’ is an acceptable title. Here in the uk at least it’s a protected title, much like (medical) doctor and you can’t practice and call yourself an architect without approval from their governing body (the arb). Apparently that doesn’t apply to software developers though somehow?
- lazyasciiart 4y agoThe Act that regulates the title 'architect' contained a specific clause that says "(2) Subsection (1) does not prevent any use of the designation "naval architect", "landscape architect" or "golf-course architect"." I think it's pretty safe to say that software architect would have been included in that carve-out if it was written today, and the ARB says: "We take a common sense approach to the use of ‘architect’ that isn’t connected to building and design, for example with ‘software architect’ or ‘systems architect’ which are increasingly used by the computer and IT industry." https://arb.org.uk/architect-information/what-we-do-to-regulate-the-use-of-the-title-architect/ https://arb.org.uk/architect-information/what-we-do-to-regul... Since the only way it is regulated is by the ARB bringing action against a person, their decision to ignore software architects is pretty final.
- anilakar 4y agoFunny. Looks like I'm traveling down the demotion path as we've grown. Literally started as Support Manager which basically meant that the tech support phone was on my desk in a four-person company. The three other people were the CEO, Software Development Manager and Hardware Development Manager. Next, I became a Senior Software Developer, because a customer contract required seniors assigned to a project. Now I'm a Software Specialist which basically means bottom of the bin in the title hierarchy here.
- snapcaster 4y agoSounds like lost a political struggle and weren't even aware it was happening. Maybe you're being taken advantage of?
- jetsnoc 4y ago> [..] people quit if they aren't promoted quick enough. Titles are free, and smaller companies have zero problems handing them out like candy to keep people happy. My experience is that those same people quit once they are promoted. They are playing a game of ladders. It might be your corporate ladder they are trying to climb but most likely it is someone else's. They want that Senior Engineering title so that they can hop to the next organization without putting in the work to achieve that title at that company. And, it works. Some of my former coworkers have been hired for jobs far above their skillsets and it's on those hiring companies for not being able to assess competence. I have had employees from my company with only four years of experience leave for a VPE title. I wouldn't trust them as an engineering manager or senior engineer reviewing code let alone a VPE but companies are desperate and they were charismatic enough to BS their way through interviews. I always smile when that happens because I know which company will likely go out of business since they can't assess skillsets without titles. These companies are willing to pay way more money for far less talent and well that's the stupidity tax these companies get to pay. If recruiters are going to farm talent from smaller companies, as they do, I will ensure from here on out that externally all of my duds have Senior, Principle, or Distinguished engineering titles. I will hand them a grenade with the pin removed... Electrons to bits they hire them without evaluating skills or experience. ;) I'll give my exceptional talent titles like Level 1-M.U. (Level 1 being our highest most prestigious rank, the title being master of the universe, or whatever.) This is the game companies they have created since they can't assess competence and corporate recruiters only know how to search LinkedIn for titles. They made that bed, now they can sleep in it :) Jokes aside, I was only burnt a few times by employees wanting titles in order to jump ship quickly. I now recognize my coworkers with accolades, great pay, flexibility, and treating them like the intelligent adults that they are. Collaborating with them. Being transparent. If they still want to quit because I won't give them a title too soon and their ego simply cannot get past that, it's just not a great fit and I don't want to keep them from fulfilling the needs of their ego at their next job. That being said, the right people get the right titles at the right time, and in between then, there are a lot of ways I promote people culturally without giving them a title too soon. Most people just want meaningful work, paid well, and only after those two have been addressed, then do they want recognition. Don't get me wrong, they want recognition too but a lot of poorly managed companies don't understand what meaningful work and paying employees well means so they hand out titles as quickly as they can. Heck, they don't understand what recognition is either if the best they can do is hand out a title. PS; I am definitely not saying that is what is happening at your company or with your higher ups. I am just over here hyperbolically weaving fantastical yarns of fanciful prose to amuse and illuminate at 0530AM MST.
- harimau777 4y agoIf lower level engineers were well treated, then I think that they would feel less pressure to be promoted. As the saying goes "shit flows down hill" and software development has a lot of shit.