The promotion packet sits on the table, and the hiring committee does not care about your code quality anymore.

You have spent five years as a Senior Software Engineer at Google, shipping critical infrastructure and optimizing latency by milliseconds. Your peer reviews are glowing. Your manager has whispered that you are "ready for the next level." You assume the transition to Engineering Manager (L6) is a natural progression of your technical excellence. This assumption is the exact reason you will fail your first calibration.

In a Q3 debrief I attended, a candidate with flawless technical metrics was rejected because their 1on1 preparation focused entirely on project status updates rather than team health signals. The committee noted, "They are still acting as a super-IC, not a force multiplier." The problem is not your ability to execute; it is your inability to signal a shift in identity. You are not being evaluated on what you build, but on how you enable others to build. The 1on1 meeting is not a status report; it is the primary instrument of your new leadership strategy. If you treat it as a checklist item, you will remain an Individual Contributor forever.

What is the real purpose of 1on1s when transitioning from IC to Manager at Google?

The sole purpose of your 1on1s during this transition is to gather behavioral data that proves you can manage ambiguity, not to track project completion.

Most engineers treat the 1on1 as a synchronized status update. They walk in, list what they shipped, mention a blocker, and leave. This is efficient for an IC, but it is fatal for a manager candidate.

In a hiring committee discussion for an L6 role, I watched a director dismiss a candidate because their 1on1 notes were purely tactical. The director said, "I see no evidence they understand the emotional velocity of their team." The insight here is counter-intuitive: the less you talk about code in your 1on1s, the more qualified you appear for management. Your goal is to surface the unspoken friction in the team. You need to identify who is burning out, who is disengaged, and where the process is breaking down before it impacts the quarterly OKRs.

Consider the difference in signal. An IC asks, "Is the API migration on track?" A manager asks, "How do you feel about the technical debt we are accumulating during this migration?" The first question yields a binary yes or no. The second yields data about morale, risk tolerance, and team cohesion. During a calibration session for a Google L6 promotion, the committee rejected a candidate whose 1on1 summaries contained zero mentions of career growth conversations.

The feedback was brutal: "They are managing tickets, not humans." You must pivot your 1on1 agenda immediately. Stop reviewing Jira tickets. Start reviewing human potential. If your direct reports cannot articulate their career goals after three 1on1s with you, you have failed as a manager, regardless of your shipping velocity.

The second counter-intuitive truth is that silence is your most valuable tool in these meetings. New managers often fill every second of airtime to prove they are adding value. This is insecurity, not leadership. In a specific debrief regarding a failed internal transfer to management, the hiring manager noted that the candidate interrupted their report three times to offer technical solutions.

The verdict was clear: "They cannot let go of the keyboard." Your job in the 1on1 is to listen until it becomes uncomfortable, then listen more. You are looking for the pause where the real issue hides. When an engineer hesitates to admit they are stuck, that is the moment you manage. If you solve the problem for them instantly, you have robbed them of growth and reinforced your role as the technical safety net.

How should I structure my 1on1 agenda to demonstrate leadership potential?

Your agenda must be 70% focused on their growth and blockers, with only 30% reserved for project alignment, inverted from the typical IC ratio.

The standard IC 1on1 is reverse-chronological: "Here is what I did yesterday, here is what I am doing today." You must destroy this format immediately. A structured agenda for a manager-aspirant looks different. It starts with personal well-being, moves to career trajectory, and only then touches on immediate work context.

In a recent promotion packet review, a candidate included their 1on1 template as an artifact of leadership. The template had a section titled "Blockers I can remove for you" and "One thing you learned this week." The committee praised this specifically because it showed a mindset of service. The problem isn't your lack of organization; it's your misalignment of priorities. You are signaling that their development matters more than your curiosity about their code.

You need a specific script to open these meetings that sets the tone. Do not start with "How's it going?" That invites a superficial "Fine." Instead, use this opening: "What is the one thing causing you the most friction this week, and how can I help clear it?" This forces the conversation toward problem-solving and support.

Another effective script for career-focused 1on1s is: "If you could change one aspect of your role to make you more excited about coming to work, what would it be?" These questions are not small talk; they are data gathering mechanisms. They reveal the structural issues in your team that you, as a future manager, will be responsible for fixing.

