What this prompt does
This prompt turns a vague "catch-up" into a structured, outcome-driven meeting. It takes your current level, target level, timeline, and recent context, then produces seven distinct deliverables — agenda, career questions, visibility framing, feedback requests, blocker escalation, a 90-day growth plan, and a follow-up email — all in one pass. That coverage is intentional: most engineers show up to 1-on-1s with one or two things to say and leave with nothing actionable.
What makes it work is the specificity baked into the variables. You are not asking for generic career advice — you are giving the model your team context, your recent work, and your actual challenges. The output then reflects your situation, not a hypothetical mid-level engineer at a fictional company. The visibility talking points section is particularly valuable: it shows you how to reframe completed work in terms of impact at your target level, which is exactly how promotion calibration conversations go.
The follow-up email template is the detail most people overlook. Sending a written summary after a 1-on-1 creates a paper trail that protects both you and your manager, and signals the kind of ownership behavior that distinguishes senior engineers from mid-level ones.
When to use it
- You have a 1-on-1 coming up and you have been coasting through them without raising your promotion timeline explicitly.
- You just shipped something significant and want to make sure your manager understands the scope and difficulty.
- You are hitting a blocker — a dependency on another team, unclear requirements, or scope creep — and need a professional way to escalate without sounding like you are complaining.
- You are approaching a performance review cycle and want to align on expectations before your manager writes their assessment.
- You recently received vague feedback ("keep doing what you are doing") and want to ask sharper questions that get you real signal.
- You are new to the team and want to establish visible momentum early.
Example output
Agenda (30 minutes)
1. Quick wins from the past two weeks — 5 min
2. Progress on the payments service migration — 10 min
3. Career path: what does Senior look like here? — 10 min
4. One blocker: design review SLA from Platform team — 5 min
Career growth question to ask:
"What is the one thing you are not seeing from me yet that would
make my promotion case straightforward?"
Visibility framing:
"The payments migration reduced P95 latency by 40%. I drove the
rollout plan across three teams and handled the on-call rotation
during cutover. That is the cross-team coordination piece I am
trying to build more of."
90-day milestone (Month 1):
Own the architecture decision record for the new event bus.
Present it in the next tech sync.
Pro tips
- Set
[timeline]honestly. If you say six months but your manager knows the next cycle is twelve months away, the plan the model proposes will feel out of sync. Use the actual review cadence at your company. - Do not skip
[challenges]. Engineers routinely omit blockers from 1-on-1s because they do not want to seem negative. The prompt's blocker escalation section helps you reframe a complaint as a request for help — a completely different conversation. - Run the prompt once before the meeting, then copy only the sections relevant to your specific agenda. Dropping a seven-section wall of text in front of your manager defeats the purpose.
- Pair the output with your company's leveling rubric. Paste the rubric criteria for your target level into a second prompt pass and ask the model to align the growth plan milestones directly to those criteria.
- Use the follow-up email template every single time, even for routine 1-on-1s. After three months you have a written record of commitments your manager made — that record is invaluable during review calibration.
