· Valenx Press  · 6 min read

1on1 with Manager Who Doesn't Give Feedback at Amazon Robotics: Survival Guide

1on1 with Manager Who Doesn’t Give Feedback at Amazon Robotics: Survival Guide

TL;DR

The only way to survive a manager who never gives feedback at Amazon Robotics is to treat every 1‑on‑1 as a data‑gathering experiment, force the conversation toward measurable outcomes, and document every signal yourself. Stop waiting for “the feedback” and start engineering your own performance loop.

Who This Is For

You are a mid‑level software or hardware PM, SDE II, or senior mechanical engineer who has been placed on a team in Amazon Robotics where the direct manager avoids giving any explicit performance input. You have already survived the 4‑round interview process, signed a $165k‑$210k base plus RSU package, and are now trying to keep your career trajectory alive despite a silent manager.

How do I turn a silent 1‑on‑1 into a useful performance check?

The answer is to redesign the agenda before the meeting starts. In my Q2 debrief, the hiring manager asked why I hadn’t raised the “feedback gap” earlier; I responded that I was “waiting for direction.” The reality is the manager’s silence is a control lever, not a neutral state.

  • Judgment: A 1‑on‑1 that lacks a manager‑driven agenda is a symptom of power‑by‑absence, not of team health.
  • Framework: Use the “Signal‑Capture‑Iterate” loop. Capture three concrete signals (metrics, stakeholder sentiment, delivery dates) before the call; present them as a status snapshot; ask a single, data‑driven question (“Given these delivery trends, should we re‑prioritize X?”).
  • Counter‑intuitive observation: The problem isn’t the manager’s reluctance – it’s your willingness to treat the silence as a cue to produce your own feedback metric.

By turning the meeting into a “review of my own data,” you force the manager to either validate or correct, creating a de‑facto feedback moment.

📖 Related: Amazon PM vs Facebook PM Salary Comparison

What should I ask to surface hidden expectations?

Ask for “success criteria” instead of vague “how am I doing?” In a July 1‑on‑1, I asked, “What does a successful Q3 rollout look like from your perspective?” The manager replied with a single line: “Meet the timeline.” That single metric became my contract.

  • Judgment: The manager’s avoidance is a filter that only lets through quantifiable goals; you must probe for those explicitly.
  • Framework: The “Three‑Bucket Question” – ask for (1) success metrics, (2) failure signals, (3) escalation path.
  • Not “I need more praise,” but “I need a measurable target.” This shift removes the emotional request that a silent manager can dodge and replaces it with a concrete deliverable they can’t ignore.

How can I protect my career when feedback never arrives?

Document everything and share a concise “decision log” after each 1‑on‑1. In a Q4 debrief, the senior director asked why I had no performance notes; I showed a 12‑page log with dates, decisions, and outcomes. The director’s reaction was, “Now you have a record; you can’t claim you were left in the dark.”

  • Judgment: A silent manager does not absolve you of accountability; it amplifies the need for self‑accountability.
  • Organizational psychology principle: The “self‑efficacy loop” – when external feedback is absent, internal feedback mechanisms become the only source of competence signaling.
  • Not “I’ll wait for their email,” but “I’ll publish my own recap.” The act of publishing forces acknowledgment and creates a paper trail that can be referenced in future performance reviews or internal transfers.

📖 Related:

When should I involve HR or a senior skip‑level?

Only after you have a documented pattern of three consecutive 1‑on‑1s with no actionable input and you have escalated at least once using the “Escalation Blueprint.” In my experience, the first escalation was a Slack thread with the senior TPM, the second was a formal email to the manager’s director, and the third was a calibrated meeting with HR.

  • Judgment: Escalation is a last‑resort lever, not a first‑step complaint.
  • Framework: “Three‑Step Escalation Blueprint” – (1) direct request for feedback, (2) copy senior stakeholder with a summary, (3) schedule HR review with documented logs.
  • Not “I’ll go to HR immediately,” but “I’ll build a factual escalation path.” This protects you from being labeled “complaining” and positions the move as a process‑driven necessity.

How do I keep my motivation high in a feedback vacuum?

Anchor your personal development to external benchmarks: Amazon’s “Leadership Principles” and the Robotics “Technical Competency Matrix.” In my Q1 review, I mapped my quarterly goals to two principles—“Dive Deep” and “Invent and Simplify”—and presented a self‑assessment that the manager could not refute.

  • Judgment: Motivation in a vacuum is sustained by aligning personal metrics with corporate artifacts, not by seeking manager validation.
  • Counter‑intuitive observation: The problem isn’t you lack praise, but you lack an external rubric that the manager cannot ignore.
  • Not “I need their kudos,” but “I need a rubric they respect.” By tying your work to immutable company frameworks, you create a self‑reinforcing loop of achievement that survives managerial silence.

Preparation Checklist

  • Capture three quantitative signals (e.g., defect rate, cycle time, stakeholder NPS) before every 1‑on‑1.
  • Draft a one‑page “Status & Question” memo and send it 15 minutes prior to the call.
  • Record the meeting (audio note) and transcribe key takeaways within 30 minutes.
  • Update a shared “Decision Log” spreadsheet with date, topic, decision, and owners.
  • Use the PM Interview Playbook’s “Structured Preparation System” (the playbook covers the Signal‑Capture‑Iterate loop with real debrief examples).
  • After the call, email a concise recap titled “Action Items – [Date]” to the manager and copy the senior TPM.
  • Review the Leadership Principles matrix weekly and align at least one personal goal to a principle.

Mistakes to Avoid

BAD: Waiting for the manager to volunteer feedback.
GOOD: Proactively ask for concrete success criteria and document the response.

BAD: Sending a vague “How am I doing?” email and filing no follow‑up.
GOOD: Sending a targeted “Three‑Bucket Question” email and logging the reply as a decision point.

BAD: Escalating to HR without a paper trail, which leads to “complaint” labeling.
GOOD: Following the Three‑Step Escalation Blueprint, attaching the Decision Log, and framing the move as a process compliance issue.

FAQ

What if the manager still refuses to give any concrete answer after I ask for success criteria?
The judgment is to treat that refusal as a de‑facto metric—no answer equals “maintain current baseline.” Document the refusal, raise the question to a senior stakeholder, and let the lack of metric become a documented risk in your decision log.

How many 1‑on‑1s should I endure before escalating?
Three consecutive meetings with no actionable input, each documented with a status memo, constitute the minimum pattern before invoking the Three‑Step Escalation Blueprint.

Can I request a different manager without looking like I’m quitting?
Yes, but only after you have a complete decision log and have escalated per the blueprint. Present the request as a “team alignment” need, citing documented gaps rather than personal dissatisfaction.amazon.com/dp/B0GWWJQ2S3).

Your next 1:1 doesn’t have to be awkward.

Get the 1:1 Meeting Cheatsheet → — scripts for tough conversations, promotion asks, and managing up when your manager isn’t great.

    Share:
    Back to Blog

    Related Posts

    View All Posts »