Honestly, the longer I work in tech, the less confidence I have in anyone’s title. Even searching for a job, different companies have different ideas of what, pretty much everything is…
I’m more on the side of IT support (sysadmin/netadmim/systems engineer/network engineer/second/third level support/engineer/whatever tf)… And even looking for a job for myself, it’s a nightmare… Even mundane details about the job are messed up. I saw a posting for a “remote support technician”, by their definition, this was “remote” as in, not from an office. The job was on-site support for remote sites. I don’t even think it was an IT position, more like mechanical maintenance IIRC. So you were “remote” aka, not at their office, doing support (for something not electronic), as a “technician”.
It’s bullshit all the way down.
When I was last looking for a job someone commented that I had “only” applied to x positions in y weeks, when their search for (some vague title related to my usual employment) had z search results, where z was more than 10 times x. I didn’t bother replying but I couldn’t help but think, did you look at any of those postings? I literally had a search filter for jobs that was “CCNA” (Cisco certified) and I literally had administrative assistant positions coming up… Those are little better than secretarial jobs. I know because I clicked on it because maybe, just maybe they meant an assistant to the systems administrator, but no, it was exactly what it said on the tin.
This is my frustration with IT. There are zero standards for what a job is. Developer? Is it software or something related to construction? Engineer? Are you examining the structure of something or building out IT solutions? Admin? Office admin? Systems admin? Department admin? There’s too many “admin” related jobs… “Support”? Supporting what exactly? Am I programming switchports, or is this some other kind of bullshit support.
That’s not even getting into all the actual IT jobs that are clearly out in left field. Sysadmin jobs that require years of experience with an application that’s extremely specific to one industry; an application you could learn likely in a matter of days, which isn’t very complicated, but your resume goes in a bin if you don’t have some very specific certification and a number of years of experience with the related app… I know that because I’ve applied to such positions and didn’t even get a courtesy email telling me to pound sand.
Which takes me to another point, you don’t get rejected. You get ghosted. They don’t want you? Fine, tell me that. You don’t even have to give me a reason, just some copy pasta about pursuing other candidates. That way I will know to not expect anything further, and keep trying. I mean, I’m going to keep trying no matter what, but still…
The whole job market is a hellscape.
Then, I can turn my attention to the pointless titles people have, which often don’t mean shit outside of your specific workplace. “Lead customer success technician” … Ok, wtf is that? What does any of that mean? Are you technical in the sense of working with information technology? Or is it one of the DOZENS of other “technical” things? Everyone is a technician and everyone is an engineer now. Those terms used to mean something. Now they’re just keywords to blast your resume with to try to match some AI filter so you can get a call. If you don’t play the game, your left behind.
I feel bad for all the professional engineers out there who hold degrees in real engineering. Now anyone, everyone and their mother is calling themselves some kind of engineer. It’s all word salad and I hate it.
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.
Honestly, the longer I work in tech, the less confidence I have in anyone’s title. Even searching for a job, different companies have different ideas of what, pretty much everything is…
I’m more on the side of IT support (sysadmin/netadmim/systems engineer/network engineer/second/third level support/engineer/whatever tf)… And even looking for a job for myself, it’s a nightmare… Even mundane details about the job are messed up. I saw a posting for a “remote support technician”, by their definition, this was “remote” as in, not from an office. The job was on-site support for remote sites. I don’t even think it was an IT position, more like mechanical maintenance IIRC. So you were “remote” aka, not at their office, doing support (for something not electronic), as a “technician”.
It’s bullshit all the way down.
When I was last looking for a job someone commented that I had “only” applied to x positions in y weeks, when their search for (some vague title related to my usual employment) had z search results, where z was more than 10 times x. I didn’t bother replying but I couldn’t help but think, did you look at any of those postings? I literally had a search filter for jobs that was “CCNA” (Cisco certified) and I literally had administrative assistant positions coming up… Those are little better than secretarial jobs. I know because I clicked on it because maybe, just maybe they meant an assistant to the systems administrator, but no, it was exactly what it said on the tin.
This is my frustration with IT. There are zero standards for what a job is. Developer? Is it software or something related to construction? Engineer? Are you examining the structure of something or building out IT solutions? Admin? Office admin? Systems admin? Department admin? There’s too many “admin” related jobs… “Support”? Supporting what exactly? Am I programming switchports, or is this some other kind of bullshit support.
That’s not even getting into all the actual IT jobs that are clearly out in left field. Sysadmin jobs that require years of experience with an application that’s extremely specific to one industry; an application you could learn likely in a matter of days, which isn’t very complicated, but your resume goes in a bin if you don’t have some very specific certification and a number of years of experience with the related app… I know that because I’ve applied to such positions and didn’t even get a courtesy email telling me to pound sand.
Which takes me to another point, you don’t get rejected. You get ghosted. They don’t want you? Fine, tell me that. You don’t even have to give me a reason, just some copy pasta about pursuing other candidates. That way I will know to not expect anything further, and keep trying. I mean, I’m going to keep trying no matter what, but still…
The whole job market is a hellscape.
Then, I can turn my attention to the pointless titles people have, which often don’t mean shit outside of your specific workplace. “Lead customer success technician” … Ok, wtf is that? What does any of that mean? Are you technical in the sense of working with information technology? Or is it one of the DOZENS of other “technical” things? Everyone is a technician and everyone is an engineer now. Those terms used to mean something. Now they’re just keywords to blast your resume with to try to match some AI filter so you can get a call. If you don’t play the game, your left behind.
I feel bad for all the professional engineers out there who hold degrees in real engineering. Now anyone, everyone and their mother is calling themselves some kind of engineer. It’s all word salad and I hate it.
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.