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?
It’s not a huge project (3-4 devs, including myself), there’s simply not enough to do for a dedicated architect. PM and SM are done by dedicated roles, but as a lead dev, I obviously have to play translator quite a bit.
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?
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
Which one fits best, you have to decide. But i would put this up on my resume if i had your responsibilities.
It’s not a huge project (3-4 devs, including myself), there’s simply not enough to do for a dedicated architect. PM and SM are done by dedicated roles, but as a lead dev, I obviously have to play translator quite a bit.