1:1 Meeting Basics: A Guide for New Tech Employees

TL;DR

Schedule your first 1:1 within two business days of starting, keep it to a strict 30‑minute block, and treat it as a data‑gathering session rather than a performance review. New hires who focus on learning their manager’s communication style and immediate priorities in these early meetings build trust faster and avoid misaligned expectations. Treat every 1:1 as a recurring experiment: set a tiny hypothesis, test it, and adjust the agenda based on what you learn.

Who This Is For

This guide is for engineers, designers, product analysts, and other individual contributors who have just joined a mid‑size or large tech company and have never run a 1:1 with a manager before. If you are in your first 90 days, unsure whether to bring a notebook or a slide deck, and want to know how to turn these meetings into a lever for early impact rather than a checkbox exercise, the advice below applies. Senior individual contributors or managers looking for advanced coaching techniques should seek other resources.

How often should I schedule my first 1:1 with my manager?

Set the first 1:1 within 48 hours of your official start date, ideally before you finish any onboarding paperwork. In a Q3 debrief at a Series C SaaS firm, the hiring manager noted that new hires who waited until the end of week one to meet their manager reported feeling “out of the loop” on critical sprint goals, while those who met within two days could ask clarifying questions about the current backlog and adjust their initial task list immediately.

A 30‑minute recurring slot works for most teams; if your manager’s calendar is tightly packed, propose a 15‑minute check‑in now and a full 30‑minute slot for the following week. The goal is not to fill time but to create a predictable rhythm that signals you respect their schedule while securing a dedicated channel for information flow.

What should I talk about in a 1:1 meeting as a new hire?

Treat the agenda as a lightweight diagnostic: spend the first five minutes confirming logistics (meeting cadence, preferred communication tool, escalation path), then allocate ten minutes to learn about the team’s current priorities and ten minutes to share your own early observations and questions.

In a hiring committee discussion for an L4 role at a FAANG‑adjacent company, a senior engineer explained that new hires who opened with “What does success look like for this squad in the next six weeks?” received clearer direction than those who began with a personal status update. Do not use the meeting to showcase your accomplishments; use it to surface gaps in your understanding and to validate assumptions about the product roadmap, stakeholder map, or upcoming deadlines.

How do I prepare for a 1:1 meeting without wasting time?

Create a three‑item template that you fill out five minutes before the call: (1) one fact you learned since the last meeting, (2) one question that blocks your progress, and (3) one suggestion or observation that could help the team. In a mid‑year review at a cloud infrastructure provider, managers reported that employees who used this template reduced meeting overruns by an average of seven minutes because the conversation stayed focused on actionable items rather than vague updates.

Keep a running note in a shared doc or a personal notebook; before each meeting, spend no more than sixty seconds reviewing the previous notes and filling out the template. This habit prevents the common pitfall of walking in unprepared and defaulting to a generic “How are you?” opener that yields little insight.

What are the signs that my 1:1 is ineffective and how to fix it?

If you leave the meeting without a clear next step, if the conversation repeatedly drifts into unrelated gossip, or if your manager spends more than half the time talking about their own workload, the 1:1 is not serving its purpose.

In a retro at a mobile gaming studio, a tech lead realized that his 1:1s had become status‑report sessions after three consecutive meetings ended with no action items; he reset the expectation by explicitly stating at the start of the next call, “I want to use this time to uncover one obstacle I can help remove.” The fix is to co‑create a working agreement: agree on a maximum length, a shared note‑taking space, and a rule that each party must bring at least one topic that requires the other’s input. When the agenda feels stale, introduce a lightweight experiment—for example, try a “reverse 1:1” where you ask the manager for feedback on your communication style for ten minutes, then swap roles.

How can I use 1:1s to influence my career growth and get feedback?

Frame each 1:1 as a data point in a longer‑term feedback loop: after every meeting, write down one piece of concrete feedback you received and one specific action you will take before the next check‑in.

In a promotion packet review at a late‑stage startup, the HRBP highlighted that candidates who could show a progression of “feedback → action → measurable outcome” across six 1:1s were 40 % more likely to receive a mid‑cycle raise than those who only discussed project updates. Do not wait for the formal review cycle to ask about career paths; instead, ask your manager, “Based on what you’ve seen in my first month, what skill should I prioritize to be ready for the next level?” and then track your progress against that answer in subsequent meetings.

Preparation Checklist

Block a recurring 30‑minute slot on both calendars within the first two business days
Draft a three‑item template (fact, question, suggestion) and keep it in a readily accessible note
Research your manager’s recent public communications (blog posts, internal talks) to align your questions with their current focus
Prepare one observation about the team’s workflow that you can share neutrally (e.g., “I noticed the daily stand‑up runs ten minutes over; is that a known bottleneck?”)
Work through a structured preparation system (the PM Interview Playbook covers effective stakeholder communication patterns with real debrief examples)
Set a reminder to spend no more than five minutes reviewing the previous meeting’s notes before each new 1:1
End each meeting by confirming the next meeting’s time and any agreed‑upon action items

Mistakes to Avoid

BAD: Showing up with a list of completed tasks and asking for praise.
GOOD: Bringing one question that uncovers a hidden dependency, such as “I’m unsure which team owns the API rate‑limit thresholds—can you point me to the owner?” This shifts the focus from self‑promotion to problem‑solving and gives the manager a concrete way to help.

BAD: Letting the meeting run over because you keep adding new topics as they come to mind.
GOOD: Setting a visible timer at the start and politely saying, “We have five minutes left; let’s capture any remaining points in the shared doc and follow up via Slack.” This respects both parties’ time and trains the habit of concise communication.

BAD: Treating the 1:1 as a one‑way status update where you only report what you’ve done.
GOOD: Preparing a short retrospective on what helped you be productive and what slowed you down, then asking, “Based on what you’ve seen, is there a process tweak you’d recommend?” This invites coaching and signals that you view the manager as a partner in your effectiveness.

FAQ

How long should I wait before asking for feedback on my performance?

Ask for specific, behavior‑based feedback in your second or third 1:1, not in the first meeting. Early on, focus on learning expectations; after you have demonstrated a few weeks of work, you can say, “In the last sprint I noticed my code review turnaround was slower than the team average—what one change would you suggest I try?” This shows initiative and gives the manager a concrete context to evaluate.

Is it appropriate to discuss personal career goals in a 1:1?

Yes, but only after you have established trust and demonstrated reliability. In the first month, keep the conversation centered on team objectives and immediate blockers. Once you have delivered a couple of small wins, you can allocate five minutes to ask, “What experiences or projects would help me build the skill set needed for a senior role here?” This timing ensures the manager sees you as invested in the team’s success before you ask for investment in your growth.

What if my manager cancels or repeatedly reschedules our 1:1?

Treat a cancellation as a signal to clarify the meeting’s value, not as a personal slight. Send a brief note: “I noticed our 1:1 got moved; I want to make sure this time is useful for you. Could we agree on a standing slot or a shorter async check‑in if calendar conflicts persist?” If the pattern continues after two attempts, escalate to your skip‑level manager or HR partner with factual examples of missed meetings and the impact on your ability to align on priorities.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.