Resume review guide
Watch out for unconscious bias!
Remember that we all have unconscious bias, and that hiring is especially susceptible to bias. However, when we recognize and accept bias we can be on the lookout and it’ll be less likely to unconsciously guide our decisions.
Research shows that the effect of unconscious bias can be profound. For example, in one study, “applicants with white names needed to send about 10 resumes to get one callback; those with African-American names needed to send around 15 resumes to get one callback.”
This bias prevents us from achieving the results we want, which is to select the best possible candidates regardless of background.
Humans are not only biased, but we almost never realize that we’re being biased. However, when we realize and accept bias, and recognize it, we can be on the lookout for bias and it’ll be less likely to unconsciously guide our decisions.
In that spirit, here are a few ways you can look out and correct for bias during the hiring process.
- Review these guidelines before every interview or round of resume review. Studies show that we’re less biased when we’re conscious of our own thinking, so continually reminding yourself to be aware will help.
- Remember that we’re especially susceptible to assume that underrepresented minorities — women, people of color, etc. — are less qualified than their white male counterparts. When considering candidates from underrepresented backgrounds, check your thinking about qualification. Ask yourself: am I reading this person’s qualifications the same as if they were white, male, etc?
- Continually re-check the guides and scoring rubrics to make sure you’re reviewing fairly. After a while, you’ll start to feel like you’ve memorized the guides and rubrics. This is good since it’ll help you be more efficient, but our memories are fickle things. The more you remind yourself of the concrete, established metrics, the less likely you’ll be to make “gut” decisions that could be colored by bias.
- Watch out for assessments of candidates that may be colored by age, gender, race, etc. For example, we tend to be more likely to use words like “aggressive” or “competitive” when describing men, vs “supportive”, “nurturing” when describing women. Are you surprised that an older person has cutting-edge technical skills? Ask yourself if an assessment might be colored by an applicant’s demography.
- Don’t check out the candidate on social media, or Google them. A person’s public profile almost certainly won’t have anything relevant to work, and might instead reveal all sorts of irrelevant information (age, gender, political affiliation, race, etc.). If the candidate application/resume links to a personal website, LinkedIn, or GitHub you can check those out — these are more work-focused, and we can assume a candidate has put what they want an employer to see there. If you use Chrome, the Unbias Me extension (written by Fureigh) can help by removing avatars and names on some websites such as LinkedIn.
- If you come to a conclusion about a candidate very quickly, before you’ve read the whole resume or finished the interview, spend the rest of the session trying to disprove that conclusion. Snap judgments are much more likely to be prone to bias than considered ones. We tend to jump to conclusions and then look for evidence to support our hypothesis. To compensate, if you find you’ve reached a Yes/No conclusion very quickly, spend the rest of the session trying to disprove that hypothesis. Explicitly look for evidence that you’re wrong. If you’ve decided immediately that a candidate is not qualified, spend the rest of your time trying as hard as you can to find evidence that they are qualified.
In order to qualify for an appointment, candidates must demonstrate that they have position-specific Specialized Experience documented in their resumes.1 TTS Talent’s review will help ensure that the candidate’s offer will likely pass review by GSA HR following the interview round. The engineering hiring manager will review to see how the individual's experience would align with needs of the team or organization. (For candidates reading this, take a look at how to prepare your resume.)
The engineering hiring manager will review to see if their experience aligns with what is needed to be successful in our working environment. Generally, the reviewer will look for experience that describes the following work:
- Working with software programming languages and application-level frameworks that are core to working at 18F
- OR devOps experience on a modern commercial cloud provider or platform, especially with common Infrastructure-as-Code (IaC) stacks like Terraform, Puppet/Chef/Ansible/etc.
- Using Agile methodologies and cross functional team experience
- Stakeholder management experience (for higher grade levels)
To do so, the engineering hiring manager will review previous roles, accomplishments and tasks, and additional items to understand the complexity and the length of experience the candidate has in these areas.
TTS crafts Specialized Experience for each role posting. We iterate on this broad description, especially if multiple teams with different skills needs are jointly participating in hiring (“bucket hiring”). If and when TTS talent and GSA HR come across less common candidate experience (programming languages or frameworks), they will work with the hiring manager to confirm if it is relevant.
1 Specialized experience “is experience that has equipped the applicant with the particular knowledge, skills, and abilities to perform successfully the duties of the position and is typically in or related to the work of the position to be filled.” OPM