Question sets for career growth and motivation

Below are curated questions organized by goal and by seniority. Use them as scripts you can adapt to each person. After a question, note the signals you want to hear and two concrete follow up actions you could take before the next meeting.

How to use these questions effectively

Schedule one on ones at a cadence that fits the engineer and the work. Prepare by reviewing previous notes and any open commitments. Ask one question at a time and give space for reflection. When an answer suggests action, write a single next step and a date to revisit it. Keep a running log so progress is visible to both of you.

Warm up questions to build trust

• How are you feeling about your work this week What went well and what felt hard
• What should I know that I might not already know Anything small or big
• Is there anything you want me to stop doing or start doing as your manager One change is enough

Signals to listen for Include tone changes, repeated themes, or deferred topics. Follow up actions could be a quick calendar change, a promise to remove a blocker, or scheduling a focused session.

Questions for junior engineers

Focus on learning, clarity, and safety. Keep questions specific and concrete.

• What did you learn since our last meeting What helped you learn it
• Which task felt unclear and how could it be explained better
• Where do you want more feedback On design, tests, or speed
• What part of the codebase would you like to own next One small area is fine

What to listen for Evidence of confidence growth, persistent confusion about a system, or avoidance of ownership. Manager actions Offer a short learning project, assign a buddy for reviews, and set a clear acceptance criterion for the next task.

Questions for midlevel engineers

Shift toward autonomy, systems thinking, and impact.

• Which technical decision are you most proud of this month and why
• What recurring friction do you see in our delivery process How would you try to fix it
• Which skills do you want to grow in the next six months Where do you need exposure
• Who on the team could use mentorship from you What would that look like

What to listen for Willingness to propose improvements, clarity about skill gaps, and readiness to mentor. Manager actions Create time for a small improvement project, connect them with a cross team initiative, and agree on measurable skill targets.

Questions for senior and staff level engineers

Emphasize influence, strategy, and multiplying impact.

• What hard tradeoff should we be talking about but are avoiding
• Where can we reduce operational cost without increasing risk
• Which people or teams would benefit most from your attention How should you spend that time
• What do you want your legacy on this codebase or product to be

What to listen for Appetite for system level work versus feature work, and realistic scope for influence. Manager actions Align priorities with product goals, clear authority to make low risk changes, and sponsorship for larger efforts.

Questions focused on career path and promotion readiness

These questions help translate daily work into career outcomes.

• Which recent outcomes best reflect the level you are aiming for How did you measure impact
• What evidence would convince you and me that you are ready for the next role Pick two metrics or examples
• Which stakeholders should be aware of your work and how can we make that visible

What to listen for Concrete examples tied to impact and scope rather than vague ambition. Manager actions Map answers to the promotion rubric, create visibility opportunities, and set a timeline with milestones.

Questions to diagnose motivation and risk of burnout

Motivation can change quickly. These questions surface energy and stress early.

• Which part of your work energizes you most right now Which part drains you
• How is your workload on a scale where zero is too light and ten is impossible What would move it one point closer to six
• What non work priorities are taking time or emotional energy Anything I can adjust

What to listen for Sudden shifts toward high drain and low energy. Manager actions Reprioritize tasks, protect focus time, approve time off, and find at least one energizing assignment in the next sprint.

Questions that surface blockers and process improvements

Blockers often live between teams and systems. Ask questions that invite problem solving.

• What stopped you from shipping a story this iteration The most important blocker to remove
• Which handoffs are adding the most latency How would you shorten them
• If you could change one process in the team what would it be Why

What to listen for Recurring handoff problems and unclear ownership. Manager actions Own or escalate the blocker, change a role temporarily, or prototype the proposed process change for a single sprint.

Examples of phrasing and follow up

Good phrasing combines curiosity with a small time box. Replace broad questions with focused variants when needed. For example use “In the last two weeks which decision felt hardest and why” rather than “What are your hard decisions”. After the answer, repeat the main point back and ask “What is the one thing I can do before our next meeting” then write that as the agreed next step.

Choosing questions by cadence and context

Use different questions depending on the meeting frequency. If one on ones are weekly favor operational and wellbeing checks. If biweekly add skill growth and blocker questions. If monthly include career path and promotion focused items. Before a promotion cycle center the conversation on evidence and visibility.

Turning answers into reliable progress

A one on one is only useful if it produces follow up. For every substantive answer record a single next step, an owner, and a date to revisit. Use three buckets for follow up work Quick fixes you can do in one day, development tasks that fit a sprint, and escalations that need broader coordination. Review open follow ups at the start of each meeting so momentum is visible.

Common pitfalls and how to avoid them

Do not turn the meeting into a status update. If you need status use a brief written update before the meeting. Avoid giving only high level praise. Pair recognition with specific behaviors to encourage. Do not promise something you cannot deliver. If you cannot meet a request explain constraints and propose alternatives.

Documenting and sharing outcomes

Keep notes that both of you can access. Record decisions, commitments, and agreed metrics. When a conversation surfaces cross team work ask permission to share a brief summary with relevant stakeholders. Visibility reduces duplication and helps promotion committees see broader impact.

Short scripts you can use right away

• Opening “What should I know before we dive in”
• Career check “If you look back at the last six months what achievement would make you proud”
• Motivation check “What part of your work would you keep if you could only do one thing”
• Action close “What is one concrete thing I will do and one thing you will do before our next meeting”

Using short scripts like these reduces friction and makes it easier to convert a conversation into measurable steps.

Next steps for managers

Pick three questions from different categories and use them consistently for four meetings. Track responses and follow up items. After a month evaluate whether those questions helped you see new opportunities or risks and iterate the set. Over time personalize the scripts based on the engineer response patterns and career goals.