you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 2 years ago (3 children)

The reality is also, that development is so extremely diverse, that it's hard to find umbrella-enough terms to describe a job.

For example, I'm a senior software developer on paper.

I'm not senior, not even 10 years job experience. But I seem to be rather good at what I'm doing, so I'm a senior now.

I'm also hardly writing any code. I talk to customers about what they want their software to do, I talk to management about how many people I need, I review pull requests, I talk to junior devs about their problems, etc, etc. Maybe 10% of my time is actual code. But what title other than "developer" should I have?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 2 points 2 years ago (2 children)

    A few more titles that you will hate, but actually describe your role. You are in no sense just a senior developer.

    You are an

    • Architect
    • Solution Architect
    • Project Manager and Team Leader
    • Service Manager

    Which one fits best, you have to decide. But i would put this up on my resume if i had your responsibilities.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 2 years ago

    Yeah, I struggle with that.

    • I’m not allowed to be called an Architect because the Lead Architect only allows product people in the role, however I’m equivalent rank.
    • I spend way too much time doing project management, but I despise that
    • I don’t lead a specific team or have people but I set requirements for engineering and sometime borrow people from teams
    • I’m in the Quality Engineering organization but don’t do QA
    • some people think I’m a Build Engineer, and I do set some of their requirements
    • some think I’m AppSec, and I do try to fill their gaps and apply their work to the organization.

    Recently, maybe DevSecOps sounds most accurate, and I avoid talking rank so I don’t piss off that Prima Donna

  • source
  • parent