Senior Release Engineer

We’re looking for a Release Engineer who can own our development process. This would be a great role for a mid-level or senior engineer looking to join a fast-growing security startup.

Firezone’s product runs on a wide range of Linux distros and needs to interface closely with kernel technologies like WireGuard and eBPF. Our product is also mission critical to our customer’s security posture. This presents challenging problems for the build-and-release pipeline and also means the bar for reliability is extremely high.

We’re looking for a talented Release Engineer that can own our CI pipeline, setup and maintain Arch, Debian, and Redhat package repositories for Firezone, and create containerized deployment options for Firezone (Docker, Kubernetes).

Key features that make the role unique:

• Firezone is built primarily in Elixir which runs on the Erlang BEAM. Packaging an Erlang application for distribution is not a trivial task — Erlang expects the same dependencies on the deployed target as the build host. We use Chef Omnibus to solve this currently, but we’d love to find better ways. If you love hacking on compiler infrastructure, diving into the nitty gritty of Linux package structures, or building award-winning CI pipelines, this is the perfect role for you!
• Most of your work will be public — our codebase is open source.
• Work closely with our users to ship features and fix bugs.
• Be a founding engineer - You’ll make core architecture choices, shape company culture, and help set the bar for quality and execution for our development lifecycle.

Hiring Process

We value the ability to learn quickly, take ownership, and ship product features over raw years of experience or company logos on your resume. Our goal is to make a well-informed decision based on your ability to do the work you’ll be expected to do at Firezone without subjecting you to a long drawn-out process. Our process involves:

1. Introduction Call - A chance to connect and see if there is interest from both sides, share more about our vision and roadmap, and learn more about your experience.
2. Take-home Coding Challenge - We're not fans of live, hours-long coding interviews since they don't resemble how most engineers get work done. Instead, we'll give you a 1-2 hour take-home challenge related to the role. You’ll be solving a problem similar to something you’d face in your day-to-day work.
3. Take-home Followup Call - We’ll hop on a call to go through the completed take-home challenge and a few technical Q&A related to the role.
4. Final call - If we have any additional questions we’ll schedule a short follow up call.
5. Background and reference checks.
6. Offer Decision