Top 3 One to ones Interview Questions
Browse 3 real-world technical and behavioral interview questions about One to ones. Review scenarios, edge cases, and architectural best practices.
What do you use one-to-ones for, how do you give feedback that lands, and where does your responsibility for someone's growth end?
One-to-ones are the engineer's time for the things that do not fit anywhere else, not a status meeting. Feedback lands when it is specific, close to the event, about behaviour and its effect, and carries a request. Growth is owned by the engineer; the manager owns opportunity, honest signal and air cover.
One of your engineers is working most evenings, has become short with people in code review, and the date has not moved. They tell you they are fine. What do you do?
Act on the behaviour you can observe rather than waiting for a disclosure, open with what you have seen instead of a question they can deflect, then remove named work rather than offering sympathy. Check your own part in the load, and know the point where this stops being a management conversation.
One of your strongest engineers tells you they are thinking about leaving. What do you do?
Separate the conversation about why from any conversation about money, find out whether the cause is something you can genuinely change, be honest that a counter-offer rarely fixes a non-financial reason, and treat the knowledge and morale consequences as work that starts the same week.