DEV Community

Cover image for What is your biggest 'red flag' when interviewing?
David J Eddy
David J Eddy

Posted on

What is your biggest 'red flag' when interviewing?

Interviews are a two way process (and dont let anyone say otherwise). Organizations need people who can 'do the work'. People 'need to get paid'. Above that is what makes showing up to work a frustrating experience or the best thing we do all day.

The job market is tight these days. Last I checked less than 2% unemployment. Skilled workers are in such high demands organizations have started offering perks that would make the pre dot-com bubble engineers jealous. As such we need to be even more careful and diligent when interviewing organizations.

For me it is the 'Do you perform well under pressure?' Via experience this typically means 'we don't know how to schedule work', 'we have no leverage to push back on business demands', or ' the requirements change every day'. None of which are situations I want to be involved in.

What about you? What are your 'red flags'?

Top comments (36)

Collapse
 
molly profile image
Molly Struve (she/her)

The biggest deal breaker for me is when a company has "set hours" where they expect you to be in the office. I personally am a morning person. I like to be in the office by 7:45am and I do my best work in the morning. Then I head home around 4/4:30pm. Some companies are rigid about the 9 to 5 in the office and that's never worked well for me.

Collapse
 
ben profile image
Ben Halpern

Some companies will tell you you have flexible hours but then shame you for making use of this policy 😓

Collapse
 
kaydacode profile image
Kim Arnett 

Worst case I had this happen - I had to work from home because school was closed. Got a bunch of dirty looks the next day for doing so. So next time school was closed, I brought my daughter to work with me and let her watch TV in the main area. I got even dirtier looks haha! But, what do you want me to do?! I found a new job shortly after this (and a few other instances of BS).

Collapse
 
kaelscion profile image
kaelscion

I've definitely experienced this many times. Just because flexibility (of any kind, not just hours) is offered, does not mean you will be allowed to use them in any way other than "technically". I usually ask what the work day of current employees looks like from person to person

Thread Thread
 
molly profile image
Molly Struve (she/her)

Oooof, nothing is worse than being guilted into the office!

Collapse
 
vinesh178 profile image
vinesh178

Following are few from me

Developers not given admin access on work laptop/desktop.
No flexibility for remote work.
Developer needs to know all technologies under the sun but work will be production support of java 1.4 monolithic application.

Collapse
 
araib profile image
Araib

Lol on that last one. I totally understand that feeling 😂

Collapse
 
damnjan profile image
Damnjan Jovanovic

Whenever I hear from the company ”we don't have too many tests because we don't have time.” thousands of my brain cells died.
But what is a real deal breaker for me is ”We need it fast.” = ”We expect you have a switch in your brain for normal and turbo mode, and you can perform x time faster if we ask you to x time speed up.” In other words, famous sentences like ”Two weeks is too long for this; we need it in 3 days, we have to make it.”

Collapse
 
david_j_eddy profile image
David J Eddy

"...Whenever I hear from the company ”we don't have too many tests because we don't have time.” thousands of my brain cells died. ..." Truth!

Collapse
 
kaelscion profile image
kaelscion • Edited

In my area I've actually had a couple of interviewers commend me on "interviewing then as hard as they did me". Not all interviewers appreciate this and that is a red flag to me. I personally feel that the interview is not just where a company finds out of they want to on board, but also for you to find out if you want to work there. If the interviewers start squirming under questions about company culture (especially if they've recently been acquired), work schedule flexibility, how conflict is handled and what the "chain of command" is, who is responsible for what, etc I begin making for the door.

I look for traits in hiring managers like accountability, honesty, directness, candor, and response to having questions asked about why they do things the way they do. If I see evasiveness or catch dishonesty, I walk away. That is why doing some "recon" on your company of choice is so important. Check their reviews on Glassdoor and actually read them, look at the profiles of them employees on LinkedIn and Twitter, Google news about them and read the articles that result. You need to do this because trust me, they are doing that to you.

It's a two way street all the way. They need to prove they are worthy of your excellent skillset, passion, and love of the craft just as much as they need to prove you are worthy of a paycheck. In my eyes, you can get a paycheck anywhere, but there is only one you. They need to earn you.

