The OSS maintainer to staff engineer pipeline

Open source maintainers and staff-plus engineers share many similar responsibilities and skills, particularly around technical leadership without direct authority

Key abilities include distributing knowledge, delegating work, and scaling oneself beyond being the bottleneck for decisions

Documentation through RFCs, ADRs, and design docs helps create asynchronous references and historical context for decisions

Automation of manual processes and tooling helps reduce maintainer burden and enables others to contribute more effectively

Succession planning is critical - projects without plans for knowledge transfer and new maintainers risk withering away

Communication skills are essential for convincing and motivating others to follow technical direction without formal authority

Being “glue” work - coordination, documentation, mentoring - is as important as deep technical contributions

Creating supportive environments and clear paths for new contributors/maintainers is key for project sustainability

Both roles require balancing deep technical knowledge with the ability to distribute that knowledge to others

Documentation and processes should be designed for “random people on the internet” to understand and contribute effectively