What this prompt does
This prompt drafts a Senior-to-Staff promotion packet that a committee can approve without follow-up questions. It casts the AI as an engineering manager who has written and defended Staff packets. You provide the [candidate] and current level, the [scope] of ownership, the [flagship_projects], and the [timeframe], and it returns an evidence-first packet: scope-and-impact framing, three flagship projects each with problem-solution-outcome, cross-team leadership examples, technical-judgement calls, mentoring and hiring evidence, and testimonial prompts to send partners.
The packet leads with scope and measurable outcomes rather than activity, which is what actually lands with a promotion committee reading dozens of cases. Framing the [scope] to show the candidate already operates at Staff level reframes the ask from "promote me" to "recognize what is already true," which is a far easier case to approve. Each flagship project follows a problem-solution-outcome arc so impact is legible at a glance, the cross-team leadership section surfaces influence beyond the immediate team, and the packet flags every metric placeholder so you fill in real numbers instead of letting gaps read as weakness.
When to use it
- Building a Senior-to-Staff case for the
[timeframe]promotion cycle - Reframing day-to-day work as Staff-level scope and impact
- Structuring
[flagship_projects]into committee-ready problem-solution-outcome stories - Surfacing cross-team influence that lives outside your immediate team
- Drafting testimonial requests so partners attest to the right things
- Identifying which gaps from the last cycle you have closed
Example output
You get a two-to-three-page Markdown packet, evidence-first, in a fixed order: scope and impact, three flagship projects with measurable outcomes, cross-team leadership, technical-judgement tradeoffs, mentoring and hiring evidence, and testimonial prompts to send partners. Metric placeholders are flagged throughout so you know exactly where to insert real numbers before submitting, and the testimonial prompts spell out what each partner should attest to.
Pro tips
- Describe
[scope]in terms of what you own across teams, not your job title — the packet argues you already operate at Staff scope - Pick
[flagship_projects]with measurable outcomes; a re-platform with a latency or revenue number beats a busy-sounding project with none - Fill every flagged metric placeholder with a real number before you submit — gaps read as weakness to a committee
- Use the testimonial prompts verbatim when asking partners, so each person attests to a specific, distinct strength
- Lead each project with the problem and the outcome; the solution detail matters less than the measurable result
- Set
[timeframe]to the actual cycle so the "gaps closed since last cycle" section is grounded in real dates - Lead the technical-judgement section with hard tradeoff calls and why they were right; committees weigh judgement under ambiguity heavily at the Staff level
- Keep the packet to the two-to-three-page target so a committee can read it in one sitting without losing the thread