Collapse
 
david_j_eddy profile image
David J Eddy

So very true. Interviews are two-way. They want your talent, you want there benefits. It has to work for everyone involved.

Collapse
 
steelwolf180 profile image
Max Ong Zong Bao

I think when they say "We work in a waterfall model for our software development". I will always run away from them since if they are following it just means that they might be stuck in the stone age in their practices or technology.

Especially you're doing work that is focusing on creating new product or services and you will only be finding your code being deployed in donkey years which is not a company I would want to be part of.

Collapse
 
webreaper profile image
Mark Otway

Funny. One of my red flags is "we're a totally agile shop". 😁

Collapse
 
sturzl profile image
Avery

Why? Because of teams who claim it but really aren't, or maybe dogmatic and inflexible leadership?

Thread Thread
 
webreaper profile image
Mark Otway

Probably both. 🤣

Thread Thread
 
steelwolf180 profile image
Max Ong Zong Bao

Yeah, I agree with Mark on that since being dogmatic and inflexible is something that will hurt the moral in the company regardless if they embrace either agile or waterfall method.

I had been in the military, it's really bad when your superior or the organisation has that culture which will snuff out the creativity of an individual contributor.

Collapse
 
helenanders26 profile image
Helen Anderson

Much like the 'Must be willing to work under pressure' red flag, I always find it weird seeing job ads for data analysts that say 'must thrive on chaos' or 'loves juggling multiple tasks'.

I cannot think of a single data analyst ever who loves a chaotic environment with lots of change and requests coming from multiple places.

Collapse
 
perigk profile image
Periklis Gkolias

Another one that had seen when I was looking for a job last year was: 'Working in the nanoseconds zone'. I believe it fits into the "we are disorganized and dysfunctional multitaskers but for reason proud for that" category too.

Collapse
 
david_j_eddy profile image
David J Eddy

It seems the 'loves juggling multiple tasks' or similar is being applied pretty liberally around IT these days.

Collapse
 
phallstrom profile image
Philip Hallstrom

Interviewers that clearly haven't even looked at my resume/cv/etc and have no idea who I am or sometimes what I'm even applying for.

Collapse
 
dfockler profile image
Dan Fockler • Edited

Most of my red flags are just bad interview practices. Not following up with me for months after an interview, holding 8 person panel interviews.

My biggest red flag is if the direct manager and I don't get along. This is the person who is going to make or break your team and if they are flaky or angry or incompetent, it's most likely the team who will get thrown under the bus.

Collapse
 
xtrasmal profile image
Xander • Edited

I walked around to check out the dev-team. Had a quick talk, so that I knew what I would sign up for.

This developer had his code-editor open and I looked at his controller, where there was this mulit nested Hadoken terror foreach loop.

I said: "Well, a lot of stuff happening over there!"
He said proud: "Yeah, nice or what"

Later I talked to the lead and senior developer and found out that he was a senior, because he worked there longest. So yeah.. super lol. But I needed work, so I took the job.

Collapse
 
david_j_eddy profile image
David J Eddy

How did that work out for you? Where you able to implement better coding standards? Best practices? Bring positive change to the team?

I see this as a challenge but also an opportunity to help improve a team.

Collapse
 
xtrasmal profile image
Xander

The snowboard trips were nice, the parties were great. Nice people and good co-workers.
All were willing to learn. So we added Sonar-Qube for code quality, implemented and iterated on scrum practices, with retrospectives and bi-weekly lightning talks to improve the team and incite continuous learning.
BUT I never got technically satisfied or inspired by co-workers.

Collapse
 
grmnsort profile image
German Rodriguez Ortiz

When I got my current job, the listing had the classic "must be willing to work under pressure", they've recently added "must have heroic spirit" and "rockstar mentallity"

And I'm not sure if they have any idea about both concepts, but I've read that those are things NOT to look for :(

Collapse
 
david_j_eddy profile image
David J Eddy

Thank you for those. Adding them to my list of 'avoid' phrases.