We all know that applying for jobs and companies’ recruitment processes can be stressful. So here at MetaBroadcast we try to make it as smooth as possible and, of course, we look to improve it all the time to make it the best we can for both applicants and us. To that end, we’ve been making some improvements to our recruitment process over the last weeks, which I’m going to talk about today.
it still takes three steps
As you may know, we have a three-step application process. Full details are here, but in summary:
- Step 1: Meet the owners. If they’re not your direct manager, you may meet her/ him, too.
- Step 2: Complete a test. In your own time, and generally limited to 2-2.5 hours.
- Step 3: Spend the day with us. We’ll make something together, have lunch together, go to the pub together and test drive how much we might like working together.
one size doesn’t fit all
We get applicants from a range of backgrounds, with many different experiences and skills. Everybody brings a unique set of skills from the next person. In the tests and exercises we set we want people to be able to show off these skills and demonstrate what they could add to the team. Of late, that has pushed us to iterate faster on steps (2) and (3) above, and I’ll share how we make sure that, for engineers in particular, both those steps have improved.
tweaking the test ftw
We have a number of tests up our sleeves for engineers, which suit a broad range of people, and we tweak each one further depending on their exact situation. One of them is for final-year students of computing, who would’ve had some practical experience before applying with us. However, we’ve recently started the recruiting process with a student that has not had that pleasure. The point of the test is to show us how a person thinks, and to prepare them for the day in and the type of exercise they might have to solve, so we couldn’t compromise either. The way we tweaked the test in this case was to focus less on writing a web service, and more on performing calculations based on data from an external one.
tweaking the day in
We’ve also been listening a lot to feedback on what could make the day in better, and in the last weeks alone made the following improvements, to give you an idea:
- We now prepare a schedule for the day in advance so every knows the running order ahead of time.
- Towards the end of the afternoon some of the engineering team convene with the applicant for a quick code review.
- It’s important to focus on the product, so we include some time with our product manager, Jonathan, to talk about the hack that’s being worked on and possible improvements.
what can we tweak for you?
The above measures, combined, have already made the whole experience less stressful, more enjoyable for all involved, and we look forward to even more tweaking. Whether you’re interested in an engineering position with us or another type of making things at MetaBroadcast, we’re very keen that there’s plenty of room to use your existing skills, develop your areas of interest (e.g. Augusto joined with a clear NoSQL agenda) and overall carve your space among us. So have a look at our open positions and let us know what we can tweak for you.