I'm an "Associate Software Engineer". As far as I know, it's totally arbitrary. I had to check our directory to confirm it. 🙃 To me it means junior-ish developer, and I believe that's what the intention is, too.
It sounds great to me, but I also don't really have a stake in my title. We're also a small team and I'm sure amongst us, it doesn't really matter. I'm guessing titles matter in bigger companies that have a larger organization structure.
Officially, "Lead Developer" because my boss gave it to me.
Usually, if anyone asks me, I say either "developer" or "web developer." Any distinction beyond that (e.g. junior, senior, etc.) is highly subjective, so I tend to avoid them.
I don't think it should. Maybe there's some arbitrary rule or for sure there's conventional biases and years of interviewing to immediately rule out non-degree holders, but hey, you're already in the company! Go for it! From experience, degree has zero sway once you're in the door, it's more about your contribution, how well you know the company and its path (you can't move up if you're not aware of what they're looking for), and sometimes you have to ask!
For that reason, I was once a "Digital Application Specialist." It was something I just made up, because it had to include the word "digital" (since our dept. handled digital marketing) but couldn't have the word "developer," because we weren't in IT. Developers were also exempt (salaried), and I was not.
“Digital Developer” because I fought to get a promotion and leave my old title of “Jr. Digital Developer” ;)
At the agency I work at, devs go by "Digital" developer versus "Frontend"/"Web"/"Backend" mostly because most of us work across the stack, and even into traditional DevOps and/or Database admin territory.
I'm really put off by he use of "digital" in titles. Everything we do with computers is digital at some point, so I'd rather take the word back and use it exclusively for people who make things with their fingers.
N/A
Because dev jobs around here are as scarce as unicorns! Also because remote teams won't trust juniors to be able to control themselves and deliver as if they were in place, for some reason.
Don't get me started on relocating.
I'm freelancing, right now. So, I guess "Mercenary Developer" suits me better.
Front-end engineer. This is the title in my contract, so this is what I display on LinkedIn. I don't like the engineer part because although I have a CS degree, I do not have an engineering degree. I'm literally not an engineer. So usually I just tell people I'm just a dev or web developer.
Having said that, that's my title because I work on the front-end of our product (React/Redux, TypeScript, HTML/CSS), but we also do node on the back end for some things (small rest APIs). I'm also starting to become familiar with Docker/K8s. Maybe I shoud become a "digital developer" like Geoff.
“Digital Developer” because I fought to get a promotion and leave my old title of “Jr. Digital Developer” ;)
At the agency I work at, devs go by "Digital" developer versus "Frontend"/"Web"/"Backend" mostly because most of us work across the stack, and even into traditional DevOps and/or Database admin territory.
It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
Until last week it was data architect: I was responsible for envisioning how applications would store and use information, designing schemas and pipelines, and implementing data access layers. It was only one of the hats I actually wore (I did regular application development, managed builds and deployments, and ran process on the side), but it was the one I was most interested in.
Now I'm a site reliability engineer, which appears to be the hot new thing as people come to grips with development and operations having more to do with each other than not. The company is focused on data so I'm still going to get to do that, but with more of a focus on scale and infrastructure.
Overall, titles don't matter unless they reflect specialization.
Oldest comments (52)
I'm an "Associate Software Engineer". As far as I know, it's totally arbitrary. I had to check our directory to confirm it. 🙃 To me it means junior-ish developer, and I believe that's what the intention is, too.
It sounds great to me, but I also don't really have a stake in my title. We're also a small team and I'm sure amongst us, it doesn't really matter. I'm guessing titles matter in bigger companies that have a larger organization structure.
Officially, "Lead Developer" because my boss gave it to me.
Usually, if anyone asks me, I say either "developer" or "web developer." Any distinction beyond that (e.g. junior, senior, etc.) is highly subjective, so I tend to avoid them.
I've never really cared for titles though. :)
"Web Developer," because I don't have a degree.
Do you think the lack of a degree would make it harder to move up in the company, if you wanted to?
Feel free to not answer if your company is watching. 👀
I don't think it should. Maybe there's some arbitrary rule or for sure there's conventional biases and years of interviewing to immediately rule out non-degree holders, but hey, you're already in the company! Go for it! From experience, degree has zero sway once you're in the door, it's more about your contribution, how well you know the company and its path (you can't move up if you're not aware of what they're looking for), and sometimes you have to ask!
For that reason, I was once a "Digital Application Specialist." It was something I just made up, because it had to include the word "digital" (since our dept. handled digital marketing) but couldn't have the word "developer," because we weren't in IT. Developers were also exempt (salaried), and I was not.
Have you considered calling yourself a Spider? :D
Brb changing my title to Spider-Man
“Digital Developer” because I fought to get a promotion and leave my old title of “Jr. Digital Developer” ;)
At the agency I work at, devs go by "Digital" developer versus "Frontend"/"Web"/"Backend" mostly because most of us work across the stack, and even into traditional DevOps and/or Database admin territory.
I'm really put off by he use of "digital" in titles. Everything we do with computers is digital at some point, so I'd rather take the word back and use it exclusively for people who make things with their fingers.
I don't mind it. But when you think about it, we still do make things with our fingers ;)
N/A
Because dev jobs around here are as scarce as unicorns! Also because remote teams won't trust juniors to be able to control themselves and deliver as if they were in place, for some reason.
Don't get me started on relocating.
I'm freelancing, right now. So, I guess "Mercenary Developer" suits me better.
Chief Technology Officer (CTO), because I own the company and started it from scratch
Director of Technology, because "Director" is the title you get at my org when you manage a department and "Technology" because well... Technology.
I like to refer to myself as the Director of Tech-sploration! But I haven't been able to convince them to put that on my card yet.
Trainee
Because... Well... Do I need to explain? :kappa:
Front-end engineer. This is the title in my contract, so this is what I display on LinkedIn. I don't like the engineer part because although I have a CS degree, I do not have an engineering degree. I'm literally not an engineer. So usually I just tell people I'm just a dev or web developer.
Having said that, that's my title because I work on the front-end of our product (React/Redux, TypeScript, HTML/CSS), but we also do node on the back end for some things (small rest APIs). I'm also starting to become familiar with Docker/K8s. Maybe I shoud become a "digital developer" like Geoff.
“Digital Developer” because I fought to get a promotion and leave my old title of “Jr. Digital Developer” ;)
At the agency I work at, devs go by "Digital" developer versus "Frontend"/"Web"/"Backend" mostly because most of us work across the stack, and even into traditional DevOps and/or Database admin territory.
Until last week it was data architect: I was responsible for envisioning how applications would store and use information, designing schemas and pipelines, and implementing data access layers. It was only one of the hats I actually wore (I did regular application development, managed builds and deployments, and ran process on the side), but it was the one I was most interested in.
Now I'm a site reliability engineer, which appears to be the hot new thing as people come to grips with development and operations having more to do with each other than not. The company is focused on data so I'm still going to get to do that, but with more of a focus on scale and infrastructure.
Overall, titles don't matter unless they reflect specialization.