DEV Community

Cover image for Job Descriptions and Other Works of Fiction
Leon Adato
Leon Adato

Posted on • Originally published at adatosystems.com

Job Descriptions and Other Works of Fiction

Last week I was talking about job applications and not holding yourself back by saying “no” pre-emptively. I started to dive into job descriptions before realizing they deserved their own post. Which is what I’m talking about today.

I’m not going to sugar-coat it: Job descriptions are often a complete work of fiction.

Sometimes, this is because the job description is years out of date – written before the previous employee in that role (or the one before that) had even started. The original responsibilities morphed and changed with the needs of the moment and the skills of the people, but the job description remained unchanged.

Sometimes the job description started out realistically but then HR (or the “AI”-driven tool HR is using) decides to add other requirements to better match similar job descriptions out of standardized databases – which are themselves nothing more than amalgams of job descriptions sourced across time and distance. It’s job-description-by-committee, with no bearing on reality.

Sometimes HR offers a single open req (when 3 are needed) so the manager tries to create a wish-list of requirements and responsibilities, in the hope that someone will come along with most (or at least many) of the boxes checked. It’s a pipe dream, but a frustratingly common one.

Regardless of the reason, the truth remains that many of the job descriptions out there are nothing more than a messy collection of vague hopes, wishful thinking, and out-of-date ideas.

Over three decades an nearly 20 jobs, I’ve lost count of the number of times I’ve shown up for an interview only to discover that the work bore NO resemblance to the requirements on paper. What I find more astonishing is that sometimes the manager knew this was the case, but often they didn’t.

The lesson in all of this goes back to the core message of the last post: In your job hunt, your job is to apply. Don’t second guess whether you have “enough” of the skills, because – as I’ve just explained – the work their need done may be very different.

Do you like the company because of it’s culture, creation, community, calling, or some other aspect? Are you intrigued enough to want to find out more?

That’s all it takes. Apply.

Top comments (4)

Collapse
 
rachelfazio profile image
Rachel Fazio

In your job hunt, your job is to apply.

Happy to see this, job hunting can be so mentally draining, it is helpful to sometimes see how thinking about it in simple terms can help alleviate stress.

Collapse
 
adatole profile image
Leon Adato

Thank you. It (job hunting) is really REALLY hard - especially now, but even in the best of times. And sometimes you just have to take it one step at a time or it all becomes far too overwhelming.

Collapse
 
canro91 profile image
Cesar Aguirre

I’m not going to sugar-coat it: Job descriptions are often a complete work of fiction

Back in the day, at one place where I worked I remember someone from HR entering the Dev room and asking what we used to put in the job description. It ended up being a meaningless list of libraries and tools

Collapse
 
adatole profile image
Leon Adato

It's still like that in a lot of places. either because of the process you describe, or because HR doesn't even bother asking the staff - they just do a search on the job title and strip out every single technical term and put that in the JD.

And that's the point. It goes beyond the now common disclaimer: "we recognize every candidate may not have all the skills listed. if you don't check every box...". It's an almost willful intention to put an utterly unrelated description on a job and just see who applies and use the interview process to figure out what you want the job to be.

Coupled with automated resume scanners, the entire process becomes demoralizing and infuriating.