At Fearless, we highly regard our developers. We rely on them to guide business decisions such as what projects and contracts we should pursue, what languages and environments we should use, what steps we should take on current projects, and – often the most important – who we should hire.
While our cultural interview is heavily weighted (we openly tell candidates that despite the technical strength of a candidate, we won’t hire them on the team if we don’t feel that they’d be a cultural fit), our tech interview is also critical. Once we have a candidate that fits our culture and wants to move forward after learning about what Fearless is all about, the next step is a technical interview, conducted by one of our current developers who is an expert in the area the candidate is applying.
Technical interviews are important for several reasons.
- We need to understand the technical maturity of a candidate.
- We want people who like tinkering and learning the newest technologies.
- We want to make sure our candidates can speak tech, communicating effectively about the tools, technologies and work they have completed.
In order to make sure we make the right call on those 3 points (and more), we have one of our current developers complete the technical interview. No one understands the skill set needed to complete our work better than the folks who are actually doing the work today.
The technical interviews are usually held in person. The candidate is also encouraged to ask questions about working at Fearless, interacting with customers, challenges with working at a customer site, etc. Since their tech questions are going directly to someone who is intimately familiar with the tech work we do, there isn’t a middle man, “I’ll get back to you on that”, or a recruiter scrambling for answers to coding questions that sound like Greek to them. It’s a win for everybody.
After a technical interview, our interviewer reports back on factors like the technical strength of the candidate, the candidate’s ability to answer technical questions with clarity, and whether or not they think the candidate is ready to join one of our projects today.
We happily leave the technical assessments to those who know best, so do not be surprised if you don’t get the opportunity to dive deep into Angular vs React, optimum OS environments, and git branch setups in your cultural interview. In the technical interview, you’ll get your chance to speak tech with a fellow developer who understands the languages, environments, and technologies listed in your résumé.