Combining SJTs with other skills assessments for holistic hiring

Two candidates score the same on a coding test. One quietly fixes a teammate’s broken feature the night before launch. The other ships their own work and lets the teammate sink. The skills test could not tell them apart. A situational judgment test could.

Combining situational judgment tests with skills assessments works because each one reads a different signal. The skills test proves what a candidate can do. The SJT shows how they act when the work gets messy. Run together, they give a hiring team a fuller read on a person than either test manages alone, and they cut the guesswork that leads to costly mis-hires.

TL;DR

• An SJT measures judgment and behavior. A skills test measures ability. Predicting real performance needs both.
• Used on its own, an SJT misses hard skills, and a skills test misses how a person works with other people.
• Pair an SJT with a role-specific skills test, a cognitive test, and where it fits, a personality or communication read.
• A meta-analysis of 102 studies puts SJT validity near .34, and that signal stacks on top of other tests.
• Two or three well-chosen assessments beat one long one. Keep the set short and keep every test role-relevant.

What is a situational judgment test?

A situational judgment test presents a candidate with a realistic workplace scenario and asks them to choose, rank, or rate possible responses. Instead of testing knowledge, it reads judgment: how a person prioritizes, handles conflict, and decides under pressure. Answers are scored against the responses that experienced employees rated as most effective for the role.

The scenarios are drawn from real situations in the job, so an SJT reads soft skills that a resume hides and an interview only hints at, such as teamwork, customer handling, and composure. Testlify’s situational judgment test library covers roles from support to supervisory, and each test maps candidate choices to a clear behavioral profile.

What do SJTs measure, and what do they miss?

An SJT measures behavior and decision-making: communication, teamwork, conflict handling, and how a candidate reasons through a workplace dilemma. What it does not measure is whether that same candidate can write clean code, close a set of books, or build a data model. Those are hard skills, and an SJT is blind to them.

An SJT is not a weak predictor, to be clear. A widely cited meta-analysis of 102 studies covering 10,640 people found SJTs predict job performance with a corrected validity near .34, and that signal holds up on top of cognitive and personality tests. The case for combining is not that SJTs are unreliable. It is that they read only one slice of the job.

That blind spot is why an SJT should never be the only screen. Judgment and ability are separate signals, and a strong score on one says little about the other. The known criticisms of SJTs, from response coaching to narrow role coverage, all point to the same fix: use the SJT for what it reads well, and cover the rest with a test built for hard skills.

Why combine SJTs with other skills assessments?

Combining assessments works because performance is multi-dimensional and no single test reads all of it. A skills test proves ability, an SJT reads judgment, and a cognitive test shows how fast someone learns. Stack them and the picture sharpens; drop one and a real risk goes unseen until the new hire is already in the seat.

The cost of getting this wrong is steep. SHRM reports that a bad hire can cost three to four times the role‘s salary once recruiting, lost productivity, and rehiring are counted. Meanwhile the mix of skills the job needs keeps shifting: the World Economic Forum estimates 39% of core skills will change by 2030. A single test, frozen in time, cannot keep up with that.

There is also hard evidence that skills-first signals predict better than the old proxies. McKinsey finds that hiring for skills is five times more predictive of job performance than hiring for education. An SJT adds a second skills-based signal on top of a technical test, so the shortlist rests on evidence rather than a degree or a gut read.

Which assessments pair best with SJTs?

Pair an SJT with tests that cover the signals it cannot read. The right combination depends on the role, but most hiring processes are well served by two or three of the four assessment types below.

Situational judgment test

An SJT anchors the process by reading judgment, behavior, and how a candidate handles pressure in a realistic scenario. It works for every role that involves people or stress, but it says nothing about the technical skill the job also requires.

Role-specific skills test

A role-specific skills test proves job ability directly, whether that is writing code, drafting copy, or working a spreadsheet. Pair it with an SJT and you cover both what someone can do and how they behave while doing it, the combination our guide to technical skills assessments builds on for engineering-heavy roles.

Cognitive ability test

A cognitive ability test measures reasoning speed and how quickly someone picks up new information, which matters most in complex or fast-changing roles. On its own it says little about how that reasoning shows up in a real interaction, which is where the SJT fills in, a gap our guide to common cognitive test challenges covers in more depth.

Personality or communication test

A personality or communication test reads work style, motivation, and tone, which matters heavily in customer-facing, sales, and team-lead roles, the same roles our guide to personality hires looks at in detail. Neither a personality read nor an SJT alone measures skill or judgment fully, so the two together cover more ground than either does solo.

