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?

[–] [email protected] 4 points 9 months ago

Manager

[–] [email protected] 2 points 9 months ago

Maybe "software producer"? (a term I've never seen used anywhere but that sort of makes sense when you think about what a movie producer does, for example)

[–] [email protected] 2 points 9 months 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.

[–] [email protected] 2 points 9 months 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

[–] [email protected] 1 points 9 months ago

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.