Thisarticlewas originally published on.cultbyMikaella C. .cult is a Berlin-based community platform for developers.
The job posting looked great.
The company is interesting.
The role offers you a challenge youre excited to tackle.
But there are also some specific warning signs fordeveloperson the hunt for a new role.
In this article, well tell you what to watch out for!
Haha, yeah, we work a lot
Its no surprise that developers often end up putting in overtime.
Its a demanding job, and sometimes youll have a stressful or busy week or month.
But watch out for companies who seem to imply that constant overtime is just part of the job.
40% off TNW Conference!
Aim to get a clear, satisfying answer about how many hours are typical.
Maybe its not your role thats challenging, but the companys management style.
Ask your interviewer exactly what about the role is challenging.
Sometimes trendy jargon is just that: trendy.
Get deep into the technicalities.
But theyre not the only part!
That makes for a lot of fights in meetings or unpleasant lunches.
Of course, thats completely fine!
And remember, a team who doesnt talk to each other is never going to get anything done.
This could be a sign of arrogance or lack of flexibility in the workplace.
For most developer roles, there will be at least one developer whos part of the interviewing team.
Dont be sucked in by a smiling face that isnt going to give you real insights into the team.
But always feel free to ask.
If your interviewer cant explain the companys vision, purpose or goals, you might be running into trouble.
A developers role is to build the technology that enables a companys USP.
Youre a developer, not a mindreader!
Could you break it down for me?
If possible, ask another person in the hiring team or the company.
And if youre still struggling to understand, it might be time to reevaluate.
The ten-year-old company that is still a startup
Look, we all love startups.
Maybe the product has expanded so much and so wildly that its tough to add new features.
Maybe there are thousands of old bugs that you cant dismantle without taking the whole product offline.
Either way, it could be a balancing act rather than a chance to build.
Ask your interviewer what the past decade has taught the company.
Ask them why theyre still self-defining as a startup.
Ask what the path for the future looks like.
As youre being led to the interview room, take a look around: how do people look?
Where do the developers work, and is it an office set-up youd be comfortable in?
How does the company make their workers feel welcome even in a situation where you dont physically work together?
And what are their plans for the future?
Why not ask something simple like, Could you describe a typical working day at your company?
See if the interviewer mentions regular team check-ins, lots of meetings, company coffee breaks, and more.
Watch out for anything that would make your daily life much better… or much worse!
Go forth and interview!
Story by.cult
.cult by Honeypot is a Berlin-based community platform for developers.