A support hire might take an SJT plus a soft-skills assessment and a short writing sample. A developer might take an SJT plus a coding test and a cognitive test. Match the set to the job, not to a fixed template.

How to build a combined assessment process

Building a combined process is less about adding more tests and more about choosing the few that each read a different part of the job. Six steps keep it tight:

Define the role’s core competencies

List the four or five things a strong hire must do well, split into hard skills and behaviors. That short list becomes the map every later assessment decision gets checked against, the same competency-first thinking behind a good interview scorecard.

Map each competency to one signal

A coding competency maps to a skills test, and a conflict-handling competency maps to an SJT. Do not double-test the same thing, since two tests reading the same signal add length without adding evidence.

Pick two or three assessments, not five

Choose enough tests to cover the competency map, and few enough that candidates actually finish, a tradeoff our roundup of pre-hire assessment platforms is worth checking before you commit to a stack. A 45-minute battery beats a two-hour one on completion every time.

Order them shortest to longest

Run a 15-minute SJT or cognitive screen first, then reserve the 30-minute skills test only for candidates who clear it. This ordering saves reviewer time on the deepest test for the people already worth that investment.

Weight the scores by what the role needs

A developer role leans its weighting on the coding test, while a support role leans on the SJT and communication read. The weighting should follow what the job actually depends on, not a fixed formula applied to every role.

Review results together, not in isolation

Compare candidates on the combined view so one high score cannot mask a low one that matters more. Scoring each test in isolation is how a strong coder with a serious judgment gap slips through unnoticed.

For a fuller menu of tests to slot into this process, the main types of pre-employment tests guide breaks down where each one fits.

Common mistakes when combining assessments

Most combined-assessment processes fail for one of three reasons, not a dozen. Spot these three and fix them, and the rest of the process tends to take care of itself.

Stacking tests that read the same signal

Two behavioral tests and no hard-skills check looks thorough on paper but leaves the real gap wide open. Cover a different competency with each test instead of layering three ways to measure the same thing, a distinction close to screening in versus screening out candidates.

Piling on too many assessments

Five assessments in one process drives strong candidates to abandon it partway through, and the marginal signal from a fourth or fifth test rarely earns back that drop-off. Two or three well-chosen tests, each reading something different, beat a long battery every time.

Trusting a single signal for the whole decision

A 40-person support team hiring a customer success manager on an SJT alone might crown a warm, agreeable candidate who freezes when a contract is at risk. Add a short scenario-based skills task and a communication read, and the candidate who stays calm under pressure and can actually save the account rises to the top instead, a difference that compounds once a company is scaling past 200 people and hiring at volume, which is exactly the discipline behind bias-free hiring at scale.

Pro Tip: Run the SJT as an early screen, before the longer skills test. It is quick, it filters for judgment, and it means a specialist reviewer only spends time scoring the deeper skills test for candidates who already cleared the behavior bar. That one ordering choice can cut a six-week screening loop to about 10 days.

Final thoughts

An SJT and a skills test answer different questions, and neither one substitutes for the other. Judgment without ability just means someone who behaves well but cannot do the job, and ability without judgment means someone who can do the job but breaks the team while doing it.

Keep the combined process to two or three assessments, map each one to a distinct part of the role, and weight the final score toward whatever that role depends on most. That discipline, not a longer test battery, is what makes a combined process predict better than any single signal alone, the same principle behind high-performance skill assessments more broadly.

See a combined assessment before you build one

Testlify lets you pair a situational judgment test with skills, cognitive, and personality assessments in one flow, then score candidates on a single combined view. Walk through it with the team and see how the signals stack for your roles.

Key Takeaways

• One test reads one signal. An SJT reads judgment and behavior, a skills test reads ability, and a cognitive test reads learning speed. Because these do not overlap, a single test always leaves a real part of the job unmeasured, which is why combining them predicts performance better than any one alone.
• Pairing beats replacing. An SJT does not replace a skills test and a skills test does not replace an SJT. The two answer different questions, so the value comes from running them together, not from choosing between them.
• Keep the set to two or three. Enough assessments to cover the role’s competency map, few enough that strong candidates finish. More than three usually adds length and drop-off without adding new information.
• Order and weight by the role. Run the short screen first and the deep skills test second, and weight the final score toward whatever the job most depends on, whether that is coding, judgment, or communication.
• Evidence is defensible. A shortlist built on several role-relevant signals stands up to scrutiny in a way that a resume screen or a single interview never can, and it makes a bad hire, and its three-to-four-times-salary cost, far less likely.

Frequently asked questions about SJTs