Interview Loops & Rounds

How do you approach one-on-ones with your team, and what do you talk about?

By Interview Clozo · Published 27 October 2026 · Last verified 26 October 2026 · 10 min read

To approach one-on-ones with your team, hold a recurring private meeting with each report on a shared agenda the report shapes, and cover goals, roadblocks, growth and two-way feedback, ending with written action items. The follow-up that separates levels is what you do when a report brings nothing to discuss.

In this article

Before you start
Why interviewers ask this
One-on-ones from first principles
The Staff-level answer
The rubric
Three variants of this question
Common mistakes
Follow-up questions
Sources

Before you start

Where this round sits in a hiring process: interview process and loops.

Why interviewers ask this

Candidates report this question in engineering-manager and other people-management interviews; the Meta engineering manager interview page shows where such rounds sit in a loop. The question tests whether you run a repeatable habit or react to problems as they appear.

A weak answer says "I check in on status and ask if anything is wrong." A strong answer names a rhythm, says who owns the agenda, lists what you cover and says how you follow through. A Staff-level answer adds the trade-off: the time cost, and what you do when the meeting goes flat.

The consequence of a vague answer is a follow-up you cannot answer. Interviewers can ask "what do you do when a report has nothing to say?" or "how do you know it works?" You prepare both below.

For wider preparation, see interview skills and the process pages on the Anthropic interview process and OpenAI interview questions; technical rounds are covered in the AI engineer interview questions.

One-on-ones from first principles

Shared agenda: A shared agenda is a single document, visible to both the manager and the report, where each adds topics before a one-on-one so both people shape how the time is used, not only the manager.
Talk share: Talk share is the part of a meeting's time that one person spends speaking, written as a percentage; in a one-on-one the useful number to watch is the report's talk share.

In plain words

Think of a regular service for a car. You do not wait for the engine to fail; you book a fixed slot, check the usual parts and fix small faults early. The analogy breaks in one place: the person is not the machine, so the person chooses much of what gets checked.

In one precise sentence, a one-on-one is a standing meeting where the report sets much of the agenda, and the manager listens, unblocks and gives feedback.

Google's re:Work guide says its higher-scoring managers were more likely than lower-scoring ones to hold frequent one-on-ones. It also says the meetings can identify issues early. They give the manager a forum for feedback and guidance. They take a large time investment.

A one-on-one repeats four steps: agree the agenda, keep the rhythm, cover the core topics, then close with feedback and actions.CC BY 4.0 — source: How do you approach one-on-ones with your team, and what do you talk about?

Step-by-step description

Both people add to a shared agenda.
A consistent time, every week or two.
Goals, roadblocks and growth; the report talks most.
Ask for feedback and review action items.

Both people add to a shared agenda before each meeting.
Each report gets a consistent time, every week or two.
The report speaks for most of the meeting.
The meeting ends by reviewing action items and what to discuss next time.

Step 1: The report brings the agenda, and you bring a fallback list

Both people add to a shared agenda before each meeting. Google's guide says to set up a shared agenda document and says both manager and team member should contribute. A summary of Rogelberg's Harvard Business Review article reports that both managers and reports rated meetings highest when the report contributed to or set the agenda (summary; article of record: Harvard Business Review (HBR), November 2022).

Now the follow-up trap. Some weeks a report brings nothing. Do not fill the silence with status questions. Bring a fallback list taken from Google's agenda items: "What have you been up to?", "What can I help you with?", roadblocks, goal updates and career development.

Input: the previous notes and the report's topics. Output: an agenda the report recognizes as theirs. You now know who owns the agenda; the next step fixes when you meet.

Step 2: Fix a rhythm and keep it

Each report gets a consistent time, every week or two. Google's guide says to choose a consistent time, generally lasting 30 to 60 minutes, every week or two (Google re:Work).

The arithmetic shows the cost. Take an illustrative team of six reports. At 30 minutes each, weekly, that is 180 minutes, or 3 hours a week.¹ The same six at 60 minutes every other week also come to 3 hours a week on average.¹ The load is equal; the choice is between a tighter loop and longer sessions. In an interview, say which you pick and why: weekly suits new or struggling reports, a longer fortnightly slot suits steady, senior ones.

Avoid cancelling. This is common practice rather than a measured result: a cancelled meeting can tell the report they are low priority.

Step 3: Cover the core topics and let the report talk

The meeting covers the report's goals, roadblocks, growth and a short admin check, and the report speaks for most of it. Gallup's chairman describes a habit of "one meaningful coaching conversation per week" with each team member (Gallup, 2021). That page is an opinion blog, not a study, and it says the conversation can be in person, on the phone, by email, at coffee or in a hallway.

Google's list adds goal updates, roadblocks, administrative topics, career development and coaching. How much the report should speak is advice, not a measured percentage: aim for the report to speak for most of the time, and watch your own talk share.

One illustrative split of 30 minutes: check-in 3, the report's own topics 12, goals and roadblocks 8, feedback 4 and next steps 3.¹ These minutes are an example, not a standard.

In this illustrative split the report's own topics get the largest block of the half hour.CC BY 4.0 — source: How do you approach one-on-ones with your team, and what do you talk about?

Text description of the diagram

One illustrative split of 30 minutes: check-in 3, the report's own topics 12, goals and roadblocks 8, feedback 4 and next steps 3.
These minutes are an example, not a standard.

Step 4: Ask for feedback and close with action items

The meeting ends by reviewing action items and what to discuss next time. Google's guide lists "Review action items and things to discuss in the next 1:1" as the close. It also suggests asking for feedback on yourself, for example "Is there anything I should be doing for you that I am not doing?"

Feedback runs both ways. You give the report specific guidance on their work, and you ask what you should do more or less of. Write down each action item with an owner and open the next meeting by checking them. Follow-through is the part reports remember.

Few organizations train managers for this. Rogelberg's article in HBR, November 2022 notes that few organizations provide strong guidance or training for managers on meeting individually with their employees. So a clear method in your answer stands out.

Knowing it is half the job. Saying it is the other half.

Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.