News for hackers. Stuff that matters.
Re:What I learned working with a senior engineer as a new grad by fake-name on Friday August 19, 2022 @05:19AM (#32518951)
> senior engineer

> been a professional engineer for 6 years

Man, the software world is just weird.

Re:What I learned working with a senior engineer as a new grad by nhoughto on Friday August 19, 2022 @06:51AM (#32519469)
Maybe I'm the outlier but at >15 years into this job I think back on what I was like/did/thought 6 years in and shudder, at that point I never mentored anyone my junior seriously enough to influence their perception (I don't think) but if I did I'm not sure it would have been a positive influence. The lack of failures, felt pain, time to reflect.. in combination with the hubris of 20-smth youth isn't a recipe for good software engineering I don't think.
Re:What I learned working with a senior engineer as a new grad by mierz00 on Friday August 19, 2022 @05:30AM (#32519028)
Is it really that weird?

In the military 6 years is definitely considered senior and I’m sure that’s also the case in a lot of other fields.

Re:What I learned working with a senior engineer as a new grad by fake-name on Friday August 19, 2022 @05:56AM (#32519158)
I know the EE & ME worlds, senior generally implies at least two decades of experience. I'm pretty sure the same is also true for civil engineering, and most of the other "hard" engineering practices.

It seems like (at least outside of the military) the duration to being senior and the importance of things not going wrong are correlated.

Re:What I learned working with a senior engineer as a new grad by ReadTheLicense on Friday August 19, 2022 @06:01AM (#32519191)
The meaning is different. In software industry, senior means "doesn't need handholding", not "super-super-long experience" as in other more traditional fields.
Re:What I learned working with a senior engineer as a new grad by pjmlp on Friday August 19, 2022 @08:31AM (#32520173)
I expect more than that, a senior should be in the position of accomplishing a task based on a ruff abstract, they should also be able to mentor juniors and jump into meetings with the customer, supporting architects and sales, if needed.
Re:What I learned working with a senior engineer as a new grad by papito on Friday August 19, 2022 @06:46AM (#32519425)
My friend is in the military (information technology side). We are both 40-ish. I am only beginning to feel like a senior, and he has the option to retire.
Re:What I learned working with a senior engineer as a new grad by BerislavLopac on Friday August 19, 2022 @05:59AM (#32519181)
I think a part of this issue is that there is nothing above senior.

Additionally, "seniority" is relative and can vary between different technologies: for example, I have been working as a software engineer for 25+ years, and while I have worked with Java before I am no better at it than someone who just graduated. Similarly, even though I spent nearly a decade as a frontend dev, the last time I did that professionally was in mid-aughts, and I have zero experience with React, TypeScript and other modern staples of that area.

Re:What I learned working with a senior engineer as a new grad by Cthulhu_ on Friday August 19, 2022 @06:11AM (#32519245)
> there is nothing above senior.

Only in industries where software development is not a primary business; beyond Senior there's titles like Lead, Staff, Principal, Distinguished and Fellow SWE, or branching off, things like architect.

Anyway, senior engineer is less about what languages do you know and more about making informed technology decisions, maintaining quality, managing and training less experienced people, etc. It's also - IMO - not down to years of experience, because you can have 25 years of experience but be stuck at a certain level or stuck in a certain technology.

Re:What I learned working with a senior engineer as a new grad by goodpoint on Friday August 19, 2022 @08:57AM (#32520396)
"Lead, Staff, Principal..." exist only in few companies, are even more vague that "senior" and don't even represent seniority but rather how long a person worked in the same company.

(And how lucky they are at getting promoted withing that company)

Re:What I learned working with a senior engineer as a new grad by wizofaus on Friday August 19, 2022 @06:35AM (#32519357)
> I have been working as a software engineer for 25+ years, and while I have worked with Java before I am no better at it than someone who just graduated

Don't see how that's possible. I wouldn't even think 50% of what makes anyone a good Java developer is due to anything Java-specific. And you'll undoubtedly pick up Java-specific knowledge faster than the graduate is likely to.

Re:What I learned working with a senior engineer as a new grad by unwind on Friday August 19, 2022 @06:02AM (#32519199)
Sometimes I see the title "principal engineer" used, and my impression is that it trumps a mere senior. See [1] for an example.

I'm not in the US though and also work as a contractor so it's hard to use titles like these in my daily work.

[1]: https://about.gitlab.com/handbook/total-rewards/compensation...

Re:What I learned working with a senior engineer as a new grad by kasey_junk on Friday August 19, 2022 @08:08AM (#32519990)
You, accidentally, tripped a pet peeve of mine. Many people seem to think of writing software as a command and control function like some hypothetical military rank (and the leveling process engaged in by tech. companies reinforces this) where people higher up the ladder “trump” those lower.

But in software (and perhaps all knowledge work) many many times its the lowest ladder employees who are closest to the actual problem space. They are the ones dealing with the hacked up code base from 8 years ago, the indecipherable comments, the untested code that is critical to the business.

The job of the more senior people is not to command and control those employees, but to empower them. Bringing breadth of experience, or in depth expertise that is not specific to the problem at hand to help them make a decision.

Sorry, rant over.

Re:What I learned working with a senior engineer as a new grad by treis on Friday August 19, 2022 @10:08AM (#32521117)
What do you think should happen if a more senior person brings their breadth of experience or expertise and the junior engineer disagrees and does something else?
Re:What I learned working with a senior engineer as a new grad by kasey_junk on Friday August 19, 2022 @10:19AM (#32521276)
Obviously depends on the situation but almost always the person closest to the specific problem should make the call.

That’s why one of the most important differences between a more senior engineer and a more junior one is the ability to mentor.

Re:What I learned working with a senior engineer as a new grad by dijit on Friday August 19, 2022 @06:05AM (#32519216)
> nothing above senior.

Title inflation dictates that there is and inevitably will be.

If you’re senior after six years, and you’re staff after 12 then eventually people will be staff after 7 years and there will be a new title above that which takes 12 years to get (principle?).

I haven’t seen a junior in 10 years, I haven’t seen an intern in longer. People seem to come out of school into “mid” level roles - which means the mid levels are actually entry levels and the titles shift down.

Re:What I learned working with a senior engineer as a new grad by chrisan on Friday August 19, 2022 @06:52AM (#32519472)
Maybe on a "does it compile" and "does it work" level you might be the same as a fresh grad, but I'm sure you have years of experiences that help you make decisions and think of possible pitfalls. Plus each new language over the years is easier and easier to pick up.
Re:What I learned working with a senior engineer as a new grad by chrisseaton on Friday August 19, 2022 @06:20AM (#32519289)
> there is nothing above senior

Staff, senior staff, principle, distinguished, architect, etc?

Re:What I learned working with a senior engineer as a new grad by j7ake on Friday August 19, 2022 @06:16AM (#32519268)
In many hard sciences, 6 years is graduate school.
Re:What I learned working with a senior engineer as a new grad by chrisseaton on Friday August 19, 2022 @06:23AM (#32519305)
If you go to graduate school then your first job is ‘senior’ because by that point you’re a world-expert in your field.
Re:What I learned working with a senior engineer as a new grad by OJFord on Friday August 19, 2022 @06:21AM (#32519294)
And a PhD would be senior to a graduate?

Also the quote is 'professional', so although it's probably not the case, it doesn't preclude spending your 6 years in 'graduate school' beforehand anyway.

Re:What I learned working with a senior engineer as a new grad by badpun on Friday August 19, 2022 @06:56AM (#32519503)
After PhD, people are forced to do postdocs, which are nominally junior positions.
Re:What I learned working with a senior engineer as a new grad by OJFord on Friday August 19, 2022 @07:43AM (#32519809)
But not compared to the new grad/undergraduate intern washing petri dishes or whatever. My point is that what you label 'junior' doesn't matter, it's all relative.
Re:What I learned working with a senior engineer as a new grad by chrisseaton on Friday August 19, 2022 @07:04AM (#32519563)
> After PhD, people are forced to do postdocs

You don’t have to do a postdoc.

Re:What I learned working with a senior engineer as a new grad by goodpoint on Friday August 19, 2022 @08:58AM (#32520411)
In most engineering it takes 15 if not 20 years. Otherwise the term "senior" gets completely watered down.
Re:What I learned working with a senior engineer as a new grad by foobarian on Friday August 19, 2022 @09:35AM (#32520761)
Many software companies have official ranks where "senior" is a step up after "junior," to be followed by "principal," "senior principal," and/or "staff." "Staff engineer" may not sound as impressive as "senior" to a layperson, but at say Google those people are like minor deities.
Re:What I learned working with a senior engineer as a new grad by goodpoint on Friday August 19, 2022 @02:12PM (#32524344)
"principal" and "staff" are even more vague than "senior" and exist only in few companies. More importantly, they almost never refer to total experience and instead refer to being promoted within a given company.
Re:What I learned working with a senior engineer as a new grad by neilv on Friday August 19, 2022 @06:23AM (#32519307)
For software developers, I've thought 5 years of solid work and continuous learning is about the right time horizon for a senior title, in a typical contemporary software/internet company. (At least, 5 years of seeing the lifecycle through awhile -- not job-hopping repeatedly, before getting to see cause and effect together.)

I could even see that going faster than 5 years, especially in a startup. For example, say one of your early hires is fresh out of school, but really curious and learning fast, already did some open source, learns from mentoring/osmosis, takes easily to a team sensibility, and has to tackle a lot of things like is the norm in a startup. Within a couple years, as the startup is starting to think about titles more, they might be a battle-scarred veteran with firsthand experience and maturity beyond their years. (Or, even if not everything is yet the complete senior package -- such as maybe they've only worked on one system and team, and could've overlearned from limited data points -- you want to acknowledge the value of their contributions, as well as their institutional memory and cultural role. So maybe help them level up any aspect they haven't yet had a chance to.)

(BTW, I avoid the term "professional engineer" when talking about software, because I've heard it have special meaning in the more regulated, traditional engineering disciplines.)

Re:What I learned working with a senior engineer as a new grad by jbreckmckye on Friday August 19, 2022 @06:37AM (#32519369)
I absolutely cannot agree with this.

It's true that after five years in a startup, you'll have seen lots of systems. But being a senior practitioner requires deep experience as well as breadth, and enough time in the industry to recognise larger trends.

There is no magic mark for this, and it's quite possible to reach ten years and still be a weak practitioner, because you were exposed to a narrow range of problems and were never around to see your bad decisions bear bad fruit.

However, the opposite does not hold. It doesn't matter how intelligent you are, you can't short circuit repeated experience and the mix of breadth and depth required. People want to. I wanted to. But I didn't: all I became was an overbearing mid who had the rhetoric (and the OSS contributions!) to convince others I knew what I was doing. There is absolutely no comparison between myself in 2017 and myself in 2022, but we both have a job title of "Senior Engineer".

In fact, I think that in the long term the trend is for the senior bar to get _higher_. This is pushed by two things: firstly, that the technical domain gets harder, software becomes more abstract, our expectation of engineers increases particularly in "left shifted" environments where every IC must do everything from frontend to microservices to infra to security to testing.

The second force is demographic: as IC salaries have increased, there has been less pressure for senior engineers to exit in favour of the management track. That means more experienced engineers on average. Industry needs a way to describe these practitioners, beyond "very senior", and overall the range of skills of ICs will widen. Under those conditions the definition of senior engineer gets more exclusive, not less.

Re:What I learned working with a senior engineer as a new grad by neilv on Friday August 19, 2022 @07:56AM (#32519895)
Good point about the increasing demands on Seniors in some regards. (The role might also be changing, such as juggling lots of high-level abstractions and vendor bureaucracy in many domains, with a significant amount of Stackoverflow consultation, rather than lots of experience in lower-level details.)

I'm trying to reconcile meaningful titles with current industry norms.

I'm open to other schemes, but, FWIW, this is my current rough idea:

* First is some kind of new college grad. Some of whom would object to Junior in their title, and I think Technician sends the wrong message about near-term goals, so I'd just call it plain Software Engineer.

* After maybe at 1 or 2 years, they've been through some projects, and they know a lot of the mechanics (big contrast to a new-grad who learns as they unlearn what they got from bloggers). You want to acknowledge that, so maybe it's Software Engineer II.

* At some point, maybe it's 5 great years in, they've seen a lot of stuff, and gotten wisdom and insight, and Senior sounds about right and conventional. This could be a plateau title that someone has for a decade, even as their TC increases quite a bit.

* Staff and Principal engineer roles transcend project teams (more than Seniors do). Large companies will each have their own definitions, and there might also be unwritten meaning. (At my first hardcore software engineering employer, there was no Staff, and only a tiny percentage ever made Principal. By the time I made Senior, the VP asked me where I saw myself in 5 years, and I said Principal... He gently set expectations that that's pretty ambitious, only a few people ever do it, and 5 years would be very fast. Correct on all points, and now I think I have a better idea of how much more the Principals knew that I didn't even know were things to be learned.)

Re:What I learned working with a senior engineer as a new grad by treis on Friday August 19, 2022 @10:24AM (#32521333)
I don't think I've seen anyone provide a workable system where senior is reserved for people around 20 years of experience. What's that structure look like? Everyone from 1-20 years experience has the same title?

There's definitely inflection points at years of experience:

0: Good enough to be hired

1-3: Solid team contributor

3-5: Best IC on a team

5-8: Lead a project/team

8+: Lead multiple projects

Then from there it's increasing complexity of teachnical problems and project size.

If you're insisting that senior applies only to the last level what do you call all those steps between 0 and 8.

Re:What I learned working with a senior engineer as a new grad by ckdarby on Friday August 19, 2022 @06:43AM (#32519400)
It is just title inflation. A senior is one who has graduated apprenticeship and is equipped with technical knowledge to begin training an apprentice.

Are there those who are masters of their craft who call themselves a senior, of course.

Re:What I learned working with a senior engineer as a new grad by lopkeny12ko on Friday August 19, 2022 @07:24AM (#32519690)
Yeah, I stopped reading after this line. Sorry, but if you call yourself "senior" with 6 years of experience you've lost all credibility in my book.
Re:What I learned working with a senior engineer as a new grad by MikeTheRocker on Friday August 19, 2022 @01:12PM (#32523633)
Much of the most widely used software in the world comes out of mid 20s so-called Senior Engineers in Silicon Valley (and other major US metros). Gatekeeping on the basis of years of experience is naive and unproductive.

IMO "senior" is a function of behavior not time. At FAANG, levels are formally defined by traits. For example, a senior engineer can plan and lead 6-12 month long projects, delegating some parts of the implementation to others where appropriate. I personally was fulfilling this definition at 25 and I know several dozen others in similar situations.

Re:What I learned working with a senior engineer as a new grad by pcthrowaway on Friday August 19, 2022 @09:34AM (#32520742)
Years of professional experience isn't a great metric of time steeped in software practices. There's a difference between someone who did a bootcamp and worked for 6 years compared to someone who started contributing to open source software at the age of 12, studied computer science, and then went into the industry. The latter might be more experienced at 1 year than the boot camp grad at 6 years.
Re:What I learned working with a senior engineer as a new grad by throwaway4233 on Friday August 19, 2022 @07:59AM (#32519920)
Seniority is the fact or state of being older or higher in rank or status than someone else. Within an organisation, a senior engineer could be the engineer with the most experience with the codebase everyone else is working on.

I do agree that certain habits or experience from working for additional years might be missing, but as the first engineer of a codebase, IMO, there will always be something to learn from them. Which makes the article credible enough to warrant a read.

Re:What I learned working with a senior engineer as a new grad by runevault on Friday August 19, 2022 @11:05AM (#32521901)
I wouldn't instantly go that far. There are people who can be senior in 6 years. People truly that good are the exception, not the rule though.
Re:What I learned working with a senior engineer as a new grad by wink on Friday August 19, 2022 @07:47AM (#32519844)
The author said that, we don't know if the mentioned person does it.
Re:What I learned working with a senior engineer as a new grad by thom on Friday August 19, 2022 @08:22AM (#32520100)
I suspect 'Senior' most places just means 'more senior than at least one other person'.
Re:What I learned working with a senior engineer as a new grad by dom96 on Friday August 19, 2022 @06:41AM (#32519383)
There are senior engineers out there that have <4 years professional experience. I myself went from IC3 (junior) to IC5 (senior) at FB in around 3 years and this is pretty common at FB from what I've seen.
Re:What I learned working with a senior engineer as a new grad by kasey_junk on Friday August 19, 2022 @07:58AM (#32519914)
I think the concern is that the industry, including Facebook, has decided that the designation “senior” is a thing you can get in <5 years. It’s a norm in software so it’s easy to see examples of it, and in practice who cares what the titles were if they are used consistently.

But what if you were outside the industry and heard that term? A senior judge typically has decades under their belt. A senior chief petty officer is the second highest non-commissioned rank in the navy implying a whole career behind them. They might infer it only takes three years of experience to reach the near top of the software craft.

Re:What I learned working with a senior engineer as a new grad by joshuamorton on Saturday August 20, 2022 @12:09AM (#32528983)
> A senior judge typically has decades under their belt.

A senior judge is also quite literally a semi-retirement role. You take on reduced workload.

> But what if you were outside the industry and heard that term?

"Senior Associates" in the legal profession are junior/mid roles, similarly, senior account managers etc. aren't particularly senior in most places. In white collar roles, a "senior" is really just a distinction of independence and reliability.

Re:What I learned working with a senior engineer as a new grad by polio on Friday August 19, 2022 @08:59AM (#32520418)
It feels similar to the title bloat of Goldman Sachs, where a lot of people are Vice Presidents.
Re:What I learned working with a senior engineer as a new grad by kasey_junk on Friday August 19, 2022 @10:21AM (#32521294)
In certain regulated or audited environments you’ll see rules like “only a person at the VP level or higher can make decision xyz”.

It’s just as stupid but there is a different reason for it.

Re:What I learned working with a senior engineer as a new grad by Cwizard on Friday August 19, 2022 @05:29AM (#32519020)
I’ve worked with some consultants that were ‘senior’ after 2-3 years of experience. I think there are two reasons for this trend: giving some a senior title can sometimes mean you have to pay them less (paradoxically perhaps) because they feel they are more important now, second consultancy agencies can ask higher rates for ‘seniors’.
Re:What I learned working with a senior engineer as a new grad by mudrockbestgirl on Friday August 19, 2022 @06:07AM (#32519228)
Easy to be a senior frontend engineer. Just say you were already around when the current most hyped JS framework was released that everyone must move to, 1-2 years ago.
Re:What I learned working with a senior engineer as a new grad by ReadTheLicense on Friday August 19, 2022 @06:57AM (#32519509)
You mean like React (9 years ago), Angular (12 years ago) or Vue (8 years ago)? Who seriously uses anything else?

I think you confused the JS ecosystem with the C# one.

Re:What I learned working with a senior engineer as a new grad by jaywalk on Friday August 19, 2022 @07:42AM (#32519805)
Angular will turn 6 years old next month. You're thinking of AngularJS, which despite the (unfortunately) similar name and parent, is basically a completely different framework.

Although I don't see why you're bashing C#. Despite the .NET Framework > .NET Core > .NET transitions, it's not really that different. There's a ton of new functionality and ways to do things, but for the most part the old ways still work too.

Re:What I learned working with a senior engineer as a new grad by tester756 on Friday August 19, 2022 @07:26AM (#32519713)
>I think you confused the JS ecosystem with the C# one.

What do you mean?