7

So in my org, as far as I can see, senior engineers and normal engineers do about the same amount of work, and the senior engineer is useful at PBRs for bringing up tech points that other engineers might not know about due to lack of experience. Is this a common thing across the whole software business? In terms of responsibilities, I’m seeing pretty much the same amount, don’t wanna sound arrogant here but we never task work etc based on seniority which I like but just want to know if it’s common

Comments
  • 6
    I'd say very common.

    When I was starting I got arrogant when I saw I was doing the same work as the seniors or even the team lead. With time, I found out two things: my seniors were incompetent (or the work is easy, at best) and that seniority is not about technical skills alone.
  • 1
    @rantsauce ah fair enough, thank you!
  • 1
    Yes. Of course everyone works for the same amount of time. Do you expect seniors to work day and night?
  • 1
    @Ikaroz individual development/growth is Super important to me. The more time you spent in a project, the better chances to grow you got. If you can't or don't want to grow, you can get overtaken easily.

    This doesn't take the level of competence at the time you join the project fully into account,though.

    I saw people joining few years after "the seniors" which are telling them now, how things need to be done 🙂
    Guess this relates to the company and team values/spirits
  • 0
    @electrineer I expect them to work less in fact because they might not struggle as much with common problems, or know common terminology at the very least. My previous senior engineer thought serialization was only DB related and grilled me for using that word for a JSON related function........
  • 0
    @Ikaroz yeah I don't blame them too much but at the same time you HAVE to keep up with times otherwise you're not qualified imo
Add Comment