The third counter-intuitive insight is that you should document the 1on1 in a shared document, but not for the reasons you think. Most people share docs for transparency. You should share them to model accountability and to create a historical record of growth. However, the content of the doc matters.

Do not write "Discussed Project X." Write "Agreed to pair Program Y with Senior Engineer Z to build mentorship capacity." This language shifts the narrative from task management to team architecture. In a calibration meeting, I saw a candidate's shared notes referenced directly by the VP. The VP pointed to a note from six weeks prior: "Engineer A expressed interest in leading the design doc." The follow-up note said: "Engineer A published design doc; provided feedback on stakeholder management." That trail of evidence secured the promotion. It proved the candidate could identify potential and execute on developing it.

📖 Related: Custom Routing for Inference Optimization: Google Cloud vs AWS for Applied AI Engineers

What specific questions reveal team health issues that Google hiring committees look for?

You must ask questions that expose systemic risks and interpersonal dynamics, as committees prioritize candidates who can detect silent attrition signals.

Google hiring committees are obsessed with retention and team health metrics. They know that a bad manager is the number one cause of voluntary attrition. Therefore, they look for evidence that you can sniff out trouble before it becomes a resignation letter. You cannot ask "Is everyone happy?" You need surgical questions.

Try this: "On a scale of 1 to 10, how sustainable is your current pace for the next three months?" If they say anything below an 8, you dig. "What specifically makes it a 6?" This uncovers the hidden workload or the toxic dependency that your reports are too polite to mention in a group setting. In a debrief for a Site Reliability Engineering (SRE) manager role, a candidate was highlighted because they identified a burnout pattern in their 1on1s two months before anyone quit. The committee called this "proactive risk management."

Another critical area is psychological safety. You need to know if your team feels safe admitting mistakes. Ask this: "Tell me about a mistake you made recently. How did the team react?" If they hesitate or say they haven't made mistakes, you have a culture problem. A strong answer from a report indicates trust.

Your job is to reinforce that trust. In a specific case involving a transition to management for a Cloud team, the candidate used the 1on1 to normalize failure. They shared their own recent error first. The hiring manager noted in the feedback: "This candidate creates an environment where truth can be spoken." That is the signal the committee wants. They do not want a manager who hides problems; they want one who surfaces them early.

You must also probe for alignment gaps. Often, engineers feel disconnected from the broader company mission. Ask: "Do you understand how your current task connects to our quarterly OKRs?" If the answer is vague, you have a communication failure on your part.

The committee expects you to be the translator between high-level strategy and daily execution. In a promotion review, a candidate was dinged because their team could not articulate the "why" behind their work. The feedback stated: "The candidate is a taskmaster, not a leader." Your 1on1s are the venue where you bridge this gap. If you are not having this conversation every other week, you are not preparing for the role.

How do I document 1on1 outcomes to build a promotion case for L6?

Your documentation must explicitly link 1on1 insights to actionable team improvements, serving as auditable proof of your management scope.

You cannot rely on memory. The promotion packet requires concrete artifacts. Your 1on1 notes are those artifacts. However, the way you write them determines their value. Do not write a diary entry. Write a log of interventions.

Every entry should follow a pattern: Observation, Action, Result. For example: "Observed Engineer B struggling with cross-team communication. Action: Paired them with Staff Engineer C for the next design review. Result: Engineer B led the review successfully; reduced review cycle time by 2 days." This format shows causality. It proves you are not just watching; you are influencing outcomes. In a calibration session I chaired, we rejected a candidate whose notes were just summaries of conversations. We promoted the one whose notes looked like a project plan for human capital.

The nuance here is critical. You are not documenting performance reviews; you are documenting coaching moments. There is a distinct difference. A performance review is judgmental and retrospective.

Coaching is forward-looking and developmental. Your notes should reflect the latter. Use phrases like "Developing skill in..." or "Removing barrier to..." rather than "Failed to..." or "Good job on..." This linguistic shift signals to the committee that you view your reports as works in progress that you are actively shaping. In a Google L6 debrief, a director explicitly cited a candidate's note: "Identified gap in SQL knowledge; scheduled workshop with Data Team." This single line demonstrated strategic resource allocation, a key L6 competency.

