SLOs and Engineering Promotions

SLO impact in promotion criteria.

Idea

Promotions in engineering organizations are usually evaluated against a rubric of qualitative criteria: leadership, technical excellence, scope, mentorship. The criteria are real but hard to measure. Including SLO impact in the rubric provides a quantifiable contribution that is hard to fake and impossible to game on a one-off project. The senior engineer who has been driving SLO improvement over multiple quarters has measurable reliability impact to point at.

What "SLO contribution" looks like in promotion criteria:

• Senior engineers contribute to SLO improvement.: The promotion rubric for senior or staff engineers includes "demonstrated impact on SLO performance for owned services." The candidate can point to specific quarters where the SLO target was tightened, where budget burn was reduced, where reliability gaps were closed.
• Concrete impact.: The contribution is quantifiable: this engineer led the work that took service X from 99.5% availability to 99.9%, eliminated a contributing incident pattern, shipped the canary system that reduced bad-deploy rate. Specific deliverables with measurable outcomes.
• Multi-quarter cadence.: A single quarter of SLO improvement could be luck or a one-off project. Sustained improvement over multiple quarters demonstrates the engineer's actual capability. The promotion rubric should weight the multi-quarter trend, not a single point.
• Cross-team contributions count.: The senior engineer who fixed a dependency that was burning everyone's SLO budget contributed to multiple teams' reliability. The promotion process should recognize this; the rubric explicitly values cross-team reliability impact.
• Documented contribution, not assumed.: The candidate (with their manager) writes up the SLO contributions for the promotion packet. Specific changes shipped, specific data showing the impact, specific stakeholders who can vouch. The artifact is the evidence; vague claims do not count.

The rubric change is small (add SLO contribution as a criterion). The cultural change is large (engineers know that reliability work counts toward promotion, so they invest in it more deliberately).

Avoid

SLO impact is one signal among many. Treating it as the only signal, or as the most important signal, distorts engineering culture in ways that undermine the practice it was meant to support.

• Avoid SLO as the only criterion.: Engineering excellence is multi-dimensional. Architecture, mentorship, technical depth, cross-functional collaboration, hiring impact, and many other dimensions matter. Reducing the rubric to SLO numbers produces engineers who optimize for the metric rather than for the underlying reliability.
• Holistic, not algorithmic.: The promotion decision still requires judgment. The SLO contribution is one input that informs the judgment; it is not a formula that outputs the answer. Engineers should not feel that their promotion is a function of one quarter's metric.
• Avoid penalizing engineers on bad-luck SLOs.: Some teams own services that depend on flaky external dependencies, or operate in regions with unusual reliability constraints, or inherited SLO debt from previous teams. The rubric should account for context, not just absolute numbers. An engineer who held the SLO steady on a difficult service deserves more credit than one who improved an easy one.
• One signal among many.: SLO contribution sits alongside scope, leadership, technical impact, and the other rubric dimensions. The candidate's case is built on the combination, not on any one piece. Promotion committees should explicitly weight the rubric to avoid SLO dominance.
• Avoid the metric becoming the goal.: Engineers who learn that "SLO impact" is on the rubric will optimize for visible SLO impact rather than for reliability. They will work on services where the SLO is easy to move; they will avoid services that need fundamental reliability work but won't show movement quickly. The rubric must value the harder, longer work too.

The discipline is to use SLO as an input, not as the answer. The rubric stays multi-dimensional; the SLO becomes one of the dimensions.

Benefit

The cultural payoff of including SLO impact in promotion criteria is substantial when done well. It aligns individual engineering ambition with the team's reliability commitments, and it surfaces the reliability work that previously felt invisible compared to feature shipping.

• Aligns engineering pride with reliability.: Engineers who care about their careers now have a direct incentive to invest in reliability work. The team that previously had to argue for reliability sprints starts having engineers volunteer for them, because the work counts toward the promotion they want.
• Reliability work becomes visible.: Before SLO impact is on the rubric, the engineer who shipped the canary system that prevented three production incidents had no way to tell that story. After, the impact is concrete: "this work prevented X incidents, saved Y minutes of customer-facing downtime, contributed to the SLO improvement that justified our 99.9% commitment." The story is tellable; the work is recognized.
• Cultural shift over multiple cycles.: The first promotion cycle that includes SLO contribution starts to shift behavior. By the second or third cycle, the cultural understanding is "reliability work matters here." New hires absorb the norm faster because it is documented in the rubric.
• Stops the velocity-vs-reliability war.: Engineering organizations often have a tension between teams that ship features and teams that maintain reliability. Including reliability in the promotion rubric removes the implicit message that feature work is what gets you promoted. Both kinds of work count; both are paths to senior.
• Compounds with the SLO practice.: Healthier SLO performance produces engineers who can point to better impact at promotion time, which produces more engineers wanting to do the work, which produces healthier SLO performance. The feedback loop is positive once it starts.

SLO impact in promotion criteria is one of those small cultural changes that produces large long-term effects. Nova AI Ops surfaces SLO contribution per engineer (commits, retros, incident-prevention contributions) so the promotion conversation is anchored in evidence rather than in subjective recollection.