6 ms·
The issue of seniority always bugs me. If a 26 year old guy who writes "good enough" code can be a Senior, which I see very often, what's left? Personally I wo
by ricardobeat 14y ago
The issue of seniority always bugs me. If a 26 year old guy who writes "good enough" code can be a Senior, which I see very often, what's left?
Personally I wouldn't feel right with a title including "senior" until I've got at least 10y experience, generated millions in revenue and lead a team of >10. And I'd still prefer not having a title. Unless the only way to increase a salary is by taking the title, which seems to be the problem.
- mattetti 14y agoThat's a very good point, John Allspaw from Etsy has a great post on that topic: http://www.kitchensoap.com/2012/10/25/on-being-a-senior-engineer/ http://www.kitchensoap.com/2012/10/25/on-being-a-senior-engi...
- tmarthal 14y agoHere is a great article on what it means to be a Senior engineer: http://www.kitchensoap.com/2012/10/25/on-being-a-senior-engineer/?utm_source=statuscode&utm_medium=email http://www.kitchensoap.com/2012/10/25/on-being-a-senior-engi... The long answer is maturity. Then the author goes to explain what maturity brings to the discipline of software engineering.
- edw519 14y ago...what's left? Where do I begin? - Drilling down multiple levels for greater understanding. Being the "anti-poser" by knowing what's really going on under the hood. Sharing this insight with others. Amazing what a difference maker this often is. - Subject matter expertise. Can you stay two steps ahead of your customers by getting behind their eyes and seeing what they need before they do? - Continuous improvement. (I know, a B.S. term if there ever was one, but it's true...): "Good enough" is never good enough any more. Get better or someone will eventually eat your lunch. - Communication skills. We all suck at them so much that this is often a bigger speedbump than technical shortcomings. We have much to learn from ants. - Vision. Another nebulous term, but one that often makes a difference between arithmetric and geometric growth. - Determining priorities. (Are we really working on the best thing?) I can go on and on, but you kinda get the idea.
- kami8845 14y agoI knew this was an edw519 post when the second point immediately talked about customers. :) Thank you, this is a good set of points.
- pan69 14y agoI think he was referring to the "title-itis". Titles make absolutely no sense and they seem to be used as a currency by employers and as resume trophies by programmers themselves. To many times have I seen mediocre programmers negotiating themselves into a BIG title simple because the employer didn't want to give that person a pay rise (titles are free you see). Once they get the title, they sit on sit for a few months and then they fuck off to work for another company. This way they keep their title AND get a pay rise and all while being mediocre.
- ricardobeat 14y agoI'm sorry, as pan69 pointed out, I meant what's left for career progression (without going into management). When a truly senior developer comes along he will be stuck at the same level as the "good enough" (in a bad sense) guy, maybe even at the same pay.
- hippich 14y agoOn the other hand how I can differentiate myself without using "senior" from others developers of my age, who took this job as a result of additional course during their college time and who as result produce quite ad-hoc code without any interest in technology and what lies below job they do? That's the only reason I am using senior in title. Because I do not agree that all 20-something devs bring same value to the team.
- vampirechicken 14y agoTitles were more about pay bands then skill. I know several hundred Vice Presidents at JP Morgan Chase. And really, if your business card tells me that you're a Programmer/Analyst 3, then you're either doing something wrong, or you're a robot, and you probably work between Programmer/Analysts 2 and 4.
- johnnymonster 14y agoCracks me up when people cling to titles. Even funnier when I see software developer 3 on a business card!
- smutticus 14y agoIn my new startup our software engineering titles go up to 11. http://www.youtube.com/watch?v=EbVKWCpNFhY http://www.youtube.com/watch?v=EbVKWCpNFhY
- mgkimsal 14y agoI was given a title once, and I think it was a 3 (this was... a heck of a long time ago). But... I wasn't told what the 3 meant - is 3 the bottom? The middle? The top? Is "level 1" where people start? Or is it like golf, where a lower number is better? I asked, and ... got the weirdest look, as if I was an idiot for not having some insider knowledge about "corporate titles". I wasn't there very long. And I never actually got an answer...
- jerf 14y agoOh... I think you got answered, at least the question that mattered. It sounds like you took the correct action based on the answer, as well.
- efuquen 14y agoI always thought that those number titles were based on a scale from 1 to 5? Usually when I see 3 I think the implication is that you're a "mid-level" engineer. I understand the point that these numbers can be arbitrary and not well defined, but I think the idea that this is a "mid-level" engineer would be well understood (I believe this sort of numeric distinction isn't unique to just software engineers). Did you truly not get that or were you just asking the question to illicit a quizzical response?
- tgrass 14y agotmarthal, you appear to be hellbanned.
- uxp 14y agoWhich is unfortunate because tmarthal's link is quite good: > Here is a great article on what it means to be a Senior engineer: http://www.kitchensoap.com/2012/10/25/on-being-a-senior-engineer/ http://www.kitchensoap.com/2012/10/25/on-being-a-senior-engi... > The long answer is maturity. Then the author goes to explain what maturity brings to the discipline of software engineering.
- tmarthal 14y agoI posted that link at the same time as someone else, with a post date like 5 minutes after them. I also didn't clear off the referral parameters (I got the original article in an email blast about tech news, with two utm_ parameters). So maybe it looked like a referral link or a possible duplicate of someone else's. shrug Either way, that article really made me re-consider the 'Senior' in front of my title. Very well written.
- fokov 14y agoIn many large corporations including the one where I work, the wages, salaries, and benefits brackets are all determined by your title. The only way to get out of those brackets is to get promoted to a 'better' title. I'm don't care for titles. When I was first starting out, I was the first hire under the "Director of Software Engineering". He was the only one in his department for over 3 years. The company had only a handful of people. Shortly thereafter I found just how bad the situation was. After 3 years for what was essentially an enterprise data entry application there was not one production line of code written, but he had a great title! I had a painful experience working there, but I'm better because of it.
- randomdata 14y agoI was given the senior title in what was essentially my first programming job. I found out later, the boss actually thought I had more than a decade of experience. I've never cared much for titles though. They seem pretty meaningless to me.
- thetrb 14y agoWhat's left in most companies is usually some title including "Principal" or "Staff". So Senior clearly isn't the end of the ladder.
- michaelochurch 14y agoThe issue of seniority always bugs me. If a 26 year old guy who writes "good enough" code can be a Senior, which I see very often, what's left? Some ideas, possibly an answer: http://michaelochurch.wordpress.com/2012/01/26/the-trajectory-of-a-software-engineer-and-where-it-all-goes-wrong/ http://michaelochurch.wordpress.com/2012/01/26/the-trajector... What companies tend to call "Senior" is usually around 1.4-1.6 in terms of responsibility. That said, most companies don't give you 1.4-level work until you're 1.7-1.8 in ability. "Senior" is a title inflation at this point. I wouldn't join a startup (or any company for less than 0.9 times what I can make in finance) for less than a VP-level title, even though I'd be perfectly happy to code full-time and have no reports.
- fizx 14y agoAlso, if you go by the google ratings, which are similar, you get: Intern Software Engineer Senior Software Engineer Staff Engineer Senior Staff Engineer Principal Engineer Distinguished Engineer Fellow All of a sudden, "senior" doesn't feel very far up the totem pole.
- michaelochurch 14y agoIf I ever develop an HR system/title hierarchy (and I don't see this as likely) titles will be more ornate at the bottom. At the top: Programmer.
- SatvikBeri 14y agoNot to mention Coder and Bug Fixer.
- guard-of-terra 14y agoI remember a talk by collegues ten years ago when they suggested we have to have "grand vizier" or "padishah" titles.
- trhtrsh 14y ago"Fellow" sort of gives you that already.