DEV Community

ClawGear
ClawGear

Posted on

35 ChatGPT Prompts for Software Engineering Managers: Lead Better, Ship Faster

#engineering #chatgpt #productivity #ai

Software engineering managers operate at the intersection of people, process, and technical strategy — a combination that demands constant communication, clear thinking, and thoughtful documentation. AI can help you draft faster, think more rigorously, and spend less time on the administrative weight of management so you can focus on the work that actually makes your team better. These 35 prompts cover the full scope of the engineering manager role.

1. 1:1s & Performance Management

Prompt 1 — 1:1 Agenda Generator

Generate a 1:1 meeting agenda for a weekly check-in with a mid-level software engineer who has been with the team for 8 months. Include questions that surface blockers, career growth alignment, project confidence, and team dynamics without feeling like an interrogation. Add one question I can rotate each week to keep the conversation fresh.
Enter fullscreen mode Exit fullscreen mode

Prompt 2 — Performance Review Draft

Draft a mid-year performance review for a software engineer based on the following notes: [paste raw notes]. The review should cover: overall performance summary, key contributions with specific examples, areas of strength, one to two development areas with actionable suggestions, and a calibration recommendation (meeting/exceeding/below expectations). Use professional, growth-oriented language.
Enter fullscreen mode Exit fullscreen mode

Prompt 3 — PIP Documentation

Write a 30-day performance improvement plan for a software engineer who has missed three sprint commitments in a row, has not proactively communicated blockers, and has received informal feedback twice without visible improvement. Include: the specific performance gap, measurable expectations for the 30-day period, weekly check-in structure, and the consequence if the plan is not met. Tone: clear and professional, not punitive.
Enter fullscreen mode Exit fullscreen mode

Prompt 4 — Promotion Case Write-Up

Help me write a promotion case for a software engineer being considered for promotion from L4 to L5. Based on the following examples of their work: [paste examples]. Structure the case around: technical impact, scope of influence, ownership and initiative, cross-functional collaboration, and leadership behaviors. Use concrete evidence to support each dimension.
Enter fullscreen mode Exit fullscreen mode

Prompt 5 — Difficult Feedback Script

Write a script for delivering difficult feedback to a senior engineer who consistently talks over teammates in meetings and has been described as dismissive of junior team members' ideas. I want to be direct but not damaging to the relationship. Include an opening that does not put them on the defensive, specific behavioral examples (placeholder), the impact on the team, and a clear ask for change.
Enter fullscreen mode Exit fullscreen mode

2. Team Communication & Documentation

Prompt 6 — Sprint Retrospective Facilitation

Create a 60-minute sprint retrospective facilitation guide for a team of 7 engineers that has just completed a challenging sprint with a missed release deadline. Use a "4Ls" format (Liked, Learned, Lacked, Longed for). Include: the warm-up activity, timing for each section, specific prompt questions for each quadrant, how to prioritize action items, and how to close with positive momentum.
Enter fullscreen mode Exit fullscreen mode

Prompt 7 — Post-Incident Review Template

Create a blameless post-incident review (PIR) template for a production outage that lasted 3 hours and impacted 15% of users. Include sections for: incident summary, timeline of events, root cause analysis (using the 5 Whys), contributing factors, what went well in the response, action items with owners and deadlines, and a section on how to prevent this class of issue. Emphasize blameless language throughout.
Enter fullscreen mode Exit fullscreen mode

Prompt 8 — Engineering RFC Template

Create a Request for Comments (RFC) document template for proposing a significant technical change to a software system. Include sections for: problem statement, proposed solution, alternatives considered, technical design overview, implementation plan and phases, risks and mitigations, success metrics, open questions, and a reviewer sign-off table. Format for Confluence or Notion.
Enter fullscreen mode Exit fullscreen mode

Prompt 9 — Team Newsletter

Write a monthly engineering team newsletter for a 20-person team. Sections to include: sprint highlights and shipped features, kudos for specific team members (placeholder names), an interesting technical concept or tool the team learned about, upcoming milestones, and one question for the team to think about this month. Keep it engaging and under 500 words.
Enter fullscreen mode Exit fullscreen mode

Prompt 10 — Stakeholder Status Update

Write a weekly project status update email for non-technical stakeholders on a 6-month platform migration project. The project is 60% complete and two weeks behind schedule due to unexpected legacy data complexity. Cover: what has been accomplished, current status with honest assessment, the delay and its cause, the revised plan to recover, and what decisions or support are needed from stakeholders.
Enter fullscreen mode Exit fullscreen mode

3. Hiring & Onboarding

Prompt 11 — Job Description

Write a compelling job description for a senior backend software engineer at a Series B fintech startup. The role focuses on building scalable payment processing infrastructure in Go with PostgreSQL and Kafka. Include: an engaging intro about the mission and team, specific responsibilities, required skills, nice-to-have skills, and a compensation and benefits placeholder. Avoid gendered language and unnecessary jargon.
Enter fullscreen mode Exit fullscreen mode

Prompt 12 — Interview Scorecard

