Situational Judgment Test Example Questions: Real Scenarios Explained
What makes an SJT question work
A situational judgment test works because it forces a choice. The candidate reads a realistic workplace dilemma and ranks response options from most to least effective. They cannot hedge. They cannot say "it depends." They have to pick, and the pattern of picks reveals how they think under ambiguity.
Good SJT questions have no obvious right answer. The ranked options sit along a spectrum of reasonable-but-different approaches. A candidate who ranks "consult your manager immediately" first might be risk-averse. A candidate who ranks "gather data from the system logs first" first might be detail-oriented. Both could be valuable. The assessment surfaces the difference.
Here are five example questions from different roles, with scoring rationale. ClarityHire's situational judgment library includes hundreds of these, role-tailored and validated against on-the-job performance. Each reflects the kind of judgment that best predicts job performance.
Example 1: Software Engineer (Incident Response)
Scenario: You're on-call and a monitoring alert fires at 2 AM. A service is returning errors for a subset of users. You begin investigating, but the data is inconclusive. Your manager typically wants to be looped in early on production issues. However, it's late and the outage is affecting fewer than 100 users.
Response options (rank from most to least effective):
A. Investigate for 15 minutes. If you can't find the cause, page your manager.
B. Page your manager immediately. This is their call.
C. Begin a postmortem in Slack to document your findings while investigating.
D. Spin up a test environment and try to reproduce the issue in isolation.
E. Check if this alert has fired before and review the previous resolution.
Most effective ranking: E > D > A > C > B
Why: The best engineers start with pattern recognition (option E). They leverage institutional knowledge before escalating uncertainty. Option D creates a controlled environment for testing. Option A balances investigation depth with appropriate escalation timing. Option C creates noise before having signal. Option B abddicates judgment—the problem is not severe enough to wake your manager immediately; it is solvable.
A candidate who ranks E first and D second demonstrates experience with incident response. A candidate who ranks B first or C first (creating noise) shows either inexperience or misaligned priorities. This kind of judgment distinction is exactly what makes SJTs valuable for reducing interviewer bias in technical hiring.
Example 2: Product Manager (Stakeholder Conflict)
Scenario: Your engineering lead and your head of design disagree on the scope of the next feature. Engineering argues for a minimal MVP to ship faster. Design argues for polish and coherence with the existing design system. Both are credible. Your leadership has no clear preference and defers to you. You have 8 weeks.
Response options (rank from most to least effective):
A. Side with engineering. Speed to market matters more than polish at this stage.
B. Side with design. Technical debt in design compounds quickly.
C. Propose a middle path: ship the MVP in 5 weeks, then iterate on design in weeks 6-8.
D. Facilitate a workshop where both teams define what "done" looks like together.
E. Defer to whichever team has stronger data about customer preference.
Most effective ranking: D > E > C > A > B
Why: Option D surfaces the hidden assumption—both teams probably agree on customer value; they disagree on process. A workshop forces that to the surface and builds shared ownership. Option E is pragmatic when data exists. Option C is reasonable but skips the deeper alignment work. Options A and B are binary thinking—neither is correct in isolation.
A PM who ranks D first has leadership instinct. A PM who ranks A or B first is defaulting to a decision heuristic instead of asking questions.
Example 3: Sales Manager (Pipeline Pressure)
Scenario: You have a rep who is underperforming against quota. It's mid-quarter. The rep is struggling with objection handling and demos, but they have built strong relationships with a few accounts. Your regional director is asking for a performance improvement plan. You believe the rep has potential but needs coaching.
Response options (rank from most to least effective):
A. Start a formal PIP immediately. The numbers don't lie.
B. Have a coaching conversation, identify specific skill gaps, and commit to weekly practice.
C. Pair the rep with your top performer for a month of co-selling.
D. Have a direct conversation about their fit for the role.
E. Wait another month before deciding. Things might improve.
Most effective ranking: B > C > D > A > E
Why: Option B is specificity plus investment—it signals that you believe in the person while setting clear expectations. Option C provides peer learning and normalized support. Option D is premature; you have not tried coaching. Option A (formal PIP) is documented escalation, but only after coaching fails. Option E is avoidance.
A manager who ranks B first understands that performance issues are often skill issues, not attitude issues. A manager who ranks A first may be confusing accountability with punishment. This judgment directly translates to better management hiring.
Example 4: Customer Success Manager (Churn Risk)
Scenario: A mid-tier customer is reducing usage of your platform. Their license covers three seats; they are only using one. When you reach out, the customer says, "We're exploring other options to see if something fits better." They are not angry. They are just evaluating. You do not want to lose them.
Response options (rank from most to least effective):
A. Send them information about new features they might have missed.
B. Understand why the other options are appealing. Ask directly.
C. Offer them a discount to lock in their commitment.
D. Schedule a deep-dive session to understand their current use case and goals.
E. Share a case study of a similar company that achieved success with your product.
Most effective ranking: B > D > A > E > C
Why: Option B is the foundation—you cannot respond effectively without understanding what is driving the evaluation. Option D shows investment and creates space for the customer to articulate needs. Option A treats the symptom, not the cause. Option E is social proof but without context. Option C (discount) trains them to shop around.
A CSM who ranks B first is curious. A CSM who ranks C first is reacting out of fear and creating bad precedent.
Example 5: Operations Manager (Process Breakdown)
Scenario: You discover a workflow in your Jira board that nobody is following. The process was documented six months ago, but the team has evolved informal workarounds. The process still theoretically works, but nobody is using it. You are tasked with fixing this.
Response options (rank from most to least effective):
A. Enforce the documented process strictly. Document violations.
B. Audit why the team stopped following the process. Ask them.
C. Redesign the process based on the informal workarounds they created.
D. Implement tooling to force compliance with the documented process.
E. Let the team run as-is; if it is working, leave it alone.
Most effective ranking: B > C > A > D > E
Why: Option B is diagnostic. The informal workarounds exist for a reason. Option C respects emergent intelligence—the team has already solved for their real constraints. Option A creates friction without understanding. Option D tries to solve a people problem with tooling. Option E ignores the lack of documentation, which will cause onboarding and consistency problems later.
An ops manager who ranks B first understands that processes are not rules; they are codifications of how work actually happens. A manager who ranks A or D first is enforcing rather than understanding.
Using these examples in your hiring
SJT questions work best when they are validated against your own company's definitions of good judgment. These five examples illustrate the structure: a realistic dilemma, ranked options without one obvious right answer, and scoring that reveals judgment patterns rather than just correctness.
If you are designing situational judgment tests for your organization, start with scenarios from your actual work. Have your top performers rank the options first. Compare those rankings to lower performers. The gaps in ranking patterns are where you find signal.
Once you understand how to interpret SJT results, you can compare your candidates against your internal benchmarks rather than generic norms. This is what separates high-signal hiring from vibe-check hiring.
Explore ClarityHire's situational judgment library to browse hundreds of role-specific and competency-specific examples, or create your own tailored to your company culture and role requirements.