Performance Management and Feedback Questions

Covers managing individual and team performance, giving and structuring constructive feedback, setting clear expectations and goals, conducting reviews, and running performance improvement plans. Includes diagnosing performance problems versus capability gaps, coaching and development approaches, documentation and escalation, handling promotions and separations, and creating accountability while maintaining psychological safety and fairness. Candidates should be able to describe frameworks for regular feedback, metrics and systems used to track performance, examples of difficult performance conversations they have led, and how they balance support with consequences.

HardTechnical

19 practiced

Your organization discovers systemic bias in performance ratings disadvantaging underrepresented groups. As an engineering manager, draft a remediation plan: immediate steps (e.g., pause promotions, recalibration), manager training and rubric updates, a communication plan to affected employees, and metrics and cadence to track reduction in bias over the next 12 months.

Sample Answer

**Immediate steps (first 2 weeks)**- Pause promotions and compensation changes that rely on affected ratings; HR + ENG leadership to approve exceptions.- Convene an urgent calibration panel (senior EMs, HR, DEI partner) to review flagged ratings and adjust where bias is evident; document decisions and rationale.- Freeze use of current raw ratings for hiring/stack-ranking decisions until recalibrated scores are produced.

**Manager training & rubric updates (weeks 2–8)**- Deliver mandatory bias-awareness workshop for all managers (examples: affinity, performance attribution, halo/leniency), with role-play calibration exercises.- Revise performance rubric to clear, observable criteria and behavioral anchors (example anchors per level: design, impact, mentoring, reliability).- Implement calibration checklist and blind-review practices (remove names/gender/race when possible).- Require written evidence for each rating (impact examples, metrics).

**Communication plan to affected employees**- Day 3: Transparent all-hands and targeted emails explaining discovery, immediate protections (paused promotions), next steps, and where to ask questions (dedicated inbox + confidential 1:1s).- Week 2: Manager 1:1s with affected individuals offering support, clarification, and interim remediation options (e.g., fast-track coaching, role audit).- Ongoing: Monthly updates on progress and outcomes; publish anonymized calibration summary and changes made.

**Metrics and cadence to track bias reduction (12 months)**- Monthly KPIs: rating distribution parity (compare median/mean ratings by demographic), promotion rate parity, calibration adjustment rate (% ratings changed by panel), manager-level variance.- Quarterly KPIs: attrition by demographic, employee sentiment (pulse survey on fairness, trust), time-to-promotion.- Targets: reduce rating parity gap by 50% in 6 months, reach <5% statistically significant difference in 12 months.- Governance: monthly review by EM leadership + HR; quarterly audit by DEI + an external reviewer; publish progress to leadership and employees.

**Owners & governance**- EM (you): lead calibration, manager training rollout, and metric tracking.- HR + DEI: policy, communications, external audit.- CTO/VP Eng: authorize pauses and resource support.

**Expected outcomes & next steps**- Restore trust through transparency, measurable bias reduction, clearer rubrics, and sustained manager accountability. After 12 months, move from corrective actions to continuous calibration processes embedded in performance cycles.

HardTechnical

33 practiced

Describe a program to mentor other managers to improve their feedback and rating accuracy across the organization. Include curriculum topics, interactive exercises (role-plays, calibration labs), frequency and duration, methods to measure effectiveness (pre/post assessments, calibration variance), and incentives to encourage manager participation.

EasyTechnical

18 practiced

List five metrics you would track to assess individual and team engineering performance. For each metric include a brief description, one potential pitfall (how it can be gamed), and one mitigation you'd implement to reduce gaming or perverse incentives.

EasyBehavioral

24 practiced

Behavioral: Tell me about a time you gave constructive feedback that the recipient initially resisted. Use the STAR structure: describe the Situation, the Task, the Action (what you said and how you said it), the Result, how you handled pushback, and what you learned. Be specific about wording and outcomes.

MediumTechnical

19 practiced

Explain what happens in a calibration meeting between engineering managers. Provide a practical agenda, the data artifacts each manager should bring (e.g., recent goals, peer feedback, objective metrics), normalization techniques (distribution curves vs criteria-based anchors), and a process to resolve disputes when managers disagree about a rating or level.

Sample Answer

**Brief framing**A calibration meeting aligns managers so ratings and levels are consistent, fair, and evidence-based. The goal is less to argue subjective impressions and more to map evidence to shared criteria.

**Practical agenda (60–90 min)**- 0–5 min: Purpose, norms (evidence-first, no anchoring)- 5–20 min: Quick recaps — each manager 2–3 highlights or concerns- 20–60 min: Deep dive on disputed cases (3–6 people): manager presents evidence, peers ask clarifying questions- 60–80 min: Private voting/scoring, reveal aggregated results- 80–90 min: Decide follow-ups, appeals, development actions, document rationale

**Artifacts each manager brings**- Recent goals and OKRs + progress evidence (last 6–12 months)- Objective metrics: PR throughput, cycle time, feature lead time, uptime/incident MTTR, test coverage trends- Qualitative data: 360/peer feedback, skip-level notes, customer/stakeholder feedback, demo recordings- Calibration sheet: current rating, proposed rating, which rubric criteria are met- Prior calibration outcomes and development plans

**Normalization techniques**- Distribution-based: compute z-scores or percentiles for objective metrics to spot outliers (useful for comparing engineers on quantitative outputs)- Criteria-based anchors: map rubric behaviors to levels (must-have examples for promotion vs nice-to-have) — anchors reduce metric bias- Hybrid: normalize objective metrics across teams, then require behavioral anchors to support rating shifts- Use role- and context-adjustments (e.g., infra vs product teams have different velocity baselines)

**Dispute resolution process**- Evidence-first discussion: require the presenting manager to cite 2+ artifacts supporting rating- Private scoring: anonymous ballot (e.g., 1–5) to avoid anchoring; show distribution, not names- If disagreement persists: majority rule on rating but document dissenting rationale- For critical promotions/termination-level changes: require 2-manager consensus or escalate to a calibration panel/leveling committee- Post-meeting: create action items (clear development goals and measurable checkpoints) and allow a 1-cycle appeal with new evidence

**Bias-mitigation / best practices**- Pre-read packets 48 hours before- Rotate facilitators; enforce time-boxing- Track inter-rater variance over time and train on rubric use- Focus on growth plans, not just labels — every disagreement should produce clear next steps.

Unlock Full Question Bank

Get access to hundreds of Performance Management and Feedback interview questions and detailed answers.

Join thousands of developers preparing for their dream job.