I’ve written a lot over the last few weeks about preparing and applying for roles, especially for the junior and aspiring developers who are entering the market for the first time. However, what I’ve not really covered is whether or not you should accept the role you’re offered.
There’s always a balance to be struck when that first offer comes. Ideally you want to have a few to choose between. However, personal circumstances may mean you really do need to take the first offer you get but I want to talk a little about what to look for when deciding whether to accept an offer or not.
Pay, obviously is a factor. If you are presented with one offer that is significantly more than another or if the increased cost of the commute would mean you can’t actually afford to take on a role then you should never feel pressured into it. There is sometimes room for negociation here (see my previous post on negociating salary), but it’s always better to set a clear expectation up front than to have a disappointingly low offer.
The next aspect, especially for people new to the profession is the confidence they have in the team, the company, and the hiring manager. For many young people entering a full time job, especially one as technically challenging as software development is one of the biggest challenges they’ll have faced so far. But it isn’t one they face alone. The responsibility for training and onboarding any new employee lies as much with the manager, team, and company as it does with the individual. No one should be thrown at a job, especially a junior one and expected to “get on with it”. They’re going to need help. What you need to establish during your application process is whether you have confidence that the company have the willingnenss and ability to invest in your over the first few years of your career.
Is your hiring manager someone you feel you could go to if you were struggling or worried about your performance? Have they discussed how they plan to train you? I’m encouraged when someone asks what support there is at the company to help and learn, it shows self awareness. It’s not a sign that the person is too inexperienced and I shouldn’t hire them!
Consider asking questions like:
- Does the company have much experience hiring junior developers straight out of university?
- What sort of training plan do you have in place for new starters?
- When do you anticipate I’ll be a fully productive member of the team?
- Will I be assigned a mentor for when I get help?
When you’re being interviewed you should always be asking yourself whether the people interviewing you are people you trust to place the next few years of your career with.
Do you have any suggestions of red flags you should watch for when deciding on a company? What advice would you give for someone looking for the right fit? Post in the commends below and don’t forget to follow the blog so you don’t miss out on the next post.
dotdotdev.com 