Activity

Stripe’s co-founder, Patrick Collison, has offered insights into the productivity of the company’s software engineers, going beyond simple metrics like lines of code. While the specific “output” per $344k salary isn’t directly quantifiable by him, his statements highlight Stripe’s approach to engineering productivity.
Here’s what he’s revealed:
* Focus on Impact, Not Just Quantity: Collison emphasizes that engineering productivity is “situation dependent” and that a technical solution can take vastly different amounts of time depending on its “legibility” or complexity. He’s been known to use a (joking) analogy of “kilograms of engineers” instead of simply headcount to stress that a bigger team doesn’t always equate to better output. This suggests a focus on the impact and quality of the work, rather than just the volume of code produced.
* High Volume of Code Changes: At Stripe Sessions 2025, Patrick Collison stated that in 2024, Stripe averaged 1,145 pull requests (changes to codebase) per day that were “fully shipped into production.” This high deployment frequency, combined with less than a minute of API unreliability for the entire year, indicates a highly efficient and rigorous engineering process.
* Rigorous Testing and Quality Assurance: Stripe runs more than six billion tests on code changes each day, evaluating each change with “a battery of 1.4 million tests.” This meticulous approach, described by the Collisons using a “peanut allergy test” analogy, ensures that changes won’t cause crashes and are thoroughly vetted before deployment. This implies that while the number of direct pull requests per engineer might be lower than some industry averages (around 2.3 per engineer per week at Stripe, compared to an average of 3.5), the quality and reliability of those changes are extremely high.
* Emphasis on “Auteurs” and Vision: John Collison, the other co-founder, stresses the importance of having an “auteur” (a specific person with a clear vision) at the helm of projects. This highlights a belief in concentrated effort and clear direction rather than simply throwing more engineers at a problem.
* Value of “Unglamorous” Work: Patrick Collison has noted that Stripe engineers tend to appreciate the “unglamorous” aspects of tech, which likely includes the extensive testing, refactoring, and infrastructure work that contributes to the overall stability and scalability of their platform.
* Profitability and Lean Teams: Stripe’s profitability and emphasis on “high leverage per employee” suggest that they aim for highly efficient, impactful teams. This mindset, also seen in AI coding assistant startups, focuses on maximizing output with a relatively lean workforce.
In essence, while a direct “revenue per engineer” figure from Collison isn’t available, his statements paint a picture of a company that prioritizes quality, reliability, and strategic impact from its highly compensated engineers, leveraging robust tooling and a culture of meticulousness to achieve a high volume of impactful changes.

Video courtesy of IPO-VID In Patrick’s Opinion

Video courtesy of IPO-VID In Patrick’s Opinion .