Loading dashboard...

--
Team EPI Average
--
vs prev period
Deploy Freq
--
Lead Time
--
Performance
--
Collaboration
--

Engineers

Engineer EPI Score Deploy Lead Perf. Collab. Dimensions Trend

Select an engineer

Click an engineer from the overview table to see their detailed scorecard.

DORA + SPACE Framework

The Engineering Performance Index combines two industry-leading frameworks into a holistic measure of engineering contribution — not just code output.

The Four Dimensions

1. Deployment Frequency (DORA) — 20%

How often does an engineer ship code? Measures commits per week and PRs merged per week.

  • 0-3 commits/week = score 0–30
  • 3-7 commits/week = score 30–60
  • 7-15 commits/week = score 60–85
  • 15+ commits/week = score 85–100

2. Lead Time (DORA) — 15%

How quickly do PRs move from open to merged? Shorter lead times indicate healthy review practices.

  • 7+ days = score 0–30
  • 3-7 days = score 30–50
  • 1-3 days = score 50–75
  • <1 day = score 75–100

3. Performance (SPACE) — 40%

Measures output quality through Linear ticket completion, bug-fix ratio, estimation accuracy, and code review thoroughness.

  • Issues completed per sprint
  • Bug fix ratio
  • Estimation accuracy
  • Review-to-PR ratio

4. Collaboration (SPACE) — 25%

The most heavily weighted dimension. Engineering is a team sport — reviews, cross-project contributions, and helping others matter deeply.

  • PR reviews given
  • Slack thread participation
  • Cross-repo contributions
  • Linear comments & collaborative work

Philosophy

This index measures holistic engineering contribution, not just code output. An engineer who writes fewer lines but reviews thoroughly, mentors others via Slack, and contributes across projects will score higher than one who only pushes code in isolation.

No single metric tells the full story. The EPI is designed to surface well-rounded engineers and identify areas for growth — not to rank or punish.

API Tokens
Connect to GitHub, Slack, and Linear to pull activity data.
Personal access token with repo + read:user scopes
Bot token with users:read, search:read scopes
Personal API key from Linear settings
Team Members
Add engineers with their platform identifiers.