Senior Backend Engineer (Foundation)

Join Proton and build a better internet where privacy is the default.

Proton was founded in 2014 by scientists from CERN on a simple truth: privacy is a fundamental human right. Since then, we’ve built the world’s largest encrypted email service (Proton Mail) and expanded into Proton VPN, Proton Drive, Proton Pass, and Proton Calendar—tools used by millions globally to protect their freedom, fight censorship, and keep their data safe. In some situations, Proton has literally helped save lives!

We are profitable, independent (no VC control), and selectively hire from the top 1% of applicants. Our 500+ team members across 50+ countries come from leading organizations and elite academic backgrounds. We move fast, keep hierarchy light, and prioritize impact over optics. If you want to do meaningful work with exceptionally high-caliber people, this is it. Join us and do work you can truly be proud of.

The Foundation Team

The Foundation team builds what the product teams build on: the shared backend framework, the internal libraries, the common services and abstractions that every Proton application reaches for. If several teams need it, it should exist once, and be good.

You will work in PHP for API related work, and in Rust for components where performance and memory safety justify it or for microservices. You will own libraries or initiatives end to end: design, implementation, documentation, versioning, and the migration path for everyone already depending on the old version.

Architecture is a large part of this role. Many engineers work in the same monorepo, which means module boundaries, dependency direction, and ownership are not academic concerns — they decide whether the codebase stays navigable or slowly turns into something nobody can change safely. You will help define those boundaries, make the structural calls that keep teams from stepping on each other, and do some work to enforce them: writing the RFC, adding rules, untangling the cycle that shouldn't have been there. None of this happens in isolation. You will work closely with other teams who consume and use what you build.

What You Will Do

• Design and build shared libraries, framework layers, and internal services used across every Proton product
• Turn recurring patterns into good abstractions
• Write documentation and examples people actually use, and treat adoption as part of shipping
• Improve the day-to-day: build times, local dev setup, test ergonomics, debuggability, developer experience
• Work in the open with product teams — RFCs, design reviews, and the occasional pull request into someone else's repo to show what you mean
• Work closely with other developers to help integrate libraries seamlessly into applications

Job Requirements

• 5+ years building and operating backend systems in production, including code you stayed responsible for long after launch, with a focus on modern PHP
• Working knowledge of Rust, or clear evidence you can get there quickly — we care that you understand ownership and lifetimes
• Genuine taste in API design. You have opinions about naming, defaults, error handling, and what belongs in a library versus a service
• A feel for architecture at codebase scale — you have worked somewhere large enough that module boundaries and dependency direction mattered, and you have views on what keeps a monorepo healthy
• Experience evolving shared code that other teams depend on, and doing it without breaking them
• A security mindset. You think about how the abstraction you just wrote will be misused
• The influence to get an internal library adopted rather than worked around, and the patience to carry a design through disagreement between two teams who both think they're right

Bonus Points

• Domain-Driven Design, or similar experience modelling complex domains where the boundaries matter
• Background in developer tooling, platform, or DX teams
• Contributions to open source, especially libraries with reusable components