Ranks 6–20 (every number is a percentile across eligible engineers; raw score in brackets)
#
Engineer
Composite
Shipped
Fixed
Multiplied
Risk held
PRs
Reviews
How it's scored
Impact here means work whose effect on users or on other engineers is visible in the repo. Lines of code, commits and PR counts are never inputs. Every PR earns credit only by clearing a quality bar in one of four lenses, and each lens sums an engineer's 15 strongest credits, so a hundred small PRs cannot outrank ten important ones. Each lens becomes a percentile rank across eligible engineers (zero stays zero); the composite is the weighted sum you control with the sliders.
Shipped to users
Feature or perf PR shipped with no flag: 1.0, plus +0.5 if it closed a request someone else filed (up to +0.5 more for reactions and comments on that request).
Built behind a feature flag: 0.5. It lifts to 1.0 when a later PR in the same area, touching the same files, made the feature available to everyone.
That gate-removal PR itself earns 0.25 (0.10 if it is flag cleanup). PostHog flips flags in its flag UI, so the repo only sees gate removals.
The template's Release status marker appeared late in the window; older PRs are classified from their own wording ("behind a flag", "remove the flag") and the evidence says so.
Fixed what hurt
Fix that closes an issue filed by someone else: 1.0 (0.5 if self-filed), +0.5 if the filer is not a PostHog contributor (not a public org member and merged no PRs in the window), up to +0.5 for reactions and comments on the issue (people waiting).
Fix with no linked issue: 0.25; severity unknown, no AI guessing.
Reverting a change, or hot-fixing someone else's change within 72 h: +0.5 to 0.75 for firefighting.
Multiplied others
A review counts when a human who is not the author requested changes or left inline comments. 1.0, +0.5 if the author pushed commits after it. Empty approvals count zero; bots never count.
Breadth matters: credits are grouped by the author reviewed and summed with diminishing returns, so 60 reviews of one teammate are worth far less than reviews across 60 people.
Reviews of agent-authored PRs are tagged as oversight. PRs whose files are mostly shared tooling (CI, dev env, agent skills) add 1.0 each, at most five.
Carried risk, and it held
Radius of a PR = the most shared non-hub file it changed: engineers who changed that file in the window × a category multiplier (migrations 2×, HogQL/schema, ingestion, auth/billing 1.5×, CI 1.3×, tests/docs 0.3×) + a base so a solo migration counts like a file ten people work in.
Held: ×0 if the PR was reverted, ×0.5 if someone else hot-fixed its files within 72 h with a reference, a regression note, or a fresh issue in the same area.
Hub files touched by more than 20 PRs (lockfiles, generated schema) never count for radius or overlap.
Who gets credit
PostHog's template names the human DRI as assignee when an agent did the work under direction, so credit goes to the assignee, else the author. PRs marked Fully autonomous credit nobody unless you flip the toggle. Bot accounts never earn credit. Each card shows the share of an engineer's PRs that were agent-assisted, as context rather than penalty.
Eligibility
An engineer needs at least 8 credited PRs spanning 3 weeks, or 10 substantive reviews.