What Are Your True Minimum Requirements?

A job description often calls for years of experience in a particular role. But, frequently, I’ve found that those role titles don’t have as much to do with the skills needed for the job as they sound. This often bars excellent candidates from the pipeline. Luckily, it’s a problem with a fix.

When you calibrate with hiring managers, focus on the true minimum requirements. What does a role actually entail? What “requirements” are really just nice to have? What are the competencies required to do the job well? Looking for the same minimum requirements across the board helps keep the whole process more equitable, and it gives sourcers more freedom.

Of course, you won’t move a profile forward if they don't meet the minimum requirements. But when you’ve thought critically about the true minimum requirements, you can find someone who’s met those bars in non-traditional ways.

If you want someone with a year of software engineering experience, maybe that could be updated to say “or technical experience or coding.” This will broaden the requirement to include folks from less traditional backgrounds. They could nail the interview, they could be the best performer on the team, but unless you think critically about what the requirements are, you are counting that person out before they can even be considered.

This type of calibration includes more people, invites more diversity of backgrounds, and helps you create a team capable of true innovation.