The first 1on1 with your manager as a Google intern isn’t about impressing — it’s about alignment. Most interns waste it on updates; the ones who succeed treat it as a calibration session for expectations, autonomy, and feedback loops. Your goal isn’t visibility — it’s establishing the rhythm and trust that will define your summer.
1on1 for Intern Engineer at Google: First Meeting Guide for Beginners
TL;DR
The first 1on1 with your manager as a Google intern isn’t about impressing — it’s about alignment. Most interns waste it on updates; the ones who succeed treat it as a calibration session for expectations, autonomy, and feedback loops. Your goal isn’t visibility — it’s establishing the rhythm and trust that will define your summer.
Running effective 1:1s is a system, not a talent. The 0→1 SWE Interview Playbook (2026 Edition) includes agenda templates and question banks for every scenario.
Who This Is For
This guide is for first-time software engineering interns at Google who’ve never had a formal 1on1 with a full-time manager. It’s for students from non-target schools who don’t have alumni mentors inside Mountain View, and for those whose only exposure to tech culture is through YouTube clips and Reddit threads. If you’re walking into your first Google 1on1 nervous about what to say — not because you lack skill, but because the norms are opaque — this is your map.
What Should I Actually Say in My First 1on1 with My Manager?
Say this: “I want to understand what good looks like for me this summer.”
That sentence ends debates. In a Q3 intern debrief I sat in on, two managers argued over whether an intern had underdelivered. One said the code was clean; the other said impact was low. The difference? One had clarified expectations week one. The other hadn’t.
The first 1on1 is not a status update. It’s a negotiation of scope, feedback frequency, and success metrics. Most interns open with “Here’s what I did last week” — bad move. You’re not behind. You’re setting the table.
Not every manager will spell out expectations. That’s by design. Google assumes you’ll probe. If you don’t, they assume you’re passive. One L6 told me, “If an intern waits for me to hand them a todo list, they’re not ready for level 5.”
Say: “What does a strong intern look like on your team?” Then: “How will I know if I’m on track?” Then: “What’s one thing I should start doing, stop doing, or do more of?”
These aren’t scripts — they’re forcing functions. They make vague expectations concrete.
How Often Should I Expect 1on1s as a Google Intern?
You should expect weekly 30-minute 1on1s with your manager, starting the first week.
Missed or irregular meetings are a leading indicator of low manager engagement. In one HC (Hiring Committee) review, an intern received mixed feedback not because of code quality, but because their manager hadn’t met with them in 18 days. The comment: “No rhythm, no trust, no narrative.”
Don’t wait to be scheduled. Forward your calendar invite the day you start. Title it: “Weekly 1on1 – [Your Name] & [Manager] – Starting [Date].” Include a recurring slot. If they decline, propose two alternatives within 48 hours.
Not showing initiative in scheduling is interpreted as low ownership. One L5 said in a debrief, “I don’t care if they know C++. I care if they own their growth.”
Google operates on calendar authority. If it’s not scheduled, it doesn’t exist.
What Questions Should I Ask My Manager in the First Meeting?
Ask questions that reveal unspoken norms, not just tasks.
Start with: “What’s the one project this team can’t afford to get wrong this quarter?” That surfaces priority. Then: “Where do interns usually add the most value here?” That reveals role archetypes. Then: “How do you prefer to receive updates — async in chat, email, or in person?” That decodes communication style.
One intern asked, “Who on the team should I build a working relationship with first?” The manager paused, then said, “You’re the first intern to ask that.” They ended up getting pulled into a high-visibility bug bash because the manager assumed intent.
Not all questions are equal. Asking “What tools do we use?” shows you’re preparing. Asking “What’s your management philosophy?” shows you’re assessing fit — which is risky early. Save that for week three.
Bad questions are vague: “Anything I should know?” Good ones are targeted: “What’s one thing you wish last summer’s intern had done earlier?”
Each question should serve one of three goals: clarify success, reduce uncertainty, or build trust. If it doesn’t do at least one, don’t ask it.
Should I Prepare a Document or Agenda for the First 1on1?
Yes — prepare a lightweight agenda and send it 24 hours in advance.
Not a 10-page deck. A 4-bullet Google Doc titled “[Your Name] – 1on1 Prep – [Date].” Include:
- One goal for the internship
- One area you want feedback on
- One question about team dynamics
- One logistical item (e.g., access requests)
In a debrief, a hiring manager pointed to this doc as the reason an intern got converted. “They weren’t just showing up — they were structuring the conversation. That’s L4 behavior.”
Google runs on shared docs. No doc, no discussion. If you walk in with nothing written, the assumption is you’re disorganized or unprepared.
Not sending an agenda signals passivity. Sending a novel signals you don’t understand scope.
One intern attached a 12-slide presentation to their 1on1 invite. The manager replied: “Let’s start with 3 bullets.” The intern was never invited to another meeting.
Keep it lean. Make it editable. Leave space for manager input.
How Do I Build Trust with My Manager During the First 1on1?
You build trust by demonstrating judgment, not effort.
Most interns lead with “I’ve been reading code and setting up my dev environment.” That’s table stakes. It’s not trust-building — it’s noise.
Say instead: “I reviewed the onboarding doc and noticed the testing guide hasn’t been updated since Q1. Should I flag gaps as I find them?” That shows pattern recognition.
Or: “I spoke with [peer] and learned we’re migrating to Bazel next month. I started a sandbox build — want me to share findings?” That shows initiative with boundaries.
Trust isn’t built through hours logged. It’s built through discretionary actions that align with team goals.
One intern asked, “Is there a bug you’ve been meaning to fix but haven’t had time for?” They were handed a P2 that had been lingering for six weeks. They fixed it in three days. That became their conversion story.
Not action, but judged action. The difference between “I did something” and “I did the right thing.”
Managers don’t trust busywork. They trust relevance.
How Do I Handle Feedback in My First 1on1?
Ask for feedback — don’t wait for it.
Say: “What’s one thing I could do better in my first two weeks?”
Then listen. Don’t defend. Don’t explain. Nod. Take notes. Say: “I’ll work on that. Can we check in on it next week?”
In a hiring committee, an intern was downgraded because they “took feedback personally.” The evidence? In their first 1on1, when told their CLs were too large, they said, “But the guide says to batch changes.” That wasn’t pushback — it was defensiveness.
Google values feedback velocity. The faster you absorb, the faster you adapt. Defensiveness is a red flag for low coachability.
Bad response: “I wasn’t sure what you wanted, so I did my best.”
Good response: “I’ll break future CLs into smaller scopes. Can you let me know if the size feels right next time?”
One L6 told me, “I don’t need perfect work. I need someone who gets better every week.”
Your first 1on1 is the baseline. The feedback you get there becomes the metric for growth. Ignore it, and you’re stuck at step one.
Preparation Checklist
- Send a calendar invite for a recurring 30-minute 1on1 within 24 hours of start date
- Draft a 4-bullet agenda: goal, feedback area, question, logistics
- Research your team’s Q3 OKRs — even if not shared, infer from product area
- Prepare three questions that uncover norms, not just tasks
- Ask for feedback in the first meeting — don’t wait
- Track action items in a shared doc and close them by next week
- Work through a structured preparation system (the PM Interview Playbook covers intern 1on1 dynamics with real debrief examples from Google L5 and L6 managers)
Mistakes to Avoid
BAD: Showing up with no agenda and saying, “I’ve been getting set up.”
This communicates you’re reactive. You’re not driving your own development.
GOOD: Sending a pre-read with a clear ask: “I want to understand what a strong first month looks like.” This shows ownership and focus on outcomes.
BAD: Asking broad questions like “How can I be successful?”
This is lazy. It puts the burden on the manager to define success for you.
GOOD: Asking, “What’s one outcome you’d want to see from me by week 4?” This forces specificity and creates a measurable target.
BAD: Defending your work when given feedback.
Saying “I followed the guide” in response to critique signals rigidity, not process adherence.
GOOD: Saying “I’ll adjust and show you the next version” — this shows learning orientation and respect for the feedback loop.
FAQ
What if my manager cancels or reschedules the first 1on1?
Reschedule immediately. If they miss two attempts, loop in your mentor or program manager. No 1on1 in the first 10 days is a risk signal. One intern lost conversion because their manager was MIA — but they didn’t escalate. Ownership means protecting your growth space.
Should I bring up mentorship or career advice in the first meeting?
No — save career advice for week 3 or later. The first 1on1 is for role alignment, not long-term paths. Bringing it up early makes you seem distracted by the wrong outcomes. Focus on the summer, not the next job.
Is it okay to send follow-up notes after the 1on1?
Yes — send a 3-bullet summary within 4 hours. Include: decisions, action items, open questions. Not for credit — for clarity. One manager said, “I judge intern ownership by who sends notes without being asked.” It’s a stealth signal of operational rigor.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.