MBA Grad Manager: First 1on1 with a Senior IC at Google

Quick Answer

Your first 1on1 with a senior IC is a judgment session, not a status update. Focus on demonstrating impact awareness, listening for the IC’s unspoken priorities, and establishing a cadence for mutual accountability. Treat the conversation as a mini‑product review where you are the PM and the IC is your key stakeholder.

TL;DR

Who This Is For

This guide is for MBA‑qualified managers who have just joined Google at L4 or L5 and are scheduled to meet a senior individual contributor (IC) within their first 30 days. You likely have limited exposure to Google’s engineering‑first culture and need to translate managerial instincts into signals that resonate with deep technical peers. The advice assumes you have completed onboarding but have not yet shipped a measurable outcome in your new org.

How Should I Set the Agenda for My First 1on1 With a Senior IC at Google?

Define the meeting as a two‑way product review, not a manager‑led check‑in. Begin by stating that you want to understand the IC’s current priorities, constraints, and definition of success, then share your own objectives for the team. In a Q3 debrief, a hiring manager noted that candidates who opened with a rigid agenda were perceived as overly procedural, while those who asked open‑ended questions about the IC’s roadmap earned immediate trust.

Prepare three bullet points: (1) the IC’s active projects and their timelines, (2) any blockers they perceive in cross‑functional collaboration, and (3) one outcome you hope to influence in the next quarter. Keep each point under ten words to respect the IC’s time. Avoid the temptation to list your managerial responsibilities; instead, frame them as enablers for the IC’s work.

Not X, but Y: The problem isn’t filling the slot with updates — it’s probing for the IC’s judgment on what “good” looks like.

What Specific Topics Should I Cover to Demonstrate Impact as an MBA Grad Manager?

Center the conversation on impact metrics that matter to the IC, such as system reliability, feature adoption velocity, or technical debt reduction. In a recent HC discussion, a senior IC dismissed an MBA grad manager who led with “I will improve team morale” because the phrase lacked a measurable tie to engineering outcomes. Instead, cite a concrete lever: you plan to reduce context‑switching by implementing a bi‑weekly sync that cuts meeting overhead by 15%, thereby freeing up to 10 hours per engineer per month for deep work.

Reference any data you have from your first weeks: ticket volume trends, CI/CD pipeline latency, or results from a pilot retrospection you facilitated. If you lack hard numbers, describe the hypothesis you are testing and the metric you will track. Senior ICs respect experiments with clear success criteria, even if the outcome is pending.

Not X, but Y: The problem isn’t showcasing your MBA toolkit — it’s translating those tools into levers that move the IC’s key results.

How Do I Navigate Power Dynamics and Build Trust With a Senior IC?

Recognize that senior ICs derive authority from technical expertise, not hierarchical position. Your role is to reduce friction, not to direct. In a debrief after a L5 manager’s first 1on1, the senior IC remarked that the manager earned credibility by asking, “What technical decision are you most uncertain about right now?” and then offering to gather data or coordinate with stakeholders to clarify the uncertainty.

Adopt a listening‑first posture: allocate 70% of the time to the IC’s perspective, summarizing their points before adding your view. Use phrases like “If I understand correctly, you’re concerned about X because Y” to confirm comprehension. Avoid offering solutions prematurely; instead, ask what support would help them test their hypothesis faster.

Not X, but Y: The problem isn’t asserting authority early — it’s earning influence by demonstrating that you can amplify the IC’s impact.

What Signals Do Senior ICs Listen For That Indicate Managerial Readiness?

Senior ICs listen for three signals: (1) your ability to surface hidden trade‑offs, (2) your comfort with ambiguity, and (3) your track record of removing impediments without overstepping. During an HC review, a senior IC cited a manager who, when asked about a delayed launch, responded, “The blocker is the API contract timeline; I’ve scheduled a joint design review with the provider’s team to explore a fallback.” That answer showed trade‑off awareness, proactive coordination, and restraint from dictating technical details.

Prepare to discuss a recent situation where you identified a misalignment between product goals and engineering capacity, and how you facilitated a resolution that preserved both intent and technical integrity. Highlight any metrics that improved as a result, such as reduced rework or faster rollback times.

Not X, but Y: The problem isn’t proving you can manage people — it’s proving you can manage the interface between product intent and technical execution.

How Do I Follow Up After the First 1on1 to Maintain Momentum?

Treat the 1on1 as the first iteration of a feedback loop; send a concise summary within 24 hours that captures agreed‑upon actions, owners, and due dates. In a post‑mortem of a stalled project, a senior IC noted that managers who failed to document decisions created ambiguity that eroded trust over weeks.

Include three items in your note: (1) a restatement of the IC’s top priority for the next month, (2) the specific support you will provide (e.g., “I will reserve two hours each Thursday for ad‑hoc clarification”), and (3) a request for confirmation or correction. Attach any relevant artifacts — meeting notes, a draft RACI, or a link to a shared tracker — so the IC can verify alignment without chasing you.

Not X, but Y: The problem isn’t ending the meeting with a handshake — it’s locking in shared understanding before the next context switch occurs.

Preparation Checklist

Review the senior IC’s public contributions (code commits, design docs, talk videos) to understand their technical focus areas
Draft three open‑ended questions that probe the IC’s current challenges and definition of success
Identify one recent team metric you can influence and prepare a hypothesis‑driven experiment to test it
Practice summarizing the IC’s points in your own words before offering your perspective
Schedule a 15‑minute buffer after the 1on1 to capture immediate notes while the conversation is fresh
Work through a structured preparation system (the PM Interview Playbook covers stakeholder alignment techniques with real debrief examples)
Set a calendar reminder to send the follow‑up summary within 24 hours of the meeting

Mistakes to Avoid

BAD: Opening the 1on1 with a list of your managerial achievements and how you plan to “raise the bar” for the team.

GOOD: Opening with, “I’ve seen you lead the migration to the new storage system; what aspects of that effort are you most proud of, and where do you see the next opportunity for improvement?” This shows you have done your homework and positions you as a learner.

BAD: Promising to resolve a technical blocker without first confirming the IC’s diagnosis of the problem.

GOOD: Saying, “I understand the latency spike may stem from the new caching layer; can we walk through the data you’ve collected so I can help design a test to isolate the variable?” This respects the IC’s expertise while offering concrete assistance.

BAD: Ending the meeting without capturing any action items, assuming the IC will remember what was discussed.

GOOD: Sending a follow‑up note that states, “Per our conversation, I will arrange a sync with the infra team on Tuesday to review the fallback options; please let me know if that timing works or suggest an alternative.” This creates accountability and demonstrates reliability.

FAQ

How long should the first 1on1 last?

Aim for 30‑45 minutes. Senior ICs often block longer slots but expect the conversation to stay focused; if you sense the discussion drifting, politely steer back to the agreed agenda.

What if the senior IC seems disengaged or gives short answers?

Interpret this as a signal that they are waiting for you to demonstrate substance. Shift to a specific, data‑driven question about a current project (“You mentioned the rollout stalled at stage three — what metric are you watching to decide whether to proceed?”). Re‑engagement usually follows when the IC sees you speaking their language of metrics and trade‑offs.

Is it appropriate to ask about career progression or promotion timelines?

Not in the first 1on1. Senior ICs view early conversations as opportunities to align on work impact, not personal advancement. Save career‑related topics for later check‑ins once you have established a track record of delivering on the team’s objectives.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.