What I learned working with a senior engineer as a new grad
tanishqkancharla.dev
What I learned working with a senior engineer as a new grad
1–10 of 199 posts
Re: What I learned working with a senior engineer as a new grad
#2> 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
#3> senior engineer > been a professional engineer for 6 years Man, the software world is just weird.
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
#4> senior engineer > been a professional engineer for 6 years Man, the software world is just weird.
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
#5> senior engineer > been a professional engineer for 6 years Man, the software world is just weird.
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.
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
#6> senior engineer > been a professional engineer for 6 years Man, the software world is just weird.
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.
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
#7Earlier quoted context omitted.
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.
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.
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
#8Earlier quoted context omitted.
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.
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 professional…
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
#9Earlier quoted context omitted.
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.
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 professional…
> 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
#10> senior engineer > been a professional engineer for 6 years Man, the software world is just weird.
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.