1on1 Meeting Agenda Template for Software Engineer at Amazon During Layoff

In a seven-minute Amazon 1:1, the manager says the reorg is “about capacity,” not performance. That sentence is not clarity. It is a controlled leak. This 1on1 Meeting Agenda Template for Software Engineer at Amazon During Layoff is not a comfort document. It is a classification tool.

The first mistake is treating the meeting like a conversation about feelings. It is not. It is a narrow attempt to learn whether the company is planning to retain, transition, or cut you, and what evidence exists either way. Not reassurance, but classification. Not chemistry, but logistics. Not a future vision, but a decision path.

What is this 1:1 really for during an Amazon layoff?

The meeting is for classification, not closure. If you walk in wanting emotional certainty, you will leave with vague language and a false sense of control.

In a Q3 debrief I sat through, the hiring manager kept saying a candidate was “solid” while the panel asked a different question: could this person absorb a surprise org change and still keep systems alive. The same logic applies here. Your manager may like your work. That is not the question.

The question is whether your name is attached to continuity, transition, or exit. At Amazon, that distinction is often decided above your manager’s pay grade, which means their tone is not the signal. Their wording is. The problem is not your answer; it is the judgment signal you send when you ask for comfort instead of facts.

The first counter-intuitive truth is that the calmer the manager sounds, the less you should trust the room. Calm usually means they have learned the script. It does not mean the answer is good. In practice, a layoff-era 1:1 is a controlled disclosure meeting where each sentence is filtered through HR, finance, and org design. If you force the conversation into performance language, you miss the real layer. Not “How am I doing?”, but “What decision state am I in, and what changes that state?”

Use this line early: “I want to use this meeting to understand my current status, the decision path, and what I should do in the next 7 days.” That sentence works because it narrows the room. It is direct without sounding emotional. It also forces the manager to choose between saying something useful or admitting they cannot.

What agenda should a software engineer bring to the room?

The agenda should be short, explicit, and built to extract one decision path in 30 minutes.

Do not bring a status update. That is the wrong genre. Bring a four-part agenda: 5 minutes on current status, 10 minutes on role continuity, 10 minutes on project handoff and ownership, 5 minutes on next steps and dates. If you have less than that, you are improvising inside a layoff conversation, and improvisation is how people waste their only real chance to reduce uncertainty. The agenda is not a sign of anxiety. It is a sign that you understand the room.

The second counter-intuitive truth is that a detailed agenda is not needy. It is a signal of self-management. In several debriefs I’ve watched, the strongest candidates were not the most polished speakers. They were the ones who made the interviewer’s job easier by sequencing the hard questions cleanly. The same principle applies here. Not “I hope the manager guides me,” but “I will structure the decision so they cannot hide behind vague sequencing.”

A workable agenda sounds like this: “First, I want to confirm what you can share about my role. Second, I want to understand what work is still critical and what would need handoff. Third, I want to know the next date I should expect an update. Fourth, if there are actions I should take this week, I want them in order.” That is not overprepared. It is the minimum viable agenda for a high-friction meeting.

> 📖 Related: amazon-l5-vs-l6-pm-lp-emphasis-customer-obsession-dive-deep

What do vague manager answers actually mean?

Vague answers usually mean the answer exists elsewhere, not that there is no answer.

When a manager says “things are fluid,” the useful interpretation is not that the situation is undecided. The useful interpretation is that the decision has been made somewhere and the communication path has not been authorized yet. At Amazon, that gap is normal during layoff cycles. Managers are often given enough information to coordinate work, not enough to promise safety. So when they hedge, read the hedge as a boundary, not a mystery. Not a lack of intelligence, but a lack of permission.

The third counter-intuitive truth is that vagueness is often a status signal. It tells you where control sits. In one manager conversation I observed, the engineer kept asking, “So am I okay?” The manager answered with three minutes of process language and never once named a date. That was the answer. When people can answer, they usually answer with dates, owners, or next checkpoints. When they cannot, they fill space. Your job is to pull space out of the conversation.

Use this script: “I hear that the process is still open. I am not asking for a promise. I am asking for the next decision point, the owner of that decision, and the date I should use for planning.” That sentence works because it removes drama. It also converts vague language into a testable timeline. If they still cannot answer, you now know more than before. The absence of a date is itself a date-shaped warning.

Which signals matter, and which are noise?

Logistics matter more than tone. People waste time reading friendliness when the real clues are in process behavior.

In a layoff 1:1, the useful signals are whether HR is present, whether the manager is focused on knowledge transfer, whether they ask who else can own your systems, and whether they ask for a list of dependencies you alone understand. Those are transition questions. If the room spends time on process, ownership, and documentation, it is not performance coaching. It is continuity planning. The manager’s tone can still be warm. Warmth is not the signal. Scope is the signal.

