50 one-on-one meeting questions for engineering managers

A good one-on-one lives or dies on the questions you ask. Ask only “how’s it going?” every week and you’ll get “fine” every week — and miss the quiet frustration, the half-formed career itch, the blocker your engineer has stopped mentioning because nothing changed last time. The right question, asked at the right moment, is the difference between a status update and a conversation that actually moves someone.

Below are 50 questions grouped by what they’re for. You won’t use all of them in one sitting — pick two or three that fit where the person is right now. Rotate them so your 1:1s don’t calcify into a script. And listen more than you ask: the best follow-up is almost always “tell me more about that.”

Opening the conversation

The first few minutes set the temperature. These break you out of the autopilot “fine” and signal that this is their time, not a status report.

• How are you, really — not just how’s the work?
• What’s been on your mind this week that we haven’t talked about?
• On a scale of one to ten, how was your week? What would have made it a point higher?
• What’s something you’re looking forward to, at work or outside it?
• If we only had ten minutes today, what would you want to spend them on?
• What’s one thing I could take off your plate this week?

Workload, focus and priorities

Burnout and disengagement often show up first as a workload problem the person hasn’t named out loud. These surface it before it becomes a crisis.

• Does your current workload feel sustainable, or are you running hot?
• How clear are you on what’s most important right now?
• What are you working on that doesn’t feel like the best use of your time?
• Where are you spending time that isn’t moving the needle?
• Is anything you’re responsible for at risk of slipping?
• How often are you getting interrupted or pulled off your main work?
• If you could drop one thing from your plate, what would it be?
• What would “a great week” look like for you next week?

Blockers and support

Engineers frequently under-report blockers — they’d rather grind through than look stuck. Ask directly, and make it safe to say “I need help.”

• What’s slowing you down right now that I could help with?
• Is there a decision you’re waiting on? From whom?
• What’s the most frustrating part of your work this week?
• Where are you stuck that you haven’t asked for help with yet?
• Is there anything about our process or tools that’s getting in your way?
• Who do you need more (or less) of to do your best work?
• What do you need from me that you’re not getting?

Growth and career

These rarely come up unprompted, and they’re the ones people remember you for. Don’t save them for review season — a casual growth question every few weeks keeps the conversation alive and catches a flight risk early.

• What do you want to be doing more of, six months from now?
• Which skills do you most want to build right now?
• What’s a project that would stretch you in a good way?
• When did you last feel like you were learning something here?
• What does the next step in your career look like to you?
• Is there a part of the codebase or the business you wish you understood better?
• Who in the industry, or on the team, do you want to learn from?
• If you could redesign your role, what would you add or remove?

Feedback for them

The 1:1 is the right venue for specific, timely feedback — both the reinforcing kind and the redirecting kind. Lead with what you’ve actually observed, then open the door.

• Here’s something I saw you do well this week — did you realise the impact it had?
• Can I share an observation about something I’d do differently?
• How do you think the [project / incident / launch] went?
• What’s a piece of feedback you’ve gotten recently that stuck with you?
• Where do you feel least sure of yourself right now?
• Is there feedback you’ve been wanting from me that I haven’t given?

Feedback for you

Asking your reports how you’re doing is one of the highest-trust moves a manager can make — and one of the most neglected. Expect silence the first few times; keep asking, and act on what you hear.

• What could I do to make your work easier or better?
• Is there anything I’m doing that’s unhelpful or in your way?
• Do you feel like I have your back? When have you felt that, or not?
• Am I giving you the right amount of context and direction — or too much, or too little?
• What’s one thing you wish I did differently as a manager?
• How could our 1:1s be more useful to you?

Team, culture and collaboration

Your reports see things you don’t. These questions turn each 1:1 into a quiet sensor for how the whole team is really doing.

• How’s the team feeling from where you sit?
• Is there anyone you think is struggling or stretched too thin?
• Who on the team has helped you recently? Have they heard that?
• Is there any tension or friction I should know about?
• What’s one thing that would make this a better team to be on?
• Do you feel like your voice gets heard in our meetings?

Motivation and the bigger picture

Every so often, zoom out. These questions reconnect day-to-day work to the reasons someone shows up — and flag when that connection is fraying.

• What’s the most energising thing you’ve worked on lately? The most draining?
• Do you feel like your work matters to the company’s goals? Can you see the line?
• When did you last feel genuinely proud of something here?
• What would make you seriously consider leaving — so we can fix it before it’s a question?
• A year from now, what do you hope will have changed about your work?

Reading the answer, not just asking the question

A question is only as good as your attention to the answer. The most common new-manager mistake isn’t asking the wrong things — it’s asking a good question and then half-listening, waiting for your turn to talk, or jumping straight to a fix. Every question above will fall flat if you treat it as a box to tick.

A few habits make the difference:

• Ask one, then stop. Resist stacking three questions together or rescuing the silence. Give the person room to think — the most honest answers often arrive after a pause that feels slightly too long.
• Listen for the deflection. “Fine,” “busy” and “same as usual” are rarely the whole story — they’re a polite door, not a locked one. Follow with “fine like good, or fine like surviving?” and watch what happens.
• Follow the energy. When someone’s voice picks up or suddenly flattens, that’s the thread to pull. The topic they get animated or guarded about matters more than the one on your list.
• Don’t rush to solve. Often people want to be heard, not fixed. “Do you want my take, or do you just want to think out loud?” is one of the most useful sentences a manager can learn.

How to actually use these

A list of 50 questions is worthless if it sits in a doc you never open mid-conversation. Three habits make them stick:

• Prep one or two in advance. Glance at what’s changed for this person since you last met — a tough launch, a missed deadline, a win — and pick the questions that fit.
• Carry the thread forward. The best follow-up question is one you asked last time: “last week you mentioned the on-call rotation was wearing you down — where’s that now?”
• Capture and act. A question that surfaces a problem you never follow up on teaches people to stop answering honestly.

That third habit is where most managers leak trust — not because they don’t care, but because the context scatters across notebooks, Slack and memory. This is exactly the gap CoManager’s 1:1 hub is built to close: it tracks your cadence, pre-loads every agenda with open threads and last time’s follow-ups, and turns anything you commit to into a tracked action. And when you’re not sure what to raise, it suggests the next topic based on what’s actually happening with that person — so you walk in with the right question already in hand.