News for hackers. Stuff that matters.
Re:Things I Learned to Become a Senior Software Engineer by bryanrasmussen on Monday September 07, 2020 @08:35AM (#24398996)
I guess the meaning of Senior has changed, that's fine - but what is the level beyond Senior now?

Ancient? Graybeard? Hallowed?

Re:Things I Learned to Become a Senior Software Engineer by psyc on Monday September 07, 2020 @07:04PM (#24403676)
At Microsoft there is a guy named Peter Spiro who I really looked up to, in SQL Server. His official title is Technical Fellow but he called himself Village Elder, because he worked on it since 1.0. In his own words, his job is to float around and be available to everyone in the group.
Re:Things I Learned to Become a Senior Software Engineer by bradleyjg on Monday September 07, 2020 @08:40AM (#24399022)
As a serious answer: staff, principal

As a cynical answer: many companies seem to think that more that 6-7 years of engineering experience is at best a waste of money and at worst counterproductive

Re:Things I Learned to Become a Senior Software Engineer by TheAdamist on Monday September 07, 2020 @08:53AM (#24399082)
Obsolete and let go.

If you can make senior in 2, irrelevance should be right about 5 years in.

Re:Things I Learned to Become a Senior Software Engineer by lllr_finger on Monday September 07, 2020 @09:21AM (#24399237)
In the midwest it's "lead". I've also been on teams where nearly every developer is a lead, which sounds strange, but it's really just a confluence of "could this person lead a team" and pay band.

I've seen the following structure at several orgs:

engineer -> senior -> lead -> staff/principal -> distinguished