Interview: How A Head Of Engineering Solved His Tech Hiring Challenges2nd May, 2019 5 minutes
Mike Sowerbutts is the Head of Engineering at White Springs, a technology provider dedicated to improving sales performance. They employ approximately 20 employees across offices in London, Banbury, Oxfordshire and San Diego.
After ten years of progressing through the ranks at White Springs, Mike took on the Head of Engineering role with the challenge of recruiting a permanent team of highly skilled software development professionals to be based out of the Banbury office.
We spoke to Mike to find out how he did it and what advice he'd give others who face similar challenges in this talent short market.
UR: First off Mike tell me a bit about yourself.
MS: I studied IT & Media at Lancaster University and was based in Oxford before I joined White Springs in March 2009. I then moved to Banbury in order to be able to walk to work, it’s been a long time since I’ve had to jump in the car and commute to work! I now live just outside of York.
UR: But that’s quite a commute isn’t it?
MS: It’s a good drive yes – but pales in insignificance to a daily commute, given that for the majority of those years, I have been 100% remote!
MS: Moving into the Head of Engineering role and realising the CEO’s ambitions it was quite clear we had to scale up our team and that two developers wouldn’t be sufficient to deliver on the projects we had lined up.
UR: So, what was the plan?
MS: I needed to hire six people including a Technical Lead to be based out of our Banbury office.
UR: And how did you start to go about doing that?
MS: Well, I went out to some recruitment agencies and I managed to make one hire inside the first couple of months.
UR: That was good then...
MS: Well yes and no. From looking at the candidates and interviews we conducted to make just one hire I wasn’t convinced that I could find another six hires of sufficient quality in the right location within the timescale required. I was ideally looking for experience of microservices, Entity Framework and .NET Core 2.0. I needed to change something…
UR: So, what did you do?
MS: I decided to expand the criteria to include the hiring of remote developers who didn’t need to be within a commuting distance of Banbury.
UR: Ah okay. What experience, if any, have you had of remote workers previously?
MS: I’m one! When I moved to Yorkshire from Banbury I asked to work remotely and while there was initially some hesitation and resistance, the company did have some people in other departments doing it as well as some employees working out of the US so the decision was made to allow me to do it.
UR: I’ll come onto what some of that initial reluctance was down to later but for the moment, tell me what your experience was from a recruitment perspective after relaxing the location criteria.
MS: I hired the six further people I needed within the timescales I had! I also hired a new recruitment agency to help me as well.
UR: What made you choose the recruiter you did?
MS: I liked the recruiter, he came across as trustworthy and not too pushy and thankfully he turned out to be able to find the calibre of people I needed.
UR: And what did you find with regards to the new candidates that you saw?
MS: I started seeing a larger pool of high-quality candidates than I had done previously. It allowed me to be more selective and certain about who I selected as I knew I had more people to choose from. If you are not careful you can hire people for the wrong reasons, i.e. they live locally even if they are not the best for the job.
UR: Okay, great, that makes sense. While it seems an obvious positive that you get more candidates to choose from, what about the negatives you hear about employing remote developers? For example, I’ve heard that productivity slumps?
MS: That hasn’t been an issue. I’ve found that by being more flexible and by hiring the right people they don’t take the mick.
UR: Trust people until they give you a reason not to then. What about still being able to foster that team culture and effective communication when everyone isn’t in the same location?
MS: I’ve been the sole remote working employee in a team previously and that is difficult, especially when your line manager isn’t the biggest fan of remote working. However, when everyone in the team is remote it becomes easier. We use Microsoft Teams (allows multiple communication channels, syncs through Outlook…) to foster collaboration while also having an open chat where we can have some non-work communication and share our love of Star Wars etc! That may become more difficult with bigger teams but for the size we have it works. We also get together at least once every 2 months and go to developer conferences etc.
UR: Sounds great! I’ve also heard that companies are concerned about sensitive data becoming unsafe through the use of remote workers – what do you do to mitigate this?
UR: How would you summarise the impact that offering remote work has played in your hiring efforts?
MS: It’s definitely been advantageous. I always ask our current developers for any negatives / improvements but there hasn’t been anything up to now. Given that all of them were 100% office based in prior positions, this is telling
UR: And what about the interview process has that had to change?
MS: Not too much, I do a telephone interview first (anything from 20-60 mins), then invite them into Banbury for a face to face interview including technical tests). Though sometimes it makes more sense to interview at a location closer to both of us. Fortunately, the recruiter I worked with was able to provide a space for this.
UR: Thanks a lot for taking the time to do this Mike, finally, for anyone reading this who is considering hiring remote developers what tips would you give them?
MS: Okay, first one – look for more than just skillset. If someone’s personal skills are poor then working remotely doesn’t mitigate this, don’t change your team & cultural fit requirements just because they aren’t going to be in the same office. It’s still really important to get the right fit for the team. Secondly, ask the candidate where they plan to work from. You don’t want someone who says the sofa! Someone who can separate themselves from family distractions when needed and ideally has a separate workspace is better. It shows they are taking it seriously as well.
And finally, you need the candidate to have fibre broadband so it’s worth checking their location, connection and speeds.