Best Situational Judgment Tests for Manager and Leader Hiring

Why manager SJTs are different

An SJT for an individual contributor measures personal judgment under pressure. An SJT for a manager measures judgment about people and systems.

A software engineer faces: "Do I investigate alone or page my manager?" A team lead faces: "Do I override my team's approach or trust their judgment?" These are fundamentally different judgment calls. The second one is harder and more consequential because it involves other people's growth and career outcomes. See practical examples across roles to understand this contrast.

Manager-specific SJTs measure:

• Delegation and trust-building under pressure
• Coaching vs. directive management trade-offs
• Handling underperformance fairly
• Prioritizing team development against shipping
• Navigating upward (managing up) and across (cross-functional work)
• Honest feedback delivery without damaging relationships
• Conflict resolution when both parties have valid points

Individual contributor SJTs measure those too, in abstract. Manager SJTs put them in a context where the candidate is responsible for people.

Core scenarios for manager hiring

Scenario 1: The high performer with an attitude problem

Your best engineer delivers results but creates friction with the team. They dismiss other people's ideas in meetings, rarely document their work, and are defensive about feedback. Their output is 20% higher than the team average. You need the results, but the team is frustrated.

Response options (rank most to least effective):

A. Pull them into a private conversation about team impact. Make it clear that brilliance plus friction is not a net positive.
B. Move them to a role where they work independently. Let them contribute without team interaction.
C. Document the behavior and build a performance improvement plan. Make the standard clear.
D. Wait. Maybe the team will adapt, or the person will grow into better self-awareness.
E. Celebrate the output publicly so the team understands what excellence looks like.

Most effective ranking: A > C > B > E > D

Why: Option A addresses the core tension honestly: you value their output, and you will not accept the friction. It gives them an immediate feedback loop and a choice. Option C (formal PIP) is the right escalation if A fails. Option B solves the symptom (team friction) by exiling the person—this trains them to problem-solve by hiding rather than integrating. Option E celebrates behavior that is harming the team. Option D is abdication.

A manager who ranks A first has the emotional intelligence to separate performance from personality and give the person a chance to change. A manager who ranks B or C first is optimizing for team peace over individual growth.

Scenario 2: The underperformer who is trying hard

One of your direct reports is struggling. They miss deadlines regularly, their code needs heavy review, and they are clearly frustrated. But they are engaged, ask for help, and are improving month-over-month. They are in month four of a twelve-month ramp. You have a high-stakes project launching in eight weeks.

Response options (rank most to least effective):

A. Reassign them to a lower-stakes project so they have room to learn without pressure.
B. Pair them with a senior engineer for embedded coaching through the high-stakes project.
C. Give them the high-stakes project. Real pressure accelerates growth.
D. Have a candid conversation about whether this role is the right fit.
E. Document their progress and plan a checkpoint at month six to decide next steps.

Most effective ranking: B > A > E > D > C

Why: Option B is investment with guardrails. You are not protecting them from the project (which would signal you do not believe in them), but you are supporting them through it. Option A shows you believe they will succeed given space. Option E is prudent checkpoint thinking but delays decision. Option D is premature at month four; you have not given them enough runway. Option C treats struggle as weakness when it may just be the normal ramp curve.

A manager who ranks B first invests in people even when it is costly. A manager who ranks C first may be confusing pressure with growth. These distinctions are exactly why manager-specific SJTs outperform generic judgment assessments in predicting management effectiveness.

Scenario 3: The peer conflict

Two of your team leads have been in conflict for two quarters. One is outgoing and moves fast; the other is methodical and data-driven. Both are strong performers. The conflict is not about work quality—it is about approach. They are slowing each other down in a cross-functional project. Your director is asking you to resolve it. You believe both approaches have merit.

Response options (rank most to least effective):

A. Have a meeting with both of them together to air out the differences and find common ground.
B. Move one of them to a different project so they do not have to work together.
C. Meet with each individually to understand the root of the friction.
D. Make a decision about which approach is right for the project and align both behind it.
E. Let them sort it out. Conflict is how teams work through differences.

Most effective ranking: C > A > D > B > E

Why: Option C is diagnostic. You cannot facilitate (option A) without understanding what is actually driving friction. Option A is premature without that understanding, but it is the right next step after C. Option D is a decision, but it requires understanding the conflict first and implicitly chooses one person's approach as "right." Option B avoids the conflict and teaches them to exit when working is hard. Option E abdicates.

A manager who ranks C first understands that 1-on-1 listening precedes group problem-solving. A manager who ranks B first is conflict-averse.

Scenario 4: The silos problem

