1on1 for New Grad Engineers at Microsoft: How to Build a Strong Manager Relationship

TL;DR

Build trust by treating each 1on1 as a data‑gathering session, not a status update. Prepare three concrete topics — progress on current work, blockers you own, and one learning goal — before every meeting. Use the first 90 days to establish a rhythm of weekly 1on1s, then shift to biweekly once your manager confirms you are meeting expectations.

Who This Is For

This guide targets recent graduates entering Microsoft as Software Engineer I (SDE I) or equivalent roles, who have completed the standard four‑round interview loop (coding, system design, behavioral, and diversity & inclusion) and are within their first six months on the job. It assumes you have a designated manager who holds regular 1on1s and that you are on a product team with quarterly OKRs. If you are in a research lab or a rotating internship program, adapt the cadence but keep the core principles of preparation and feedback.

How often should I have 1on1s with my manager as a new grad engineer at Microsoft?

The default cadence is weekly for the first six weeks, then biweekly thereafter unless your manager signals a need for more frequent check‑ins. In a Q3 debrief, a senior manager noted that new grads who skipped weekly 1on1s in month two were perceived as disengaged, even when their code output was strong.

The first 1on1 should occur within three business days of your start date; treat it as a contract‑setting conversation where you clarify expectations around response time, meeting length, and preferred communication channel (Teams chat vs. Outlook). After the initial month, propose a shift to biweekly only after you have demonstrated consistent delivery on at least two small, well‑scoped tasks.

What should I talk about in my first 1on1 with my Microsoft manager?

Use the meeting to surface three data points: (1) a summary of your onboarding tasks completed, (2) one specific blocker you cannot resolve alone, and (3) a skill you want to develop that aligns with the team’s quarterly goal.

In a recent HC discussion, a hiring manager rejected a candidate’s self‑rating because the new grad spent the entire 1on1 listing completed trainings instead of asking for clarification on ambiguous API ownership. Your opening sentence should state the purpose: “I’d like to align on my current priorities and identify where I need your input.” Keep each point under 90 seconds; your manager will use the remaining time to coach or redirect.

How do I get actionable feedback from my manager in 1on1s?

Frame feedback requests as a request for observable behavior, not a vague opinion. Instead of asking “How am I doing?” say “In the last sprint, I raised two blockers in the daily stand‑up; did those updates help the team unblock work faster?” A manager in a mid‑year review told a new grad that the most useful feedback came when the engineer cited a specific commit hash and asked whether the comment style matched the team’s guide.

After receiving feedback, repeat it back in your own words and note one concrete change you will implement before the next 1on1. If the manager’s response is vague, ask for a single metric you can track — such as code review turnaround time — to turn the insight into a measurable goal.

How can I use 1on1s to influence my early performance review at Microsoft?

Treat each 1on1 as a chance to collect evidence for your self‑review: document decisions you influenced, metrics you improved, and learning you applied. In a calibration meeting last fall, a manager advocated for a new grad’s “exceeds” rating because the engineer had logged three instances where a 1on1 surfaced a dependency that, once resolved, saved the team two days of sprint time.

Bring a one‑page summary to the mid‑checkpoint discussion that lists: (a) OKR contributions, (b) feedback loops closed, and (c) areas where you sought mentorship. This shifts the conversation from subjective impression to objective impact, making it harder for reviewers to downgrade your rating based on recency bias.

What are the signs my 1on1 is not working and how to fix it?

A stagnant 1on1 feels like a status report with no follow‑up items; if you leave the meeting without at least one action you own or one clarification you received, the format is broken. In a recent debrief, a manager complained that a new grad treated the 1on1 as a “show‑and‑tell” of completed tickets, resulting in zero new insights for either party.

To fix it, propose a new structure: start with a two‑sentence update, then spend five minutes on a blocker you need help with, and close with a question about the team’s upcoming priority. If your manager consistently deflects or cancels, escalate to your skip‑level after two missed sessions, citing the impact on your ability to meet sprint goals.

Preparation Checklist

Block 15 minutes on your calendar 24 hours before each 1on1 to review your task board and note any blockers.
Write three bullet points: progress since last meeting, one obstacle you need help with, and one learning objective tied to a team OKR.
Identify a specific piece of work (e.g., a pull request or design doc) you can reference to make your points concrete.
Prepare a single, measurable question for your manager (e.g., “Does the API latency target of 50 ms still hold for this feature?”).
Work through a structured preparation system (the PM Interview Playbook covers communication frameworks that also apply to engineering 1on1s with real debrief examples).
After the meeting, send a brief Teams message summarizing agreed‑upon actions and deadlines.
Review your notes at the end of each week to spot patterns in recurring blockers or feedback themes.

Mistakes to Avoid

BAD: Treating the 1on1 as a monologue about what you finished.

GOOD: Use the first minute to state what you need from your manager, then give a concise update that leads directly into that request.

BAD: Accepting vague praise like “good job” without asking for specifics.

GOOD: Respond with “Thank you. Could you point to the part of my code or design that you felt was most effective?” to turn praise into actionable insight.

BAD: Waiting for the manager to set the agenda and then showing up unprepared.

GOOD: Send a one‑line agenda in the meeting invite (“Discuss blocker on service X, feedback on recent code review, learning goal for observability”) and stick to it.

FAQ

How long should each 1on1 last?

Aim for 25‑30 minutes for the first two months; if you consistently finish early, ask your manager whether they’d like to use the extra time for deeper topic exploration or to end early.

What if my manager cancels our 1on1 repeatedly?

After two consecutive cancellations, send a brief note stating that you need clarity on priorities to stay aligned with sprint goals and request a reschedule within 48 hours; if the pattern continues, involve your skip‑level with the same factual request.

Should I discuss compensation or promotion in my 1on1s?

Compensation conversations belong in the formal review cycle; use 1on1s to discuss the skills and impact that will support a future promotion discussion, not to ask for a raise or stock adjustment directly.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.