Create a structured interview scorecard for evaluating senior software engineer candidates. Include dimensions: technical depth, system design thinking, problem-solving approach, communication clarity, ownership mindset, and collaboration. For each dimension, write a 1-5 scale with behavioral anchors at levels 1, 3, and 5. Add a section for overall hire / no-hire recommendation with justification.
Enter fullscreen mode Exit fullscreen mode

Prompt 13 — Technical Interview Debrief Guide

Create a 45-minute debrief meeting guide for an engineering hiring panel after a final-round interview. Include: a structured format that prevents the first speaker from anchoring the group, how to surface evidence-based assessments versus gut feelings, how to resolve split decisions, and a final calibration question the panel should answer before leaving the room.
Enter fullscreen mode Exit fullscreen mode

Prompt 14 — 30-60-90 Day Onboarding Plan

Create a 30-60-90 day onboarding plan for a new senior software engineer joining a team working on a microservices-based e-commerce platform. For each phase, define: the primary goal, key learning activities, first concrete deliverables, people to meet, and how success will be assessed at the end of the phase. Include a note on the manager's role at each stage.
Enter fullscreen mode Exit fullscreen mode

Prompt 15 — Offer Negotiation Response

Write a response to a candidate who has pushed back on the initial compensation offer, asking for $20K more in base salary than our approved range. We cannot increase the base but can offer an additional 5,000 options and an accelerated first-year review. Write a response that acknowledges their ask respectfully, explains the constraints honestly, and positions the counteroffer compellingly without over-promising.
Enter fullscreen mode Exit fullscreen mode

4. Technical Strategy & Planning

Prompt 16 — Technical Debt Prioritization Framework

Help me create a technical debt prioritization framework for my engineering team. We have a backlog of approximately 40 known technical debt items. Create a scoring model with criteria: business impact of the debt (if left unaddressed), estimated effort to remediate, risk level, and frequency with which the debt slows down feature development. Include a scoring rubric and a suggested portfolio allocation (e.g., 20% of sprint capacity).
Enter fullscreen mode Exit fullscreen mode

Prompt 17 — Engineering OKR Drafts

Draft a set of engineering team OKRs for next quarter. Our company objective is to increase platform reliability and reduce customer-reported incidents. Write three engineering Key Results that are measurable, ambitious but achievable, and clearly owned by the engineering team. For each KR, suggest the metric, the current baseline, and the target.
Enter fullscreen mode Exit fullscreen mode

Prompt 18 — Build vs. Buy Analysis

Create a build vs. buy analysis framework for evaluating whether to build an internal data pipeline orchestration tool or purchase an existing solution. Include the key factors to evaluate: core vs. non-core capability, total cost of ownership (build vs. license), maintenance burden, time to value, vendor risk, and team capability fit. Add a scoring worksheet and a recommendation decision tree.
Enter fullscreen mode Exit fullscreen mode

Prompt 19 — Capacity Planning Model

Help me build a quarterly engineering capacity planning model for a team of 12 engineers. Account for: planned feature work, on-call rotation overhead, bug triage, technical debt investment, hiring interviews, and planned time off. Create a spreadsheet structure that shows available engineering weeks by person and a summary of how capacity is allocated across work types.
Enter fullscreen mode Exit fullscreen mode

Prompt 20 — Architecture Decision Record

Write an Architecture Decision Record (ADR) for the decision to migrate our monolithic application to a microservices architecture over 18 months. Include: the context and problem, the decision drivers, the options considered, the decision and rationale, the consequences (positive and negative), and the date and decision makers. Use the MADR format.
Enter fullscreen mode Exit fullscreen mode

5. Team Culture & Processes

Prompt 21 — Team Working Agreement

Help me facilitate the creation of a team working agreement for a newly formed engineering team of 8 people (4 senior, 3 mid-level, 1 junior). Generate a starter template covering: communication norms (response times, async vs. sync), meeting practices, code review expectations, on-call responsibilities, definition of done, and how the team will handle disagreements. Format as a living document the team can edit.
Enter fullscreen mode Exit fullscreen mode

Prompt 22 — Runbook Template

Create a runbook template for a critical microservice in a production environment. Include sections for: service overview and dependencies, key contacts and escalation path, common alert types and their investigation steps, known issues and workarounds, rollback procedure, deployment checklist, and post-incident documentation requirements. Format for a team wiki.
Enter fullscreen mode Exit fullscreen mode

Prompt 23 — Engineering Principles Document

Help me draft a set of 6-8 engineering principles for my team that will guide technical decision-making and code quality expectations. Principles should cover: simplicity, ownership, reliability, testing philosophy, documentation, and cross-team collaboration. For each principle, write a title, a one-sentence summary, and a two-sentence rationale explaining why this principle matters for our team.
Enter fullscreen mode Exit fullscreen mode

Prompt 24 — Incident On-Call Rotation Policy

Write an on-call rotation policy for a backend engineering team of 10 that operates a 24/7 production service. Cover: rotation schedule (weekly primary + secondary), escalation matrix, response time SLAs by severity level, tools required (PagerDuty, etc.), compensation or time-off policy for weekend pages, the on-call handoff process, and how the team will learn from on-call incidents.
Enter fullscreen mode Exit fullscreen mode