You inherit a team where different sub-teams have grown isolated. The backend team does not know what the frontend team is building until code review. Product is surprised by engineering constraints. Engineering is frustrated that product does not understand technical trade-offs. The separation is organizational (they report to different managers) but the work is integrated. You cannot reorganize immediately. You need to break the silos without reorganizing.

Response options (rank most to least effective):

A. Institute a daily stand-up where all sub-teams present their work. Transparency will solve this.
B. Facilitate a working session where you design a shared definition of "done" across the team.
C. Assign rotating "liaison" roles—one engineer attends product standups, one PM attends engineering planning.
D. Restructure the org so all teams report to you directly.
E. Wait for the next project. Use it as an opportunity to start fresh with better integration.

Most effective ranking: B > C > A > D > E

Why: Option B addresses the root: nobody has a shared framework for what "integrated" means. A working session to design that creates ownership. Option C is a tactic that reinforces the separation ("your job is to translate between them") rather than solving it. Option A (daily standups) increases information flow but does not build the shared mental model. Option D solves the problem by reorganization but skips the chance to make the current structure work. Option E is avoidance.

A manager who ranks B first understands that silos are a shared sense-making problem, not an information problem.

Scenario 5: Promotion vs. retention of a high performer

Your best individual contributor wants to be promoted to manager. They are an exceptional engineer—strong technical judgment, mentors informally, and people want to work with them. But they have no direct management experience. You have a manager role opening, and you also have the option to create a staff engineer or senior individual contributor role for them instead.

Response options (rank most to least effective):

A. Promote them to manager. They are your best person; they will figure it out.
B. Create a staff engineer role for them. They are too valuable as an IC to move them into management.
C. Have a conversation about what they want long-term. Be honest about management risks.
D. Offer them the choice: manager or staff role, and let them decide.
E. Do not promote them yet. Give them another year to develop management skills informally.

Most effective ranking: C > D > E > B > A

Why: Option C is clarity plus honesty. You need to understand if they want management because they think it is the next step or because they want to lead people. Option D respects their choice once they understand the trade-offs. Option E is prudent—year of informal leadership experience makes the transition more likely to succeed. Option B optimizes for retention but potentially moves them into a role they do not want or are not ready for. Option A is just hoping they will figure it out.

A manager who ranks C first takes the responsibility of career conversation seriously. A manager who ranks A first is avoiding the hard conversation about readiness.

Design principles for manager SJTs

Scenario quality matters more than scenario number. 5–7 high-fidelity manager scenarios reveal more than 20 generic workplace scenarios. This aligns with the principles described in how to design tests. Invest in realism.

Make emotional stakes explicit. Manager dilemmas have consequences for other people. A good scenario says "you will disappoint someone no matter which choice you make." This forces the candidate to decide based on principles, not desire to please.

Avoid "leadership clichés." Scenarios like "your team wants you to be friends" or "you have to deliver a project early or the company fails" are overdone. Use scenarios grounded in real manager experience.

Include delegation and accountability. Most manager SJT pitfalls involve clarity on who is responsible for what. Ask scenarios about the transition from "I am doing this" to "my team is doing this."

Measure for growth mindset, not just judgment. Look at whether their ranking suggests they believe people can improve (option: "invest in coaching") vs. people are fixed (option: "find someone better"). This reveals how they will lead. High scores also reflect strong emotional intelligence, a predictor of management effectiveness.

Validating manager SJTs

After using a manager SJT to hire 5–10 managers, correlate results against:

• Do they get promoted again? (high signal of leadership fit)
• Do their reports stay longer than average? (retention signal)
• Do their 360 reviews rate them higher on "develops people"? (direct measure)
• Do their teams hit goals on time? (business outcome)

Do not look just at "manager performance." Look specifically at people leadership because that is what manager SJTs measure.

Implementation in your hiring

Place manager SJTs before the behavioral interview, not after. An SJT takes 15–20 minutes and filters for judgment patterns. A behavioral interview then probes the specific examples behind those patterns.

Scoring: most-effective (MD) method is cleanest. Did they rank the "most effective" option first? This requires you to have a master ranking from your leadership team first—essential context before hiring.

When interpreting results, treat a weaker SJT score as a signal to probe deeper in the interview: "I noticed in the team conflict scenario you ranked [option] first. Walk me through your thinking. When have you handled something similar?"

Build your own manager SJTs from your best managers' stories. This approach aligns with the process described in how to design situational judgment tests. ClarityHire's leadership assessment library includes pre-built manager scenarios, but your own context will be richer and more predictive. When interpreting your results, remember that manager patterns are especially telling—they predict who will invest in their teams.