Mentoring and Psychological Safety Questions

Covers approaches to coaching engineers, creating an environment where people learn and take appropriate risks, and structuring feedback and development conversations. Includes delivering feedback in ways that accelerate growth, explaining why rather than only what to change, and framing code review as a learning conversation. Also includes running one on one meetings and career development planning, identifying stretch assignments, supporting promotions and succession planning, mentoring senior engineers through complex problems to grow their technical judgement, and practicing clear teaching and communication while pairing or during technical interviews so others can follow design decisions and reasoning.

EasyTechnical

54 practiced

Explain the GROW coaching model (Goal, Reality, Options, Way forward) and show exactly how you'd structure a 1:1 using it with an engineer who says 'I want to become more confident making architecture decisions.' Include at least two example questions for each GROW stage.

HardTechnical

63 practiced

A senior, top-performing engineer publicly dismisses junior suggestions and reframes others' ideas as their own, undermining psychological safety. Provide a concrete remediation plan that includes coaching conversations, measurable behaviour goals, tracking cadence, performance consequences, and a team communication plan that restores trust without publicly shaming individuals.

Sample Answer

**Situation & Objective**Restore psychological safety and stop a senior engineer from dismissing juniors and taking credit, while coaching behavior change and holding them accountable without public shaming.

**Remediation Plan (30–90 day)**- 1:1 Coaching (Days 1–7): Private conversation—share specific observed examples, impact on team, expected behaviours (listen, credit others, invite input). Set clear SMART goals and consequences. Document and email a short recap.- Measurable Behaviour Goals (30 days): - Solicit input in every design review (min. 2 junior contributions acknowledged per meeting). - No public dismissals (zero incidents) logged by team for 30 days. - Credit others in PR descriptions and meeting notes 100% of the time.- Support Actions: shadow pair reviews, assign a peer coach, recommend conflict/communication training.

**Tracking & Cadence**- Weekly 1:1 check-ins (manager + senior) with written progress notes.- Biweekly skip-level/anonymous pulse surveys to measure psychological-safety signals (NPS-style + free-text).- Meeting audits: rotate a neutral note-taker to confirm acknowledgements in reviews.- 30/60/90 day formal reviews with documented examples vs goals.

**Performance Consequences**- If insufficient progress at 30 days: written performance improvement plan (PIP) with concrete milestones. - At 60/90 days: escalate to performance actions (role change, loss of leadership tasks, or termination) if behaviour persists.

**Team Communication Plan (restore trust, avoid shaming)**- Team all-hands: acknowledge cultural expectation (psychological safety), announce coaching and team-wide refresh of collaboration norms — no names. Share new norms, meeting etiquette, crediting practice, and how to raise concerns (anonymous form + manager/HR channels).- Reinforce via handbook update, retrospective agenda prompts, and public recognition program spotlighting collaborative behaviour.

**Expected Outcomes**- Increased meeting participation, higher pulse scores, visible crediting in repos/notes, reduced micro-aggression reports. Regular measurement and transparent follow-up ensure accountability while preserving dignity.

MediumTechnical

46 practiced

A senior engineer on your team frequently experiences decision paralysis when faced with architecture trade-offs. As their EM, outline a three-month coaching sequence to build their technical judgement without imposing your solutions. Include exercises, decision-frameworks you would teach, mentorship patterns, and success criteria.

MediumBehavioral

61 practiced

Run a short mock transcript (approx. 6 minutes of dialogue) where you, as manager, coach an engineer who says they feel 'stuck' about their career direction. Include opening lines, active listening, reframing, suggested stretch options, and a concrete next step that both of you commit to at the end.

MediumTechnical

48 practiced

Design a feedback model that works for distributed/remote teams and preserves psychological safety. Cover asynchronous feedback channels, synchronous rituals, code-review norms, and a short template for an async feedback message and for a synchronous coaching moment.

Sample Answer

**Clarify goals (one line)** Create repeatable, low-friction feedback that’s timely, specific, private/public as appropriate, and preserves psychological safety for distributed engineers.

**Asynchronous channels**- Use documented channels: PR comments for code, dedicated #feedback-private (DM-capable) and #feedback-public for recognition.- Encourage “ask permission” pattern: start with “Would you like feedback on X?” in DM or thread.- Store feedback summaries in a private growth doc (owned by the engineer) for performance conversations.

**Synchronous rituals**- Weekly 1:1s focused 50% on career/feedback, 50% on blockers; schedule with agenda shared 24h prior.- Monthly coaching huddles (small groups) for peer coaching and psychological-safety-building exercises.- Quarterly calibration meetings with managers to align norms and fairness.

**Code-review norms**- Always separate technical critique from author identity; use “I” statements and refer to code, not person.- Minimum checklist: correctness, readability, tests, performance/security impacts.- Use “suggest” vs “request” labels on comments; require at least one positive observation per review.- Set SLA: review within 24–48 hours; prefer small, focused PRs.

**Why this preserves safety**- Permission-based async prevents ambushes; public praise balances corrective feedback; rituals create predictable safe spaces.

**Async feedback template**- Subject: Feedback on [area] — short- Body: - Context: what I observed (when/where) - Impact: why it matters - Suggestion: concrete change or question - Offer help: “I can pair with you for 30m” - Closing: invite response: “Would you like to discuss?”

Example:- Context: “In PR #123 I noticed the retry logic retries indefinitely.”- Impact: “May cause cascading retries under load.”- Suggestion: “Limit retries to 3 and add exponential backoff.”- Offer: “I can help draft the change.”- Closing: “Want to chat or prefer I open a PR?”

**Synchronous coaching moment script**- Open: “Do you have 10–15 minutes? I’d like to share an observation and hear your view.”- Observation (facts only), Pause for reaction.- Impact + Question: “I noticed X; this caused Y. How do you see it?”- Collaborative next step: propose experiment, timeline, and offer support.- End: “Thank you — what do you need from me to try this?”

Unlock Full Question Bank

Get access to hundreds of Mentoring and Psychological Safety interview questions and detailed answers.

Join thousands of developers preparing for their dream job.