Prompt 25 — Blameless Culture Workshop

Design a 90-minute workshop to introduce blameless post-incident review culture to an engineering team that currently avoids discussing failures openly. Include: an opening exercise to surface current attitudes about blame, a presentation on the psychology of blame and how it hurts learning, a case study exercise using a fictional incident, and three specific behavioral commitments the team will make before leaving the room.
Enter fullscreen mode Exit fullscreen mode

6. Cross-Functional Collaboration

Prompt 26 — Engineering Estimate Communication

Write a message to a product manager who has just asked why engineering estimates are "always wrong" and wants engineers to commit to hard deadlines. Explain the difference between estimates and commitments, how uncertainty is inherent in software development, what engineers can commit to, and propose a collaborative planning process that gives the PM the predictability they need while being honest about what engineering can control.
Enter fullscreen mode Exit fullscreen mode

Prompt 27 — Saying No to a Scope Request

Write a response to a VP of Product who has just asked the engineering team to add a significant feature to the current sprint that would require deprioritizing a committed security fix. The response should: acknowledge the business need, explain the trade-off clearly in business terms (not technical jargon), propose alternatives, and make a clear recommendation — without being dismissive or political.
Enter fullscreen mode Exit fullscreen mode

Prompt 28 — Engineering Roadmap Presentation

Create an outline for a 20-minute engineering roadmap presentation to a mixed audience of product, sales, and executive stakeholders. Structure: (1) what we shipped last quarter and why it mattered (5 min), (2) current state of the system and capacity (3 min), (3) Q3 priorities and rationale (8 min), (4) risks and dependencies (4 min). For each section, suggest the key message and one visual that would make it land.
Enter fullscreen mode Exit fullscreen mode

Prompt 29 — Post-Launch Retrospective for Cross-Functional Teams

Design a 60-minute post-launch retrospective facilitation plan for a cross-functional team (engineering, product, design, QA) after a major product launch that was technically successful but had a chaotic final week before release. The goal is to surface systemic process improvements, not assign blame. Include the pre-work to send participants, the facilitation structure, and how to produce action items with owners.
Enter fullscreen mode Exit fullscreen mode

Prompt 30 — Executive Escalation Summary

Write a one-page executive summary escalating a critical infrastructure risk to the CTO. The risk: our primary database has no automated failover, runs on hardware nearing end of life, and a failure would cause an estimated 4-8 hours of downtime. Include: the risk description, business impact (revenue per hour of downtime, SLA implications), the proposed remediation, estimated cost and timeline, and the decision needed from the CTO.
Enter fullscreen mode Exit fullscreen mode

7. Manager Growth & Leadership Development

Prompt 31 — Manager Self-Assessment

Create a quarterly self-assessment framework for a software engineering manager to evaluate their own performance. Include reflection prompts across: team health and psychological safety, individual engineer growth, delivery execution, technical strategy contribution, stakeholder relationships, and personal leadership development. Add a section for identifying the one thing that, if improved, would have the biggest positive impact.
Enter fullscreen mode Exit fullscreen mode

Prompt 32 — Skip-Level Meeting Guide

Create a guide for conducting effective skip-level 1:1 meetings with engineers who do not directly report to me. Include: the purpose of skip-levels and how to set expectations, five to eight open-ended questions that surface honest feedback about team health, process, and my management reports, what to do with sensitive information that surfaces, and how to close the loop with the engineer after the meeting.
Enter fullscreen mode Exit fullscreen mode

Prompt 33 — Managing Up Strategy

Help me develop a strategy for managing up to a new VP of Engineering who has a different management philosophy than I do. Specifically, they favor high process and documentation; I lead a team that values autonomy and minimal overhead. Write a plan for: building trust with the new VP, understanding their priorities without compromising team culture, finding genuine common ground, and influencing upward thoughtfully.
Enter fullscreen mode Exit fullscreen mode

Prompt 34 — Delegation Framework

Create a delegation framework for a first-time engineering manager who struggles to delegate because they are a former senior engineer and find it faster to do things themselves. Include: a decision matrix for what to delegate vs. retain, a four-level delegation ladder (from "I decide" to "you decide and inform me"), common delegation failure modes and how to avoid them, and a conversation template for delegating a significant responsibility to a senior engineer.
Enter fullscreen mode Exit fullscreen mode

Prompt 35 — Leadership Development Plan

Create a 6-month leadership development plan for a software engineering manager who wants to grow toward a Director-level role. Based on the following gaps I have identified in myself: [paste gaps]. For each gap, suggest: one book or resource, one on-the-job experience to seek, one skill to practice in the next sprint cycle, and a way to measure progress. Format as a structured plan with monthly milestones.
Enter fullscreen mode Exit fullscreen mode

Get the Complete Software Engineering Manager AI Toolkit

Get the complete AI Prompt Toolkit for Software Engineering Managers →

Works with Claude, ChatGPT, and DeepSeek. Copy-paste ready.

Top comments (0)