Evan Rittenhouse is a software engineer with four years of experience building high-performance network and runtime systems, currently working on protocols at Cloudflare and previously at Amazon. He contributes to prominent Rust projects—such as quiche (QUIC/HTTP3) and Tokio—and is a core team member of Sequelize while contributing to Ruff, a fast Python linter written in Rust. Comfortable across Rust, Python, Java, and TypeScript, he blends low-level networking and async runtime work with database and ORM internals. A UCLA economics graduate who once researched in academia, he brings analytical rigor to debugging complex protocol and concurrency issues. Peers would note his unusual cross-cutting interest in both transport-layer protocols and developer tooling, with a knack for shipping tests and subtle correctness fixes.
4 years of coding experience
1 year of employment as a software developer
GPA 4.5/4.0, ACT 34, GPA 4.5/4.0, ACT 34 at Bellarmine College Preparatory
English, Economics, Economics, English, Economics, Economics at University of California, Los Angeles
🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
Role in this project:
Back-end Developer
Contributions:55 reviews, 51 PRs, 209 pushes in 1 year 7 months
Contributions summary:Evan primarily contributed to the implementation and testing of the QUIC transport protocol and HTTP/3 in Rust. Their work includes adding tests for HTTP/3 content length mismatches, making initial CWND configurable, exposing wire error codes, and adding various trait derivations to QUIC/HTTP/3 WireErrorCode enums. They also addressed issues related to FFI imports for Windows and implemented close trigger frames to close connections based on expected frames.
An extremely fast Python linter and code formatter, written in Rust.
Role in this project:
Back-end Developer
Contributions:105 reviews, 50 PRs, 273 comments in 1 year 4 months
Contributions summary:Evan's contributions primarily involve enhancing the "ruff" Python linter and code formatter. They focused on improving the tool's functionality, including implementing new rules and improving existing ones. This involved writing and modifying Rust code, as indicated by the file paths, and ensuring the correct behavior of the linter based on changes within python files. The user also contributed to the test suite, verifying the implemented rules.
linterpythonruststyle-guidepep8
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.