Performance Feedback & Career Development for Engineers

Performance Feedback and Career Development

For most engineers, their manager's feedback and support shape their growth more than any training program. Yet feedback is often vague ("keep doing great work"), delayed until annual reviews, or skewed by recency and bias. People are surprised by ratings, unsure what "senior" means, and stuck on promotion paths with no clear evidence of what is missing.

Effective performance management is mostly a set of habits: make expectations explicit, give specific, timely feedback, gather evidence continuously, review performance through a calibrated, fair process, address problems early, and invest in development with real opportunities. Done well, there are no surprises at review time, and people know exactly what to work on next.

TL;DR

Make expectations explicit using role and level descriptions, and connect them to the team's goals.
Give frequent, specific, behavior-based feedback — both reinforcing and redirecting — in one-on-ones and close to the moment.
Gather evidence throughout the cycle: shipped work, design docs, reviews, incidents, peer input, and the engineer's own record.
Run reviews with calibration and bias checks; no rating should be a surprise.
Address underperformance early, with clear gaps, support, and timelines.
Build development plans with stretch opportunities and sponsorship; promote on demonstrated scope and impact.

Quick Example

A feedback note written the same day, using situation, behavior, and impact:

A quarterly development check-in agenda:

Core Concepts

Expectations

Expectations come from role and level descriptions (scope, impact, technical skill, collaboration, leadership) and from team goals. Translate them into concrete examples for each person: what a senior engineer on this team does in design reviews, incidents, and mentoring. Revisit them when roles or teams change. See Engineering Levels and Career Paths.

Feedback

Feedback is the main content of one-on-ones, not an annual event. See Mentorship, Sponsorship, and Feedback.

Evidence

Keep notes throughout the cycle and encourage engineers to keep their own brag document — a running list of work, impact, and learning. Sources include shipped projects, design documents, code reviews, incident participation, mentoring, cross-team work, customer impact, and peer feedback collected with specific questions. Evidence counters recency bias and makes reviews and promotion cases concrete.

Reviews and Calibration

Write reviews from evidence against expectations, with specific examples.
Calibrate with other managers to align standards across teams; challenge ratings that lack evidence.
Watch for bias: recency, halo effects, likability, visibility of work (glue work and on-call are easily overlooked), and differences in self-promotion.
Deliver results in conversation, not only in documents, and connect them to next steps.

Underperformance

Address gaps as soon as they appear: describe the gap with examples, understand causes (unclear expectations, skills, workload, personal circumstances, team problems), agree on specific improvements and support, and check progress frequently. Formal improvement plans should follow documented earlier conversations, be achievable, and be run fairly with HR. Many performance problems are fixed by clearer expectations or a better-fitting project.

Development and Promotion

Development plans name one or two growth goals, the opportunities to practice them, and the support available — pairing, training, a mentor, or a sponsor who advocates for stretch work. Promotions should recognize people already operating at the next level with sustained evidence, through a consistent process that is transparent about criteria.

Best Practices

No Surprises

Anything in a review should already have been discussed in one-on-ones.

Keep Running Notes

Record feedback and evidence weekly, for yourself and for each report.

Make Invisible Work Visible

Recognize glue work, mentoring, reliability work, and incident response explicitly.

Tie Growth to Real Opportunities

Pair development goals with projects and responsibilities that let people practice them.

Common Mistakes

Vague Feedback

Annual-Only Feedback

Rewarding Only Visible Heroics

FAQ

How often should managers give feedback?

Continuously — in weekly or biweekly one-on-ones and close to notable events — so formal reviews contain no surprises.

What is the SBI feedback model?

Situation, behavior, impact: describe when and where something happened, the specific observable behavior, and its effect, which keeps feedback concrete and actionable.

How do I handle an underperforming engineer?

Raise the gap early with specific examples, understand the causes, agree on clear improvements and support, follow up frequently, and involve HR if formal steps become necessary.

What is calibration in performance reviews?

A process in which managers compare ratings and evidence across teams to apply standards consistently and reduce individual bias.

How should promotions work?

Promote people who consistently demonstrate the expectations of the next level, based on documented evidence and a transparent process, rather than as a reward for tenure or a single project.