· Valenx Press  · 7 min read

New Manager 1on1 Template for Underperforming Engineer at Amazon

New Manager 1on1 Template for Underperforming Engineer at Amazon

The verdict is stark: a new manager who treats an underperforming Amazon engineer like any other employee will never drive improvement. The only way to reverse a performance slide is to embed clear expectations, data‑driven signals, and a documented escalation path from day one.

How can a new manager immediately set expectations in a 1on1 with an underperforming engineer at Amazon?

A new manager must state the performance gap, the measurable targets, and the review cadence within the first five minutes of the meeting. In a Q2 HC debrief, the senior TPM challenged my notes because I had failed to articulate the “what‑and‑when” of the engineer’s deliverables; the committee voted to delay the promotion until I revised the 1on1 template. The correct opening line is a non‑negotiable fact: “Your current code‑review score is 62 %; the goal is 85 % by the end of this sprint.” This frames the conversation as a contract rather than a coaching chat.

The manager then flips the typical “feedback sandwich” on its head: not “you need to improve your communication,” but “you will document every design decision in a wiki entry by Friday, and I will audit it.” The problem isn’t the engineer’s lack of skill — it’s the manager’s failure to signal what success looks like in Amazon’s data‑centric culture. By anchoring the discussion on a concrete metric (e.g., story points completed per sprint), the manager forces the engineer to align with the team’s delivery cadence.

What concrete agenda should a new manager follow during the first 30‑day 1on1 cadence?

The agenda must be a three‑part loop: data snapshot, corrective action, and verification checkpoint, repeated every week for 30 days. In a recent hiring manager conversation, I presented a slide that listed “Week 1: Review last sprint velocity; Week 2: Set micro‑goals; Week 3: Pair‑program on a high‑impact ticket; Week 4: Document outcomes.” The hiring manager immediately approved the cadence because it mirrored Amazon’s “two‑pizza team” rhythm and left no room for vague aspirations.

Week 1’s data snapshot is a one‑page table: story points delivered, defect leakage, and code‑review rating. Week 2’s corrective action is a single SMART goal, such as “increase unit‑test coverage from 48 % to 70 % on the checkout service within five days.” Week 3’s verification checkpoint is a 15‑minute live demo where the engineer walks through the new tests, and the manager records a concise “outcome” line: “Goal met, coverage now 71 %.” The loop repeats, and after four weeks the manager has a documented trail that can survive a future performance review.

Which signals reveal that the engineer is truly disengaged versus merely stressed by Amazon’s delivery cadence?

The decisive signal is the variance between commitment and execution over two consecutive sprints. In a March 1on1, the engineer claimed to be “overloaded” but his Jira history showed a 30 % drop in committed versus completed tickets, while his peer’s completion rate stayed above 95 %. The manager concluded the engineer was disengaged, not merely stressed.

The not‑obvious contrast is not “low output equals low talent,” but “low output combined with no proactive communication equals a risk factor.” When an engineer logs “blocked” without opening a ticket, the manager must treat that as a red flag. The manager should ask, “What concrete step did you take to remove the block?” If the answer is “I waited for a manager email that never came,” the disengagement is confirmed. Documenting this pattern in the 1on1 notes protects the manager during the HC review, where data‑driven evidence outweighs anecdotal impressions.

When should a new manager transition from coaching to formal performance improvement at Amazon?

The transition point is the end of day 45, when the engineer has missed two consecutive verification checkpoints. In a Q3 debrief, the director asked why I had not escalated after the 30‑day plan failed; I responded that the engineer’s metrics had improved from 62 % to 78 % code‑review score, but the defect leakage remained at 4.2 % versus the team average of 1.1 %. The director instructed me to open a Performance Improvement Plan (PIP) immediately.

The key judgment is not “wait until the annual review,” but “activate the PIP as soon as the data shows a sustained gap.” The manager must send a written notice that includes: (1) the specific metric shortfall, (2 ) the 30‑day corrective actions that were missed, and (3) the next review date, typically day 60. By anchoring the escalation to hard numbers, the manager removes ambiguity and aligns with Amazon’s “metrics‑first” culture.

How does a manager document the 1on1 outcomes to survive a future HC review?

The manager must log every 1on1 in a single, immutable table within the internal HR portal, capturing metric, goal, and outcome fields. In a senior manager review, I was asked to produce the “last three 1on1 entries” for an engineer under review. Because each entry contained a row with “Metric | Target | Result | Next Step,” the committee accepted my documentation without request for additional testimony.

The not‑trivial contrast is not “write a narrative,” but “record a data point.” A narrative can be reinterpreted; a data point cannot. The manager should also attach the relevant Jira filters and code‑review dashboards as evidence. This practice creates a paper trail that survives any “manager bias” claims during the HC review and satisfies Amazon’s internal audit requirements.

Preparation Checklist

  • Draft a one‑page performance snapshot (story points, defect rate, code‑review score) before the first 1on1.
  • Define three SMART goals aligned with Amazon’s L6 expectations, each with a 5‑day verification deadline.
  • Schedule a recurring 60‑minute slot for the next four weeks; block the calendar to prevent drift.
  • Prepare a brief script for the opening line: “Your current code‑review score is X%; the target is Y% by Z date.”
  • Work through a structured preparation system (the PM Interview Playbook covers Amazon’s “Metrics First” framework with real debrief examples).
  • Capture the meeting notes in the HR portal immediately after each 1on1, using the mandated table format.
  • Set an escalation trigger: if two consecutive verification checkpoints are missed, draft the PIP notice within 24 hours.

Mistakes to Avoid

BAD: Treating the 1on1 as a casual check‑in and leaving the agenda open‑ended.
GOOD: Use the three‑part loop (data, action, verification) and stick to the timing schedule.

BAD: Relying on vague compliments like “you’re doing better.”
GOOD: Cite exact numbers—e.g., “code‑review score rose from 62 % to 78 %.”

BAD: Delaying the PIP until the annual review cycle.
GOOD: Initiate the PIP as soon as the 45‑day data threshold is crossed, documenting every missed metric.

FAQ

What should I say if the engineer pushes back on the metric target?
State the target as non‑negotiable: “The 85 % code‑review score is a team standard, not a personal preference.” Offer a concrete support plan, but do not renegotiate the metric itself.

How often can I change the agenda if the engineer’s workload spikes?
Do not adjust the agenda to accommodate workload spikes; instead, record the spike as a variance and keep the verification checkpoints unchanged. The consistency of the agenda is a signal of managerial rigor.

Can I use this template for senior engineers (L6) as well as L5?
Yes, but scale the metric thresholds upward (e.g., 90 % code‑review score) and shorten the escalation timeline to 30 days for senior engineers, reflecting Amazon’s higher performance bar.amazon.com/dp/B0GWWJQ2S3).

You Might Also Like

    Share:
    Back to Blog

    Related Posts

    View All Posts »