You must also track the frequency and consistency of these meetings. Missing 1on1s is a red flag. It signals that you prioritize your own work over your team. In a specific instance, a candidate missed three consecutive 1on1s due to "critical production issues." The committee interpreted this as an inability to delegate.

The verdict was: "If they cannot protect 30 minutes for their team during a crisis, they will not protect them during normal operations." Consistency is a leading indicator of reliability. Your documentation should show a perfect streak. If you have to cancel, reschedule immediately and document the reason as a learning moment about prioritization. This turns a negative into a demonstration of accountability.

📖 Related: Google APM vs Meta RPM: Which Rotational Programs Is Better in 2026?

Preparation Checklist

  • Invert your agenda template: Replace "Status Update" with "Growth & Blockers" as the first item, ensuring 70% of the time is dedicated to the report's needs.
  • Script your opening question: Memorize and use the friction-focused opener: "What is the one thing causing you the most friction this week?" to bypass small talk.
  • Implement the Observation-Action-Result logging format: Rewrite your last three 1on1 notes using this structure to practice linking insights to interventions.
  • Schedule a mock calibration: Ask a current L6 manager to review your 1on1 notes and tell you exactly where they see "IC behavior" vs "Manager behavior."
  • Audit your listening ratio: Record your next 1on1 (with permission) and measure your talk time; if it exceeds 40%, you are failing the transition.
  • Work through a structured preparation system (the PM Interview Playbook covers leadership transition frameworks with real debrief examples): Adapt the stakeholder mapping exercises from the playbook to identify hidden influencers in your current team before your next 1on1.
  • Create a "Career Trajectory" doc for each report: Draft a one-page summary of each report's goals based on your last conversation to prove you are thinking long-term.

Mistakes to Avoid

Mistake 1: The Technical Savior Complex

BAD: Your report mentions a bug. You immediately say, "Show me the code, I'll fix it," and spend the rest of the meeting pair programming.

GOOD: Your report mentions a bug. You ask, "What approaches have you considered?" and guide them to the solution without touching the keyboard.

Judgment: Solving the problem for them proves you are still an IC. Guiding them to solve it proves you are a manager.

Mistake 2: The Agenda-less Drift

BAD: You start the meeting with "What's up?" and let the conversation wander until 30 minutes are gone, ending with no action items.

GOOD: You send an agenda 24 hours in advance, stick to the three key topics, and end with clear owners and deadlines for follow-ups.

Judgment: Unstructured 1on1s signal a lack of respect for your report's time and a lack of strategic intent.

Mistake 3: The Feedback Vacuum

BAD: You spend the entire meeting listening to their problems but offer no synthesis, no pattern recognition, and no directional advice.

GOOD: You listen for 20 minutes, then spend the last 10 summarizing the themes you heard and proposing a strategic shift for the next sprint.

Judgment: Listening without synthesizing is passive. Management requires active interpretation of data to drive team direction.

FAQ

Can I get promoted to L6 without managing people directly at Google?

No, not for the standard Engineering Manager track. While Tech Lead roles exist, the L6 management band explicitly requires evidence of people management, including hiring, firing, and career development. The committee looks for 1on1 artifacts that prove you have handled personnel issues. Without this, you remain on the Individual Contributor ladder, regardless of your technical scope.

How many 1on1s do I need to document for my promotion packet?

There is no hard number, but quality outweighs quantity. A packet with six deep, transformative 1on1 records is better than twenty superficial status checks. However, you should aim for at least three months of consistent weekly meetings with at least two direct reports or mentees. The committee needs to see a trend of behavior, not a one-off experiment. Consistency over a quarter is the minimum bar for proof.

What if my current manager refuses to let me lead 1on1s?

This is a structural blocker you must escalate. If your manager will not give you the opportunity to practice, you cannot build the case for promotion. Request a formal "acting manager" period or ask to shadow another manager's 1on1s. If neither is possible, you must consider an internal transfer to a team where leadership opportunities are available. Staying in a role that denies you management reps guarantees stagnation.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 the real purpose of 1on1s when transitioning from IC to Manager at Google?