Back to Library

Engineering Manager Performance Review

Engineering & ProductWordengineering managerperformance reviewfeedbackmanagementleadership

Prompt

Write a comprehensive performance review for [ENGINEER NAME], a [TITLE] on the [TEAM NAME] team at [COMPANY NAME].

Review period: [DATE RANGE]
Reviewer: [YOUR NAME AND TITLE]

Input for the review:
- Key projects and contributions: [LIST MAJOR WORK]
- Technical strengths demonstrated: [LIST]
- Areas for growth: [LIST]
- Peer feedback themes: [SUMMARY OF 360 FEEDBACK]
- Impact on team and organization: [DESCRIBE]
- Goals from last review: [LIST AND STATUS]
- Performance level recommendation: [EXCEEDS / MEETS / DEVELOPING / BELOW EXPECTATIONS]

Write the performance review:

1. **Overall Assessment** — 2-3 sentence summary of the engineer's performance this period.

2. **Technical Impact** — Specific contributions with business context. Quantify where possible.

3. **Collaboration and Communication** — How they work with the team, cross-functionally, and with stakeholders.

4. **Growth and Learning** — How they've developed their skills and grown in scope.

5. **Leadership** (if applicable) — Mentorship, influence beyond their role, driving team outcomes.

6. **Areas for Development** — Honest, specific, and framed constructively. Not a list of failures — a growth agenda.

7. **Goals for Next Period** — 3-5 goals: 2 for technical growth, 1 for collaboration, and 1 stretch goal.

8. **Closing** — What makes this person valuable and your commitment to their growth.

Tone: honest, specific, encouraging. Avoid corporate vagueness.

More from Engineering & Product

Engineering & Product

Product Requirements Document (PRD) Generator

Write a comprehensive Product Requirements Document (PRD) for [FEATURE OR PRODUCT NAME] at [COMPANY NAME]. Context: - Problem being solved: [DESCRIPTION] - Tar...
Copilot Chat
Engineering & Product

Sprint Planning Facilitator

Facilitate sprint planning for [TEAM NAME] at [COMPANY NAME] for Sprint [NUMBER]. Sprint context: - Sprint length: [1 / 2 / 3 WEEKS] - Team velocity (average s...
Copilot Chat
Engineering & Product

Technical Architecture Decision Record

Write an Architecture Decision Record (ADR) for the following technical decision at [COMPANY NAME]. Decision context: - Decision title: [SHORT DESCRIPTIVE TITL...
Copilot Chat
Back to Library