InnerSourcing HR: Rewarding the Engineers Who Quietly Hold the Company Together
The engineers who review other teams' PRs, answer #help-eng questions, and keep the internal docs alive are invisible in standard performance reviews. InnerSourcing HR uses Git metadata to find and reward them.
- Open-source ecosystems run on 'glue' contributors: reviewers, maintainers, doc writers, mentors.
- Inside companies, the same dynamic exists — but standard performance reviews ignore it.
- InnerSourcing HR pulls Git, Slack, and docs metadata to surface citizenship contributions across team boundaries.
- GitHub's 2023 Octoverse report found the top 5% of internal reviewers reduce time-to-merge by 41% company-wide.
- Reward citizenship explicitly — promotion criteria, comp band, and visible recognition. Glue people are the highest-leverage retention save.
She was up for principal engineer. Her shipped-feature count was middling. Two reviewers nearly downvoted her. Then someone pulled the Git stats: she had reviewed 38% of the org's cross-team PRs that year, mentored 6 juniors to senior, and authored the internal docs that onboarded every new hire. The Git metadata told a story the OKRs did not.
What InnerSourcing means
Coined at Tim O'Reilly's open-source company in 2000 and popularised by PayPal and SAP, InnerSource is the practice of running internal projects with the open-source ethos — public-by-default, anyone can contribute, reviews are open, mentorship is the norm. InnerSourcing HR is the people layer: measure and reward this ethos in performance reviews.
What to measure
| Citizenship signal | Source | What it indicates |
|---|---|---|
| Cross-team PR reviews completed | GitHub/GitLab API | Generosity, breadth of expertise |
| Answers in #help-engineering channels | Slack analytics | Mentorship and on-demand teaching |
| Internal RFC/design doc comments | Notion/Confluence/Google Docs | Architectural thinking beyond own scope |
| Pair-programming hours logged | Calendar + voluntary log | Skill transfer |
| Onboarding mentor assignments completed | HRIS | Long-term investment in others' ramp |
| Internal library/SDK contributions | Git | Platform leverage |
How to reward without gaming
The moment 'cross-team PR reviews' becomes a promotion target, you will get rubber-stamp reviews. Pair every citizenship metric with a quality signal — e.g. reviews that produced changes, answers marked helpful, design docs that shipped.
- Add an explicit 'Citizenship' rubric to performance reviews — equal weight to 'Impact'. Promotion to staff/principal requires citizenship contributions.
- Quarterly 'Glue Awards' — public, named, with real comp attached ($2–5K). Cheap retention insurance for irreplaceable people.
- Publish an internal leaderboard of citizenship contributions — but show the long-tail, not the top-3, so it celebrates participation.
- Build comp bands that explicitly reward maintainers — many companies pay maintainers less than 'feature shippers' even though they keep the lights on.
- Track 'bus factor' per system — if any system has bus factor 1, that maintainer's citizenship work is critical-path. Pay accordingly.
Takeaways
- Glue work is real work. Measure it.
- Standard sprint metrics make glue people invisible. Git metadata makes them visible again.
- Reward citizenship in comp and promotion, or you will lose the people who keep the lights on.
- Tanya Reilly — Being Glue — LeadDev, 2019
- GitHub Octoverse 2023 — GitHub
- InnerSource Commons — Industry consortium
- Stripe Engineering Ladder — Stripe, public
Read next
All playbooksOrg charts tell you who reports to whom. REND tells you who lights up the room — and who turns the lights off. The next layer of Organizational Network Analysis.
Stop talking about 'upskilling'. Start measuring exactly what percentage of each role belongs to the human and what belongs to the AI agent — and design the job around the split.
Melvin Conway proved teams ship their own communication structure as software. The Inverse Conway Maneuver flips this — HR designs reporting lines to mirror the ideal microservice architecture, not the legacy org chart.