DEV Community

Cover image for 7 Key Red Flags To Watch For In Software Job Listings
Maddy
Maddy

Posted on • Originally published at techwithmaddy.com

7 Key Red Flags To Watch For In Software Job Listings

I've been going through an interview loop, applied for dozens of jobs and interviewed at several companies (both big and small).

Reading through job descriptions is the funniest part of the job hunt!

This article will show you some signs you need to look out for when job hunting for your next software job.

Let's start.

First of All: Who Writes Job Descriptions?

According to an Indeed survey, the three most common people involved in writing job descriptions at small businesses are hiring managers (35%), owners/CEOs (29%) and HR departments (24%).[Indeed]

Many of these people have a non-technical background.

What Are Key Signs You Need to Watch Out for in Software Job Listings?

#1 “We’re a Family”

I always get a bit concerned whenever I read the word "family" in job descriptions.

Now, there's nothing wrong with having great relationships with your colleagues and engineering manager.

I believe a company has a healthy culture when colleagues consider each other more than colleagues and friendships are formed outside of the workplace. Often, promotions are more about the relationships you have with other people.

But remember that a company is a business.

A company can decide to lay off their employees if it's needed for business reasons.

An article from Harvard Business Review explains brilliantly why picturing a company as a family is a red flag:

  1. Thinking of a company as a "family" leads employees to forget about personal boundaries and get attached to the company.

  2. Being too loyal does more harm than good: it may lead engineers to work more hours.

  3. As I mentioned before, a business, if needed, will have to let someone go. In a company that brands itself as "family", this decision can be taken personally.

2. Being Able To Multi-task

Being able to multi-task is another potential red flag to look out for.

Software engineering in itself is already a multi-faceted role.

"Multi-tasking" invites the idea of having to take on roles that are outside of your scope.

Often, employers want software engineers to be able to carry out multiple tasks (and sometimes other roles) with no pay variation.

2. Work Under Pressure

This one is probably the one which I cannot stand the most.

Let's clarify that companies often have periods in the calendar year when things need to go faster than other times. This is normal and expected.

However, if a company lists "being able to work under pressure" as a requirement, my concern is that that's how the company operates. It's the standard.

You might want to look out for this and ask questions when speaking with the recruiter.

3. Hit The Ground Running

hit-the-ground

"Hit the ground running" means being able to work at full speed from day one.

This is a sign of a company which:

  1. Doesn't understand the value of a great onboarding experience.
  2. Doesn't understand that getting familiar with a new codebase takes time.
  3. Everyone learns at different speeds.

The problem with a “hit the ground running” mentality is that it celebrates speed over quality. It suggests that a top performer at one company can perform at that same level right away at another. [...][Kate Reilly - LinkedIn]

Related: How To Choose A Software Engineering Job

4. An Emphasis on Working “Very Quickly”

Software engineering is often perceived as a job where you must deliver as much code as possible in the shortest time possible.

If you think about it, there's the "10x Developer" character in this industry, someone who is 10 times more productive than other developers.

Companies that value working "very quickly" are potentially not interested in delivering quality software.

5. "Rockstar", "Guru", "Superstar", "Ninja"

These terms are simply senseless.

To start with, let's ask a simple question: "What's the point of a job title? Or job description?" Quite simply, they're used to label and describe the job that needs doing. Pretty obvious. The key point is that they're not about what you think of the job, they're about what they need to think the job is about.[Certified Hiring]

6. Emphasis on Flexibility

An emphasis on flexibility has nothing to do with the work mode. Meaning how and where you work. In this point, "flexibility" means having to adapt to the constant changes of minds and requirements.

Would you like to work in a place where requirements change on a daily basis?

7. Strong Work Ethic

Technically, there's nothing wrong with having a strong work ethic. Some people are hard workers by nature and genuinely love what they do.

However, this may signal that the company expects you to work 60+ hours per week.

Conclusion

This article described 7 key signs you need to look out for when reading software job listings.

You must have a conversation with the recruiter before deciding not to consider a company.

I hope this article is helpful to you.

Which one of these makes you run away? Let me know in the comments. 😁

Until next time!

🙋🏾‍♀️

Top comments (15)

Collapse
 
panditapan profile image
Pandita

Big red flag:

"We are proud of our 10 step interviewing process that ensures high quality software engineers for our clients."

eh no sorry, I'm high quality* but I'm not going to put up with a 10 step interview process >:V sdjhsks

  • I will not die of low self esteem.
Collapse
 
maddy profile image
Maddy • Edited

My ideal interview length is 3 stages. Maximum 4. Beyond 4 is unacceptable.

Collapse
 
panditapan profile image
Pandita

Definitely, the 10 step process was incredibly dumb. It was something like: recruiter call -> hr meet -> lead pm of project -> code challenge call -> 10min english conversation call -> team meet and approval -> client approval -> one day at the office approval -> and two other ones I can't remember.

It's a great company based on what I know but it's way too many steps. I had two friends that reached the english conversation step and was dropped off. They could've avoided 3 steps if it was done by the recruiter on the 1st step DX

Collapse
 
ypdev19 profile image
Yuli Petrilli

Really good article!
Work under pressure: haha no thank you .__.
A "rockstar", "ninja", "guru"... it's kinda crazy, not so long ago i was trying to get a new job but it shocked me to see a significant amount of posts from companies asking for a developer to have experience with a million things at once. It was a bit difficult not to feel intimidated and frustrated…

Collapse
 
jmfayard profile image
Jean-Michel 🕵🏻‍♂️ Fayard

Wow, I wanted to write a similar article, I'm glad I waited because yours is much better!

Context: I have an ongoing Hiring is broken Series - and many more drafts on the same topic.

Collapse
 
maddy profile image
Maddy

Niiice! I'll have a look at the series. Please go ahead and write your own article on the topic, I'd love to read it! ❤️

Collapse
 
jmfayard profile image
Jean-Michel 🕵🏻‍♂️ Fayard

Thanks. I plan to write that on LinkedIn because that's where recruiters are, so that's what my education efforts can be more fruitful.

Thread Thread
 
maddy profile image
Maddy

Brilliant idea! ❣️

Collapse
 
aarone4 profile image
Aaron Reese

As a contractor....
Posted on a Thursday: 1 phone interview and must be able to start on Monday.
Are you such a disorganized company that you need a warm body in a chair accessing your systems with no time to properly assess suitability or check references? And if so, how much chaos am I walking in to?

Collapse
 
maddy profile image
Maddy • Edited

OMG. Some companies are hilarious, ahaha

Collapse
 
hleivacr profile image
Hugo Leiva

We’re a Family? On my work one of the Managers says "We are in the same boat" and we joke about that. Yes, Right you are in the Penthouse and we are dealing on the Machine Room.

Collapse
 
noriller profile image
Bruno Noriller

Not exactly in the listing, but I receive a lot of contacts from recruiters and always ask a few questions that are things important to me, one of which is how much they are willing to pay.
Since they always say "depends", I added to the template exactly as follows: "(I know it depends, but I'm looking for a range.)".
If they refuse to answer any question, insisting on a call... then it's a red flag that it's gonna be just a waste of time.

Collapse
 
eljayadobe profile image
Eljay-Adobe

HR: What are your salary requirements?

Me: Umm, I suppose $50,000 a year.

HR: Great! We're looking for a Rockstar developer!

Me: Ahhh, in that case $5,000,000 a year.

Collapse
 
maddy profile image
Maddy

I like this ahaha

Collapse
 
kimdontdoit profile image
kimdontdoit • Edited

Enjoyed the read! Thanks

  • Dev Ninja Superstar

Some comments have been hidden by the post's author - find out more