Engineering manager 1 on 1 questions should cover three loops HR templates skip: technical career path, code review, and cross functional friction. Ask a few each week. Write one action that ties a team goal to a personal milestone. Status belongs on the board, not in this meeting.
This is the engineering spoke of The High-Performance Team Playbook.
What should an engineering manager discuss in a 1-on-1?
A technical 1 on 1 must bypass project tracking and focus on system architecture ownership, burnout vectors, and technical debt.
Developers already have standup, the board, and review comments. If this hour is another status pass, they will mute it. Split the remaining time: one architecture or system question, one career question, then one written action.
| Architecture questions | Career questions |
|---|---|
| Who owns this service if you are out for two weeks? | In 18 months, do you want more system depth, more people leadership, or still unclear? |
| What technical debt is now a burnout vector, not just a cleanup wish? | What work this quarter would count as evidence for that path? |
| Where are you still the only person who can change the design? | If we froze titles for a year, what would still feel like growth? |
| What should we stop shipping until the architecture is named in writing? | What skill would make the next hard project less scary? |
Let them drop technical blockers into the shared agenda before the call. The 1 on 1 starts on judgment, not on discovery.
Why generic 1 on 1 lists fail engineering managers
A product owner or engineering manager sits between delivery, craft, and people. A hobby question does not help any of those.
Standard HR content asks how are you, what are your goals, and do you feel included. Those can matter. They do not tell you if review is blocking the squad, if the person wants staff IC or tech lead, or if product keeps changing the bet mid sprint.
Your 1 on 1 is the only private place to talk about the system without performing in standup. If you spend it on ticket recap, you steal the only hour that can change the system.
According to iSilta's 2026 survey of 146 organizations, 78% cite weak 1 on 1s when manager training is late or thin. Many EMs were strong ICs last year. They copy a template and still miss the technical thread. According to the same survey, 61% train managers only after promotion. This list is the missing technical half.
How to use these questions
Pick two questions, listen, then write one action with an owner and a next date.
Do not fire all 15. Rotate by what is loud this week: a painful review queue, a promo packet, a product reset. Let them go first. Your questions fill gaps, they do not replace their agenda.
Technical career path questions
Career talk on an engineering team means IC depth, tech lead, or manager, plus what evidence would make the next step fair.
| # | Question | What you learn |
|---|---|---|
| 1 | In 18 months, do you want more system depth, more people leadership, or still unclear? | IC vs lead vs wait, without forcing a title |
| 2 | What work this quarter would count as evidence for that path? | A milestone you can put next to a team goal |
| 3 | Where are you still the bottleneck because you are the only one who knows the area? | Staff shaped work vs accidental heroics |
| 4 | What skill would make the next hard project less scary? | Learning that is not a random course |
| 5 | If we froze titles for a year, what would still feel like growth? | Whether they chase scope or only a label |
Close this block by naming one milestone in their words. Example: own the failover runbook so the on call load is not only yours. That is personal career work that also is a technical goal.
Code review loop questions
Review is how the team teaches. If the loop is slow or harsh, people hide work or rubber stamp.
| # | Question | What you learn |
|---|---|---|
| 6 | What is stuck in review right now, and for how long? | Queue pain the board may hide |
| 7 | When you review others, what do you wish you could skip? | Nit culture vs real risk |
| 8 | When others review you, what comment pattern wastes days? | Style wars, missing context, or late design fights |
| 9 | How should we treat agent written diffs this month? | Ownership and quality bar when tools draft code |
| 10 | Who do you want more review from, and who is overloaded? | Load balance without a public callout in Slack |
Turn answers into system changes: SLA, pairing on design before the PR, or a written bar for tests. Do not leave review pain as a vibe.
Cross functional friction questions
Friction with product, design, or other squads shows up as churn, surprise scope, and engineers who stop trusting the plan.
| # | Question | What you learn |
|---|---|---|
| 11 | Where did product or another team change the bet after we started? | Rework that looks like slow engineers |
| 12 | What decision are we waiting on that you cannot unblock alone? | Your job as EM: escalate or cut scope |
| 13 | When do you feel used as a ticket machine instead of a partner? | Respect and craft |
| 14 | What would a good written handoff to product look like this week? | Async clarity that saves a meeting |
| 15 | Who outside the team do you need a real relationship with? | Staff and senior growth through influence |
Product owners in the same 1 on 1 pattern can ask the inverse: where did engineering need a clearer problem, not a longer spec. The point is the joint system, not blame.
A simple weekly shape for an EM 1 on 1
- Their topics first (10 minutes)
- One career or craft question (10 minutes)
- One system question: review or cross team (10 minutes)
- Actions that name a team goal and a personal milestone (5 minutes)
Forty five minutes is plenty if you refuse status theater.
How iSilta bridges technical goals and career milestones
iSilta is the operational dashboard where team goals, 1 on 1 notes, and career actions sit together so you do not run two private lists.
EMs often keep delivery in Jira and career in a forgotten doc. Then promo time is a scramble. The 1 on 1 never connected the failover project to the staff packet.
On iSilta, people drop technical blockers into the agenda asynchronously before the call, so status never has to open the meeting. Action Points can tag a team OKR and a personal outcome. Both of you see the same history. Prep is not hunting Slack for that thing about review SLA. Shared profiles also remind you how this engineer likes feedback before you walk in.
That is the product job: not replacing the 1 on 1, holding the bridge between the roadmap and the person.
What to skip
| Skip | Why |
|---|---|
| Full sprint recap | The board already has it |
| Personality tests as labels | Ask for behavior in review and meetings instead |
| Live debugging the whole hour | Pair later; protect the people conversation |
| Comparing them to a named peer | It kills safety and does not scale |
Implementation steps
- Save this question bank. Mark 5 you will actually use this month.
- Add a standing 1 on 1 section: career milestone this quarter.
- After each meeting, write one Action Point that names a team goal and a personal outcome.
- Once a month, ask a code review question even if the queue looks fine.
- Keep the loop in iSilta so the next 1 on 1 starts on the list, not on memory.
Frequently asked questions
What should an engineering manager discuss in a 1-on-1?
A technical 1 on 1 must bypass project tracking and focus on system architecture ownership, burnout vectors, and technical debt. Follow architecture questions with career questions. Write one action that ties a team goal to a personal milestone.
What should an engineering manager ask in a 1 on 1?
Ask about technical career direction, code review load and quality, and friction with product or other teams. Skip generic icebreakers. Tie answers to a team goal and a personal milestone.
How is an EM 1 on 1 different from an HR 1 on 1 template?
HR templates rarely cover IC vs tech lead paths, review SLA pain, or product priority churn. Engineering managers must talk about the work system, not only feelings.
Should engineering 1 on 1s include status updates?
No as the main course. Status belongs in the board. Use the 1 on 1 for judgment, career, and system pain the board cannot show.
How often should you rotate engineering manager 1 on 1 questions?
Keep a standing career thread. Rotate code review and cross team questions when the system is noisy. Do not ask all 15 every week.
How does iSilta help engineering manager 1 on 1s?
iSilta is the dashboard where team technical goals sit next to personal career milestones and Action Points, so the 1 on 1 is not two separate notebooks.
Related: The High-Performance Team Playbook, High impact engineering 1:1: a framework for elite leadership, EM vs tech lead: the ultimate guide to choosing your leadership path.
Prefer prepared conversations over memory alone? Explore iSilta features or try the product demo.