Hiring Review

Purpose: Reach a clear, evidence-based hire or no-hire decision through structured debrief before any compensation discussion

How to run this meeting

Use a scorecard, not a vibe. Before the meeting, every interviewer should have submitted individual ratings against the same rubric — technical skill, communication, role-specific competencies, and any leveling criteria. When the debrief opens, have the facilitator read the scores aloud before anyone speaks. This prevents the first person to talk from anchoring the room. If scores are consistent, the debrief is fast. If scores diverge, the divergence is the conversation.

Discuss evidence, not impressions. "She seemed nervous" is not useful. "She walked through three trade-offs in the system design problem, chose option B, and articulated exactly why — even when I pushed back twice" is useful. The facilitator's job is to steer the room away from adjectives and toward specific moments from the interview. When someone says "I wasn't sure about their communication skills," the right follow-up is "What did they say or do that made you uncertain?" Impressions that can't be grounded in evidence usually reflect bias, not signal.

Make the hire/no-hire decision before discussing compensation or leveling. These are separate questions. Conflating them leads to situations where a genuine no-hire becomes a "conditional hire if we can get them cheap enough" — which is bad for the candidate and bad for the team. Reach consensus on the decision first, then — only if it's a hire — discuss level and range. If there's no consensus, the facilitator should call the decision explicitly rather than leaving it ambiguous.

Before the meeting

• Confirm all interviewers have submitted scorecard ratings before the meeting starts (do not proceed without them)
• Prepare a one-paragraph candidate summary covering background, role applied for, and interview panel composition
• Pull the job description and leveling criteria to keep the discussion anchored
• Block 45–60 minutes; do not rush this meeting — a bad hire costs 6–12 months to undo
• Invite only those who interviewed the candidate; limit the room to avoid social pressure dynamics

Meeting Details

• Date:
• Facilitator:
• Attendees:
• Duration: 45–60 minutes

---

Candidate Summary

Brief, neutral overview of the candidate — who they are, what they're applying for, and who they met with. Keep this factual, not evaluative.

Candidate: Jordan Mehta Role: Senior Software Engineer, Platform (L5) Source: Employee referral (via @carlos) Interview panel: @sara (technical screen), @daniel (system design), @ling (behavioral/values), @priya (hiring manager) Interview date: March 10, 2026

Jordan has 7 years of experience, most recently as a Staff Engineer at a Series B infrastructure startup. Background is predominantly in distributed systems and data pipelines. Applied specifically for the Platform team's data infrastructure work.

---

Interview Feedback

Summarize each interviewer's scorecard ratings and key observations. Read scores aloud before open discussion begins.

Scorecard ratings (1–4 scale: 1=Strong No, 2=No, 3=Yes, 4=Strong Yes)

@sara: Strongest technical signal of any candidate this cycle. Immediately identified the consistency trade-off in the distributed cache design problem and proposed a solution I hadn't considered. Proactively asked about failure modes. Communication was clear but occasionally jumped ahead before I finished the question.

@daniel: Solid system design. Worked through the problem methodically, asked good clarifying questions. Slightly over-indexed on familiarity with AWS-specific tooling — would want to probe on vendor-agnostic thinking. Great listener.

@ling: Values and behavioral signals were positive but not exceptional. Good answers on conflict and feedback examples. Didn't see strong evidence of the "raises the floor for the team" behavior we look for at L5.

@priya: Technical fit for the data pipeline work is high. Role fit feels genuine — Jordan articulated specific things about our infrastructure challenges that matched our actual problems. My hesitation is L5 leveling; some of the leadership examples felt more L4 in scope.

---

Strengths

What specific evidence supports hiring this candidate? Ground each point in interview observations.

• Distributed systems depth (concrete): In the technical screen, independently surfaced the clock skew problem in our cache invalidation scenario before being prompted — this is a senior-level instinct.
• Intellectual curiosity: Both @sara and @daniel noted Jordan asked follow-up questions after the interviews, not during — suggesting genuine interest, not performance.
• Role fit: Deep familiarity with the specific class of problems our Platform team is solving. Would not need the usual 2–3 month ramp on context.
• Communication with depth: Can explain complex concepts clearly to different audiences — demonstrated with @daniel (technical) and @ling (non-technical).

---

Concerns

What specific evidence gives the panel pause? Distinguish between "disqualifying" and "worth monitoring."

• L5 leadership scope (moderate): @priya's note about leadership examples feeling L4 in scope is worth taking seriously. We're hiring for someone who will own the data pipeline roadmap — the examples Jordan gave involved executing on someone else's vision, not setting it.
• Vendor lock-in mindset (minor): @daniel's observation about AWS-specific thinking. Probably coachable but worth a follow-up question if we move forward.
• No prior experience managing up in ambiguous environments (minor): All examples of navigating organizational complexity came from well-structured environments. Our Platform team has a lot of ambiguity right now.

---

Decision

State the hire/no-hire decision clearly. If there is disagreement, the facilitator should surface it explicitly and drive to resolution — do not leave the meeting with ambiguity.

Panel decision: Hire — with leveling discussion

The panel reached consensus that Jordan clears the bar for an offer. The open question is L5 vs. L4 with a clear path to L5. @priya will make the final leveling call with input from @ling's behavioral observations. Compensation discussion to follow separately.

Leveling recommendation: L4 with explicit 12-month L5 criteria shared at offer stage.

---

Action Items

Follow-up

The hiring manager owns the outcome from this point forward. Notes from the debrief should be logged in the ATS (Greenhouse, Lever, etc.) against the candidate record — not just stored in a doc. If the decision is a no-hire, the recruiter should send a timely, respectful rejection within 48 hours; candidates who spent time on a full loop deserve a quick answer. For hires, the panel's observations about strengths and concerns make excellent input to the 30/60/90-day onboarding plan.