When preparing for a staff engineer promotion and needing to build both the impact and the evidence.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Developer Productivity & Career - Use case: Staff Engineer Impact Framework - Source task: - Help a senior developer build the portfolio and impact needed for a staff engineer promotion. Current level: senior developer at {{company_size}}. Staff engineer expectations: {{describe_or_use_standard_technical_vision_cross_team_influence_m}}. - Step 1: gap analysis between current impact and staff engineer expectations. - Step 2: design high-visibility projects that demonstrate each staff-level competency. - Step 3: build a narrative for the promotion case (impact statements for each competency). - Step 4: advice on navigating the promotion process at {{company_stage}}. # Goal Gap analysis, high-visibility project ideas per competency, impact statement narrative, and promotion process navigation advice. # Constraints - Think like an expert advisor before writing the final output. - Ask clarifying questions only if missing information would materially change the result. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Gap analysis, high-visibility project ideas per competency, impact statement narrative, and promotion process navigation advice.
{{double-curly}} with your real context.When preparing for a staff engineer promotion and needing to build both the impact and the evidence.
Staff engineers are promoted for impact on other engineers' work, not their own output — mentoring, documentation, and architectural influence count more than lines of code.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.