In this article
How a good one-on-one runs
What is a one-on-one, and who owns it?
A one-on-one belongs to the report. GitLab's handbook says the report should add most of the agenda items, and that a manager who adds more than half of them is a sign something is wrong (GitLab 1-1 agenda, September 2025). Say that you use it for support, blockers and growth, and that status can live elsewhere. The engineering manager interview hub places the question in a full loop.
Why it is asked: it shows whether you see the meeting as a status check or as the report's time.
How often should you hold 1:1s?
Weekly is the usual default. GitLab advises at least weekly 1:1s, with a minimum of two live conversations a month, and lets manager and report mix live and written weeks (GitLab 1-1 page, September 2025). Say the rhythm depends on how experienced the report is with the task at hand, so a new hire gets more contact than a veteran, and that you protect the slot instead of moving it for other work.
Why it is asked: interviewers listen for a concrete cadence and a reason for it.
What goes on the agenda?
Use a consistent format that both people add to ahead of time. Cover blockers, the report's priorities, feedback in both directions and, once a month, career growth. GitLab suggests filling the agenda at least a day early so both sides can think (GitLab 1-1 agenda, September 2025). Mention one standing question, such as "what can I do better?", so the report has an open door.
Why it is asked: it shows you run the meeting with a structure and not on mood.
What do you do when the report brings nothing?
Ask open questions, not yes-or-no ones. GitLab suggests prompts such as "what went well since last week?", "what went less well?" and "is there anything I can do to help?", and it warns that "you doing alright?" leaves no room to answer (GitLab 1-1 page, September 2025). Also look for the reason, because silence can mean low trust or a heavy week.
Why it is asked: it tests whether you can create openness when nobody offers it.
How do you talk less than the report?
Aim for the report to speak most of the time. GitLab's page sets a target of 20% of the talking for the manager and 80% for the report (GitLab 1-1 page, September 2025). Use silence, ask a follow-up before offering a view, and keep your own agenda items short. Say you check yourself by asking afterwards who spoke more.
Why it is asked: it separates managers who listen from managers who direct.
How do you use 1:1s for career development?
Hold a separate career conversation about once a month. GitLab's 1-1 page suggests asking which projects the person is proud of, which they struggled with and what they want to learn next, then turning the answers into a growth plan (GitLab career talk, September 2025). Say the report owns the plan and you remove obstacles. See growing engineers for the full set of questions.
Why it is asked: growth is a core manager duty, and a monthly habit is proof you do it.
Giving hard feedback
How do you give hard feedback?
Use situation, behavior and impact, then ask the person's view. The Center for Creative Leadership (CCL) describes situation-behavior-impact (SBI): name the specific setting, describe the observable action without judgement and explain its effect. Its extended version adds intent, so you ask what the person was hoping to achieve (CCL, August 2025).
Why it is asked: vague feedback is the most common failure, and the interviewer wants a method.
Text description of the diagram
- Situation-behavior-impact names the specific setting, describes the observable action without judgement and explains its effect.
- The extended version adds intent, so you ask what the person was hoping to achieve.
How soon should feedback follow the event?
Soon, and not saved for the next 1:1. GitLab says to give positive or negative feedback right away instead of waiting, and to use the face-to-face 1:1 for feedback that is sensitive or being given for a second time (GitLab 1-1 page, September 2025). Say you pick the setting by how sensitive the message is and keep the facts fresh.
Why it is asked: late feedback is a known cause of surprise at review time.
How do you give hard feedback to a low performer without losing their motivation?
Be specific about the gap, specific about the support and honest about the stakes. Tie the feedback to written expectations, name what you will do to help and agree dates to review. Motivation drops when people feel ambushed or judged as a person, so describe behaviour and its effect, and ask what is in the way. The low performer answer gives the five steps.
Why it is asked: it tests whether you can be firm and kind in the same conversation.
Tell me about a time you had a difficult conversation with an employee.
Choose one real conversation and tell it in four beats: what the issue was and why it mattered, how you prepared, what you said using situation, behavior and impact, and what changed afterwards. Include what you would change next time. Keep names out. The situation, task, action, result guide shows how to time each beat.
Why it is asked: stories prove you have done it, and the follow-ups test the detail.
How do you give hard feedback to a peer or to your own manager?
Use the same shape but ask for permission and focus on impact on shared goals. Say what you saw, what it changed for the work and ask for their view, since you have no authority over them. GitLab's meeting guidance also encourages asking your own report what you could improve, which models receiving feedback upward.
Why it is asked: it separates authority-based feedback from influence.
What do you do when the person gets defensive or upset?
Slow down and acknowledge the feeling without retracting the facts. Pause, say you can see this is hard to hear, and return to the specific example. Offer a short break or a second conversation instead of pushing for agreement on the spot. Ask for intent, since it often reveals a misunderstanding on one side.
Why it is asked: real conversations rarely go as planned, and interviewers want your recovery.
How do you receive hard feedback yourself?
Listen without defending, ask for an example, thank the person and decide on one change. Then tell them what you changed, which closes the loop. For a story, see the page on tough feedback you received. Managers who ask for feedback in their own 1:1s make it normal for the team.
Why it is asked: how you take feedback predicts how safe your team feels giving it.
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.
Start Free Trial →Plans and follow-through
How would you build a forward coaching plan?
A coaching plan is a short written agreement with a goal, support and review dates. Start from the cause of the gap, set two or three observable goals, name the help you will give and set a review date. GitLab names coaching, training, tools and a mentor as common supports for a skill gap (GitLab Handbook, September 2025).
Why it is asked: it tests whether feedback leads to action, not only to a talk.
What is the difference between a coaching plan and a performance improvement plan?
Coaching comes first, and a performance improvement plan (PIP) is a later, more formal step. GitLab's underperformance page says to start with documented coaching that is shared with the employee. A written performance letter or PIP may be considered together with employee relations, and in some places the law requires one. GitLab also says it often moves to separation without a formal PIP (GitLab Handbook, September 2025). Say you would follow your company's process and involve human resources early.
Why it is asked: it tests whether you know the order of steps and treat a PIP as a serious step, not a shortcut.
How do you know the feedback landed?
Ask the person to say it back in their own words, then watch for the specific behaviour at the next checkpoint. Agree one observable sign in advance. If nothing changes, treat it as a signal to check whether the message was clear, not only whether the person is willing.
Why it is asked: it shows whether you measure results instead of assuming them.
How do you document feedback?
Keep a short private note after each conversation with the date, the example, what was agreed and the next review. GitLab suggests a shared document visible only to manager and report, because performance feedback should be as private as possible (GitLab 1-1 page, September 2025). Share the note with the person so there are no surprises.
Why it is asked: documentation protects fairness for both sides and supports a later decision.
What if you have to give the same feedback twice?
Treat the second time as more serious. GitLab says a face-to-face meeting suits feedback that is being given for the second time and needs to be taken more seriously (GitLab 1-1 page, September 2025). Ask what blocked the change, make the stakes and the next step explicit, and involve your human resources team if a plan is needed.
Why it is asked: repeat issues test your willingness to escalate fairly.
How the format is scored
Many employers rate each answer on the same scale. Google describes using the same questions and a rubric that illustrates poor, borderline, solid and outstanding answers for structured interviews (Google re:Work, March 2026). Expect your story to be compared with others, so be specific. Read the people management round for how stories map to question families and behavioral interviews for the wider format.
- A one-on-one belongs to the report, who adds most of the agenda.
- Give hard feedback as situation, behavior, impact and a question.
- Give it soon, in the right setting, and write down what was agreed.
- Pair a gap with specific support and review dates.
- Treat repeat feedback as more serious and escalate fairly.
Sources
- 1-1, The GitLab Handbook — GitLab (last modified 2025-09-22), 22 Sep 2025
- Closing the gap between intent vs. impact: the SBII feedback model — Center for Creative Leadership, 19 Aug 2025
- Underperformance, The GitLab Handbook — GitLab (content last updated 2025-09-04), 4 Sep 2025
- A guide to structured interviewing for better hiring practices — Google re:Work (updated March 2026), 1 Mar 2026
