Please follow and like us:
Java. HTML5. MongoDB. Agile/Scrum. REST/JSON. Kubernetes. AWS. Product management. GAAP/financial accounting. Channel development. Interviewing.
Wait. Interviewing?!? Yes, interviewing skills!
Startups hunger for talent. A company’s ability to source and hire skilled employees determines its ability to grow. A quick search on any job board produces long lists of openings for web developers, DevOps engineers, cloud architects, mobile app developers, product managers, sales engineers, business development managers, accountants, and more. Building a robust hiring engine is an often overlooked but essential part of growing a startup.
How Borderline Employees Get Hired
A growing startup devotes a significant amount of time and effort to interviewing candidates to fill open positions. However, very few companies spend any time to establishing a structured interview methodology. In the rush to get back to their primary job of writing code, chasing a deal, or closing the books, startups assume employees know how to interview prospective employees. The hiring team rarely does any advance planning to prepare for candidates coming onsite for an interview. Interviewers are left with no guidance and no structure. The interview may cover overlapping topics and/or miss several key topics, resulting in a disjointed and disorganized process. One of a startup’s most important operational decisions is left to an unstructured and subjective sense of whether the interviewers generally liked the candidate. This mistake allows a higher percentage of borderline candidates to join the team.
Borderline employees dilute the effectiveness and productivity of the entire team. Senior employees invest one of the company’s most precious assets – time – into training the new employee and getting them up to speed. Team leads, managers, and peers spend multiple man months on a new hire, only to be disappointed in the borderline employee’s output. Companies can minimize these headaches by adopting the simple, structured interview guidelines below.
Behavioral >> Situational
First, every person on the interview team must understand how to conduct a behavioral instead of a situational interview. Many great articles are available that dig into the definition of these terms and provide detailed explanations of why behavioral questions are better than situational. In short, behavioral interviewing asks the candidate to describe how they handled a past experience. In contrast, situational interviewing asks the candidate to make a choice among several options presented.
Behavioral interviews are built on the premise that past history is the best predictor of future behavior. A behavioral question or request tends to start with “Tell me about a time where you (faced a certain problem)”. A situational question tends to resemble “What would you do if you (had to choose between option A and option B)?” Behavioral questions tend to extract a better picture of a candidate’s ability to execute. A person who is good at interviewing will often be able to guess what the situational question is driving at and will give you the response you wanted to hear. For example, “Tell me about a time where you faced an unreasonable deadline” will provide good insight into how the candidate handles pressure. In contrast, “What would you do if you had to work late to meet a deadline?” usually results in the candidate responding that they’ll just suck it up and work longer hours. Whether the candidate really will do that isn’t truly known, but it’s probably the safest response during an interview. Clearly, behavioral interviewing produces better results. Train your interview team to use behavioral questioning. You can use the attached one-page document to provide an overview of behavioral vs. situational interviewing.
The hiring engine usually includes some version of the four phases above. I’ll assume that you have a recruiter sourcing candidates and doing the first round of filtering. The recruiter’s job should be to provide a short list of candidates that have a good chance of being a fit. Recruiters rarely have the technical experience to effectively validate the skills of all the roles they have to fill, but a seasoned recruiter should be very good at filtering. Filtering generally involves some combination of the following:
- Ensuring the candidate’s goals align with the company’s opportunity
- Evaluating the candidate’s communication skills
- Determining at a high-level if the candidate’s past roles provide the foundation to perform the responsibilities of the position
- Assessing logistical fit with the role (timeframe, travel expectations, work location, relocation, etc.)
- Performing initial due diligence (work authorization status, work location, compensation and title expectations, readiness to make a change, etc.)
- Providing background information about the company
- Selling the role
- When at the appropriate stage in the process, performing final due diligence (background checks, reference checks, verification of degrees/certifications, etc.)
Once a candidate clears the filtering process, the interview team validates the candidate’s fit. I generally ask the interview team to cover the following topics: cultural fit, manageability, and technical skill. One person (usually the recruiter) covers the cultural fit. The hiring manager should cover manageability and may cover some technical topics. A technical lead and one or more colleagues should cover technical skills.
To help guide your behavioral interviewing, I’ve put together the following list of cultural and manageability questions, along with some simple forms you can use guide your questions and capture the candidate’s responses:
Cultural Interview Questions
(downloadable form here, 148K)
- Why are you looking for another job?
- What are you looking for in a job? What are your goals?
- Describe a time where you worked on a project with an unreasonable deadline.
- Describe a time where you worked in an environment with very little structure.
- Describe a time where you were asked to work on something you were unfamiliar with.
- Describe a time where you had to take a risk.
- Describe a time where you had to move faster than you were prepared to move.
- Describe a time where you had to choose between working on an immediate task vs. meeting the needs of another person.
- Describe a time where you were faced with choosing between individual achievement and team achievement.
- Describe a time where you had to work within an established process that you disagreed with.
- Describe your three biggest strengths and your three biggest weaknesses.
Manageability Interview Questions
(downloadable form here, 149K)
- Describe a time where you had a conflict with a co-worker.
- Describe a time where you disagreed with the decision of a subordinate.
- Describe a time where you had a difference of opinion with a co-worker.
- Describe a time where you worked with an under-performing co-worker.
- Describe a time where you were asked to work on something you did not enjoy.
- Describe a time where you disagreed with the direction of a project or with a decision made by management.
- Describe a time where you didn’t feel heard.
Because of the broad range of technical topics possible, it’s beyond the scope of this article to provide a sample list of technical questions. However, one thing I strongly believe in during the interview process is asking candidates to produce some work related to what the role needs. If you are trying to hire a programmer, then ask them to write some code that solves a problem. A simple Google search on “Java programming problem and solution” will provide a number of useful web resources such as CodingBat.com. If the candidate needs strong written communication skills, a Google search on “writing tests” will point you to resources such as IELTS academic writing practice tests. Asking them to produce some real work products in your office often separates someone with true skill from someone who is just buzzword-compliant or who merely holds paper credentials without real capabilities. In some cases, online tools or tests (such as those found on BrainBench.com and PanPowered.com) can supplement the interview process and reduce the time or effort needed to vet a candidate’s technical skills.
Before the candidate leaves, either the recruiter or the hiring manager should conduct a wrap up conversation. Topics to cover may include:
- How does the candidate feel the day went?
- What do they like about the company?
- What concerns do they have about the company?
- What do they like about the role?
- What concerns do they have about the role?
- How does this opportunity align with their goals and objectives?
- What other opportunities are the candidate currently considering?
- What considerations would lead the candidate to choose this opportunity over other opportunities in play?
- What questions does the candidate still have about the company or the opportunity?
- When would the candidate look to make a decision about their next role?
At the end of the interview, the interview team should reconvene and summarize their portion of the interview and provide their individual recommendation (hire, don’t hire, need more information to decide). Finally, the recruiter should collect the actual notes from each member of the interview team. Having the notes will help justify any decisions not to hire the candidate in the unlikely event that the candidate accuses the company of bias and/or threatens legal action.
If the interview team recommends hiring the candidate, the hiring manager and/or executive take responsibility to assemble a compelling job offer. The closing team should use the candidate’s responses to the wrap-up questions above to help close the deal.
Hopefully, this framework provides the foundation for you to set up a robust hiring engine so you can find the most qualified candidates to grow your company.