Finding a job is hard. The application process is full of resume parsers that don't work, requests to rewrite your entire resume section by section, and long stretches of waiting. And that's before the interview rounds, where each conversation raises your hopes if it goes well and the sting if it doesn't.
Product managers get a special version of this. One company wants PMs who can code. Another wants someone who can read code. Some want excellent writers, exceptional presenters, people with executive presence. Others want data analysts who like talking to customers.
As Kyle Lee, a senior technical product manager, puts it: "It's a mess."
It's a mess for a reason. Every product manager role is different because every company and product is different. Peter Deng, former Head of Product at Instagram, described the job as filling in the white space between the other roles: you are the owner, so either do it or delegate it, because otherwise nobody will.
So how have hiring teams adapted to that variability?
"Tell me about a time you resolved a conflict."
"Explain an API to a 5 year old."
"What's your favorite product?"
Truly innovative.
Recycling job descriptions, application forms, and interview questions has stopped working. The range of products, the teams behind them, and the businesses selling them ask for something better.
Why do traditional interviews fall short?
They test the resume and then judge the answers by feel. Traditional interviews lean on titles and job descriptions that drift from the skills the work actually needs, which creates two problems at once: candidates don't know how to present themselves, and interviewers can't assess what matters most.
Candidates come away disconnected. Employers come away without a read. Everyone loses the time.
What replaces it is specific. A senior accountant needs GAAP expertise. A technical product manager needs API knowledge. An engineering lead needs experience scaling distributed systems. The conversation should sit on those capabilities rather than on a career summary.
What changes in a skills-based interview?
The question changes, and the standard for the answer changes with it. Take hiring a financial controller. The traditional opening asks the candidate to describe their finance experience. That's broad, it invites a vague answer, and it doesn't tell you whether they can handle regulatory compliance, hold a reporting deadline, or work across departments.
The skills-based version asks how they keep financial reports accurate and on time, especially under local and international regulations.
Now you're assessing one skill: financial reporting. The candidate knows what's being evaluated. You know what to listen for. Both sides get a conversation worth having.
Ryan Roslansky, CEO of LinkedIn, has made the same argument about how companies define work: the smartest ones are starting to treat jobs as a collection of skills and tasks rather than titles, and to think about how those skills will change. The focus moves from what someone has done to what someone can do.
Does it actually make hiring fairer?
It makes hiring more consistent, which is the part you can measure. Unstructured interviews have no shared standard, so evaluations come down to impressions that differ by interviewer and by day. A skills-based process assesses every candidate against predefined competencies, which narrows that drift.
The research supports the mechanism directly: structured interviews are the #1 predictor of job performance, more than twice as predictive as unstructured ones (Sackett, Zhang, Berry, & Lievens, 2022). Candidates demonstrate the skills the job needs, and interviewers work from well-defined questions and follow-ups tied to real experience with the critical competencies.
It also lowers the weight carried by proxies, which is where a lot of unnecessary screening happens. Two-thirds of employers in Harvard Business School's Dismissed by Degrees study acknowledged that requiring a four-year degree excluded qualified candidates, and the study found degree inflation made roles harder to fill without delivering the productivity gains meant to justify it. Removing a degree requirement that stands in for "can learn technical material" means assessing the thing itself.
Worth being precise about the limit. No interview method eliminates bias, and structure does not make a human judgment objective. What the 2022 data does show is that structured interviews produce among the smallest subgroup score differences of any top-performing hiring method. That's a real advantage and a narrower claim than fairness solved.
What do candidates actually get out of it?
Two things: a conversation where they can show their strengths, and an earlier answer.
On the first, a skills-based interview puts the discussion on competencies that decide the role, so candidates spend their time on relevant expertise rather than on generalized career questions. That tends to produce better evidence for the interviewer as a side effect.
On the second, the most common candidate frustration is advancing through several stages and then being rejected on something nobody named at the start. Deciding the critical skills upfront means a team can tell early whether a candidate has them. Nobody wants to be passed over, and finding out early on clear, role-relevant grounds is a far better experience than finding out in week five. It frees the candidate to pursue other work.
The employer side of that is documented. In Harvard Business School and Accenture's Hidden Workers research, 88% of employers said qualified high-skill candidates get screened out because they do not match the exact criteria in the job description, rising to 94% for middle-skill roles. Every one of those people sat through a process that never told them which criteria mattered.
How does it shorten the process?
By making each round collect something new. Interview loops get long when nobody decided what each stage is for, so three conversations end up testing the same two competencies. Name the critical skills first, assign them across the stages, and the redundancy disappears along with the candidate fatigue. Employers report reduced time-to-hire after making the change, and most of that comes from removing rounds rather than rushing them.
Clear criteria do the same work inside each conversation. When interviewers know which skill they own and what a strong answer sounds like, they ask precise questions and don't need to revisit the topic later.
How do you put this in place?
Four moves, and the first one carries the rest.
Run a skill-mapping session with the hiring manager. Identify the competencies the role genuinely needs, then use them to rewrite the job description and build the interview scorecard. This is the step that determines whether everything downstream is worth anything.
Keep a repository of skill profiles. Document the skills and competencies behind past successful hires, and build reusable profiles for roles you fill repeatedly.
Review the requirements on a schedule. Reassess which skills matter as the business and the market change, rather than inheriting last year's list.
Bring in outside expertise for specialized roles. For unusual or highly technical hires, a partner with domain knowledge shortens the learning curve.
The implementation gap is the real obstacle, and it has been measured. When large firms dropped degree requirements, the Burning Glass Institute and Harvard Business School found the net change in who actually got hired was 0.14 percentage points, about one hire in 700. Only 37% of firms genuinely changed their hiring; about 45% changed in name only. The posting moved and the interview did not, which is the same failure this article describes at the level of a single conversation.
Skills have always been what mattered. Structuring the interview around them just makes that explicit, and makes the decision something a hiring team can show its work on.
How Ratio fits
Building structured, skills-based assessments by hand takes hours per role: read the job, identify the critical skills, assign weights, write targeted questions, write the scoring guides. All before anyone interviews anybody.
Ratio does that preparation. Working from whatever you have on the job, whether that is a job description, your notes, or a hiring-manager transcript, it extracts and weights the skills the role needs for success, then builds a complete interview kit: targeted questions for each skill, planned follow-ups, and ready-to-use scoring guides. Interviewers get the structure. Candidates get a relevant conversation. People assign every rating; Ratio never auto-scores candidates.
References
- Hancock, B., Higgins, C., Law, J., Olson, S., Patel, N., & Van Dusen, K. Taking a skills-based approach to building the future workforce. McKinsey & Company. [publication year and URL to confirm]
- Cantrell, S., Griffiths, M., Jones, R., & Hiipakka, J. (2022). Skills-based organizations: A new operating model for work and the workforce. Deloitte Insights. https://www.deloitte.com/us/en/insights/topics/talent/organizational-skill-based-hiring.html
- Roslansky, R. (2021). You Need a Skills-Based Approach to Hiring and Developing Talent. Harvard Business Review. https://hbr.org/2021/06/you-need-a-skills-based-approach-to-hiring-and-developing-talent
- Field, E. Hire more for skills, less for industry experience. McKinsey & Company. [publication year and URL to confirm]
- Sackett, P. R., Zhang, C., Berry, C. M., & Lievens, F. (2022). Revisiting meta-analytic estimates of validity in personnel selection. Journal of Applied Psychology, 107(11), 2040-2068. https://doi.org/10.1037/apl0000994
- Kyle Lee, Senior Product Manager. LinkedIn Profile
Frequently asked questions
What is a skills-based interview?
An interview built around the specific capabilities a role requires, with one question per skill and a written standard for judging the answers, rather than around career history. For a financial controller, that means asking how the candidate keeps reports accurate and on time under local and international regulations, which assesses financial reporting directly, instead of asking them to describe their finance experience.
Why do candidates prefer skills-based interviews?
Because they can tell what is being assessed and get a fair chance to show it. Traditional processes move candidates through several rounds without clarity on fit, and the most common frustration is advancing for weeks only to be rejected on a criterion nobody named. Deciding the critical skills upfront means candidates who are not a match find out earlier, on role-relevant grounds.
Do skills-based interviews reduce interviewer bias?
They reduce inconsistency, which is a different and more measurable thing. Asking every candidate the same job-based questions and scoring against written anchors narrows how far two interviewers can drift apart, and it lowers the weight carried by proxies like job titles, tenure, and academic credentials. No interview method eliminates bias. Structured interviews do show among the smallest subgroup score differences of any high-validity method (Sackett et al., 2022).
How many interview rounds does skills-based hiring need?
Fewer than most processes run, because rounds multiply when nobody decided what each one is for. When a team names the critical skills upfront and assigns them across stages, each conversation collects new evidence instead of re-testing the same few competencies. Employers report reduced time-to-hire after the change, largely from removing redundant rounds.
Isn't this just a rebrand of competency-based interviewing?
The lineage is the same, and the difference is where the weighting lives. A skills-based model ranks the competencies by how much they decide the role, marks which are genuine must-haves, and drops the trainable ones from the interview entirely. Competency frameworks often list everything at equal weight, which is how a loop ends up testing twelve things and deciding on two.
Was this useful?