When searching for a job, it can be very easy to fall into the trap of accepting any offer that you get, especially if you’re having trouble even getting a nibble from the whirlwind of applications you’ve sent out. It’s important to diligently consider any job offer before accepting it. Here are a few red flags to look out for when choosing a developer job.
1. The Interview is Only Technical
As a developer, your technical capabilities are of utmost importance, therefore they tend to be the primary focus of interviews. However, if you are not asked any behavioural questions, questions that give the interviewer and insight into the type of person you are...run. People and processes are more important than technology. Your job role extends to more than coding. You will have to collaborate cross-functionally, hold meetings and make plans with other staff members. The people you work with are most important. If you aren’t asked anything about yourself, the likelihood is that no one else that has been hired has had their personality screened either.
2. You Get Offered The Job During or After The Interview
If you’re currently unemployed, this may seem great. In reality, it conveys that the hiring of staff is a low priority to the company. Companies should diligently weigh up their options when filling a position. A quick offer signals that they’re simply hiring someone to fill a vacancy ASAP, increasing the likelihood that you will be undervalued and unappreciated going into the future.
3. Won’t Let You Meet With A Developer
You should always be afforded the opportunity to meet a developer prior to, during, or after the interview, without management supervision. Developers can give you a real insight into the processes of the company and how it really is to work there. If they refuse this, it’s likely their developers are unhappy.
4. Change in Offer
If there is any change in the offer that was advertised or as you discussed, walk away. If a company has already lowballed you at the first afforded opportunity, they’re likely to do it again.
5. Poorly Defined Job Specification
This is a clear red flag indicating that the company is unprepared and not well organised, especially due to the highly technical and specific nature of developer jobs. You may end up performing tasks outside your job description that serve no benefit to your career.
6. Poor Glassdoor Reviews
Glassdoor is an excellent resource for getting the low down on what it’s really like to work for a company. On Glassdoor, current and former employees rate the company, giving their own personal reviews and comments. If the majority of these are negative, stay clear.
7. If The Interviewer Doesn't Sell You On The Job
Interviewers should aim to have all their interviewees wanting the position as it gives them the best opportunity to hire the best candidate.
8. Highly Rigid Start/Break Times
Everyone works differently, especially in the developer world. Tech giants such as Google, Microsoft and Facebook offer flexible break times/working hours, as they have realised the clear benefits that it offers. Companies who strictly enforce start and break times are likely to be less productive and have lower morale.
Posted by Adam Dunne on 24 January 2019
