12 Engineering 1:1 Questions That Actually Get Real Answers
TL;DR: Most engineers ask their manager the wrong 1:1 questions. "Am I doing okay?" gets you a hedge. "What would you have a hard time defending in calibration about my work?" gets you specifics. Twelve questions, sorted by what you actually want: career signal, project unsticking, manager calibration, and a wildcard for skip-levels. Steal the list.
You don't need 50 questions. You need three good ones per meeting.
Most lists you find online are 50-question dumps with no priority order. They feel comprehensive. They're not. You can't ask 50 questions in a 30-minute meeting, and the lack of curation actually makes them worse, not better.
Twelve questions. Four buckets. Pick three per 1:1 based on what you actually need this week.
Asking "am I doing okay?" for the fourth straight week. (Giphy search: awkward-look-monkey-puppet)
How should I organize my 1:1 questions?
I keep mine in a doc with four sections:
- Career signal — what's my manager seeing about me that I'm not?
- Project unsticking — what's blocking me that they can move?
- Manager calibration — what does their world look like right now?
- Wildcard / skip-level prep — stuff I'd never normally ask.
Before each 1:1, I scan the doc and pick one from career, one from unsticking, one from calibration. Three questions, ten minutes of prep, 30-minute meeting. Done.
The full list is below. Each one is a question I've actually used, with the reason it works and the trap to avoid.
What questions reveal career feedback I'm not getting?
1. "If you were writing my promo packet today, what would you have a hard time defending in calibration?"
The single best question on the list. It works because:
- It assumes you're a candidate (so the answer isn't "well, you're not at the bar"; it's "the bar requires X, you have Y, the gap is Z").
- "Calibration" forces them to think about other people in the room, not just their own opinion.
- "Hard time defending" is concrete and unflattering, which short-circuits the politeness reflex.
Trap to avoid: don't ask this until you have at least 6 months of work to talk about. Asking on day 30 just gets you a vague "still getting to know your work."
2. "What's one piece of feedback you've been sitting on because you weren't sure how I'd take it?"
Permission-giving phrasing. Most managers have one piece of feedback they've been chewing on. This unlocks it.
Don't argue with the answer. Just say "thank you, can you give me an example?" and write it down.
3. "Who on the team is doing work I should be more aware of, and why?"
Surface question: who else is good? Real question: what does my manager value, and how do I stack against it?
You'll learn more about your own promo case from this question than from asking about yourself directly.
What questions actually unstick projects?
4. "What's the one thing about [project] you'd push back on if you had time?"
Managers see the project from a different altitude. They're rarely going to volunteer concerns ("don't want to micromanage"). Asking explicitly invites the senior-eye review.
I've had 30-second answers to this that saved me 3 weeks of work.
5. "If this project slipped by four weeks, what'd be the biggest problem?"
The wrong version of this is "are we on track?" That gets you "yes, looks good."
The right version forces them to articulate the consequences of slippage, which tells you what to defend. You'll find out which milestone actually matters and which ones are flexible.
6. "Who else needs to know what we just decided?"
Ask after any 1:1 that includes a decision, however small. Managers have a 30,000-foot view of the org. They know who's going to be surprised.
This question alone has saved me from more cross-team blowups than any process I've adopted.
What questions tell me what's actually happening in my manager's world?
7. "What are you worried about that you can't really tell us?"
Bold question. You can't ask it on week one. After ~6 months of trust, it's the unlock that turns a transactional 1:1 into a real working relationship.
Managers operate with information they can't share (re-orgs, performance issues, hiring freezes). They're also lonely about it. This question doesn't ask them to break confidence; it asks for the shape of the worry. They'll often share enough that you can adjust your work accordingly without ever knowing the specifics.
8. "What's the one thing your skip-level is pushing you on right now?"
Tells you what flows downhill. If your manager is being pushed on cost, your roadmap will have a cost-cutting flavor. If they're being pushed on velocity, expect a hiring push. Aligning to this isn't politicking; it's basic situational awareness.
9. "How can I make your job easier this month?"
The most underrated question in the manager-employee relationship. Most engineers spend years extracting from their manager (feedback, project allocation, promotion). The flip is rare and remembered.
Caveat: don't ask if you don't mean it. The answer is usually small and concrete ("write the post-mortem for last week's incident, send me a summary by Friday"). Do the thing.
Brain expanding: asking about my work → asking about their work → asking what's flowing downhill. (Giphy search: galaxy-brain-meme)
What questions should I save for skip-levels and special situations?
10. "What's the story you'd tell about me at a leadership offsite?"
Skip-level 1:1 gold. Forces them to articulate your reputation, not just your performance. Reputation is what travels in calibration meetings you're not in.
If they can't tell a story, you have a visibility problem. That's a real signal.
11. "What's a project you'd take on if you had three more months in your role?"
Asked of a senior IC, this is mentorship. Asked of a manager who might move soon, it's a roadmap leak. Either way it tells you what they think matters.
12. "What would have to be true a year from now for you to feel like this team is in a great spot?"
Long-arc question. Hard to ask without sounding fluffy. The trick is to be sincere and silent after.
You're listening for what they don't say. If "we have a clear promotion path" doesn't make their list, you have information about how they think about people work. Not a deal-breaker, but useful to know.
What's the prep ritual that makes 1:1s actually work?
Ten minutes before the meeting. Open the running doc. Three steps:
- Re-read last week's notes. What action items did you commit to? Did you do them? If not, lead with that.
- Pick three questions from the list above. One from career, one from project, one from calibration.
- Write one thing you're going to share. A win, a screw-up, a frustration. Don't make your manager pull it out of you.
After the meeting, three more minutes:
- Date-stamp the entry.
- Write down any feedback you got, verbatim. Verbatim matters; paraphrasing softens.
- Note any action items. Whose? Due when?
Six months of this and you have the spine of your next promotion brief.
Are there questions I should not ask my manager?
A few that backfire:
- "How do I get promoted?" Too vague. Use Question 1 instead.
- "Am I doing well?" Solicits hedged reassurance. Use Questions 1 or 2.
- "Why didn't I get promoted?" Adversarial framing. Use "if you were writing my packet today, what would the hard part be?" instead.
- "What do you think of [colleague]?" Puts your manager in a bad spot and signals to them that you'd be willing to talk about colleagues to other colleagues. Don't.
- "Are we doing layoffs?" Your manager either doesn't know or can't tell you. The question creates anxiety without solving it.
How do I make my manager give better answers?
Three small moves:
Send the questions ahead. Five minutes before the meeting, drop the three questions in Slack. Managers think better with prep time. Hedged answers come from being put on the spot.
Get specific in the follow-up. "Can you give me an example?" / "What does that look like in practice?" / "If I did one thing differently, what would it be?" These three follow-ups turn 80% of vague answers into useful ones.
Write down what they said, in front of them. It's a signal that you're taking it seriously and that you'll be back about it. Managers calibrate their answers based on whether they think you'll act on them.
For the meta-strategy behind all of this, The Engineer's Guide to Getting Promoted (2026) walks through how 1:1 work compounds into a real promotion case over a 12-month arc.
If your 1:1s are broken at a deeper level (skipped, agendaless, status-only), start with Why Your 1-on-1s Feel Like Dentist Appointments. Fix the meeting before you optimize the questions.
For broader engineering management writing, Lara Hogan's site and Will Larson's lethain.com are the two best free archives on the internet.
FAQ
What are the best 1:1 questions for engineers to ask their manager?
The single highest-leverage question is "If you were writing my promo packet today, what would you have a hard time defending in calibration?" It forces specificity and surfaces real gaps. Beyond that, rotate between career-signal questions, project-unsticking questions, and questions about what's happening in your manager's world.
How many questions should I bring to a 1:1?
Three. One career, one project, one calibration. Trying to cover more dilutes the conversation. A 30-minute meeting with three real questions beats a 30-minute meeting with ten shallow ones.
Should I send my 1:1 questions to my manager in advance?
Yes, 5–10 minutes before. Managers give better answers when they've had a moment to think. The "ambush" version of a hard question produces a hedged answer; the prep-shared version produces a useful one.
What's a 1:1 question I should never ask?
"Am I doing well?" It solicits hedged reassurance. Substitute "if you were calibrating me today, what would the hard part be?" Same intent, ten times the signal.
How do I ask for promotion feedback without sounding pushy?
Frame it as collaboration: "I'm putting together a brief on what I'm working toward, can you tell me what would have to be true for you to advocate for the next level?" You're asking for criteria, not for a promotion. Managers respond well to criteria questions.
What questions should I ask in a skip-level 1:1?
Different agenda. Skip-level is about reputation, strategy, and visibility. Try "what's the story you'd tell about me at a leadership offsite?" and "what are you worried about that I should know but probably don't?"
How often should I refresh my list of 1:1 questions?
Quarterly. Same list for 18 months means you've stopped thinking about what you actually need from your manager. After every review cycle, audit the list. Drop the ones that always get the same answer, add new ones based on the season you're in.
This is part of the Engineering Self-Management series. The free 14-day workbook includes a guided 1:1 reset exercise on Day 7.