This is where most engineers misread the room. They look for emotional cues and ignore operational cues. They search the manager’s face, not the calendar invite. The problem is not that you are bad at reading people.

The problem is that organizations communicate risk through logistics. A meeting moved by 24 hours, a sudden HR join, a request for current project inventory, a question about handoff coverage, a demand to name the only person who knows the deployment path. Those are the breadcrumbs. Not “How nice was the conversation?”, but “What did they need me to map?”

The fourth counter-intuitive truth is that friendliness can be a mask for transition work. I have seen a manager smile through a conversation while quietly asking for the exact service ownership matrix and the names of the secondary approvers. That is not casual curiosity.

That is the company preparing to function without you. If the meeting goes there, do not try to prove loyalty. Ask for specificity: “Which deliverables need a clean handoff by Friday, and who receives each one?” That keeps you inside the operational layer where useful information lives.

> 📖 Related: 2026 Review: Amazon PM Interview Playbook vs. LeetCode for SWE Transitioners

How do you leave with leverage instead of uncertainty?

You leave with leverage by ending the meeting in writing, with dates, names, and next steps.

A good meeting does not end with “Let’s stay in touch.” It ends with a recap you can send the same day. The point is not politeness. The point is memory control. In debriefs, I have watched people lose offers because they relied on oral reassurance and never forced the conversation into a written artifact. Layoff conversations are worse. If it is not written, it will drift. Not because people are dishonest, but because organizations are convenient about memory.

Use this follow-up line: “Thanks. My understanding is X, Y, and Z. If I missed anything, please correct me by EOD tomorrow.” This is the cleanest move in the room. It does three things at once. It creates a paper trail. It tests whether the manager will correct you. It forces the conversation to become operational within 24 hours. If they refuse to correct it, that refusal is also information.

If you are told to support a handoff, be exact: “I can help with a 2-week transition. I need the priorities, the recipient, and the deadline.” If you are told nothing is final, push for a next checkpoint: “What date should I use for the next update, and who owns that communication?” If you are told to keep working, ask what work is still worth doing versus what work is now pure maintenance.

The meeting is not about proving resilience. It is about extracting a plan before the organization extracts your time.

Preparation Checklist

The checklist is about control, not preparation theater.

  • Write down three outcomes before the meeting: stay, transition, or exit. If you cannot name the outcomes, you will chase reassurance instead of facts.
  • Prepare one opening sentence that states your purpose in under 20 seconds. The room should not have to guess why you are there.
  • Bring a 5-line project inventory: service name, your role, critical dependencies, current risk, and who else can step in.
  • Draft two exact scripts for uncertainty: one for timeline, one for handoff. Rehearse them aloud once. Words change under pressure.
  • Save a follow-up template before the meeting starts so you can send the recap in 10 minutes, not 10 hours.
  • Review your severance, last payroll date, benefits end date, and equity vesting timing so you do not ask basic questions under stress.
  • Work through a structured preparation system (the PM Interview Playbook covers layoff-era manager conversations and debrief examples, which is useful when you need to pressure-test your wording before the meeting).

Mistakes to Avoid

The common mistakes are not emotional; they are structural.

  • BAD: “Just tell me if I should be worried.”

GOOD: “What is the next decision point, and what should I do in the next 7 days?”

The bad version asks for reassurance. The good version asks for a planning input.

  • BAD: Defending every project you touched.

GOOD: Naming which work is still critical, which work can be handed off, and which work is dead.

The bad version sounds like self-protection. The good version sounds like an operator who understands triage.

  • BAD: Leaving without a written recap.

GOOD: Sending a same-day summary with dates, owners, and any open questions.

The bad version depends on memory. The good version creates accountability before memory drifts.

FAQ

What if my manager says they do not know yet?

Then they probably do not control the answer. Treat the meeting as a timeline extraction exercise, not a truth revelation. Ask for the next checkpoint, the owner, and the date. If none of those exist, you have learned something real.

Should I ask directly whether I am being laid off?

Only if the room has already moved into transition language or HR is present. Otherwise, the sharper move is to ask for your current status, decision path, and next date. Directness is useful. Premature bluntness just gives them a place to hide.

What if the meeting feels friendly and supportive?

Do not confuse warmth with safety. In layoff conversations, friendliness often coexists with preplanned transition work. Keep the meeting anchored to dates, owners, handoff needs, and written follow-up. The tone is irrelevant. The logistics are the truth.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.

Related Reading

What is this 1:1 really for during an Amazon layoff?