Senior Rust Engineer (Systems)

We’re looking for a senior systems engineer to make foundational technology decisions and help mentor a growing team. This would be a great role for a seasoned systems engineer looking to overcome distributed systems challenges at an early-stage security startup. If you thrive on solving low-level packet hacking problems, lie awake at night dreaming of NAT traversal, or obsess over squeezing every last bit of performance from your network stack, this role is ideal for you!

You'll be responsible for designing, testing, and implementing various parts of the Firezone connectivity layers in Rust. These layers have platform-dependent codepaths for interfacing with the network stacks for each platform. So bonus points if you have Apple, Windows and/or Android development experience! Much of your work will run on those platforms.

The ideal candidate will have at least 3 years (or equivalent) experience shipping and operating Rust code in production.

Key features that make the role unique:

• Ship code that runs on thousands of customer's devices worldwide
• Overcome connectivity challenges related to blocking of the WireGuard® protocol by nation-states, crappy public WiFi, and other hostile networks
• Opportunity to "wear many hats": Rapidly level up your skillset across a variety of technologies from cross-platform development to TCP/IP hacking, to hacking on core pieces of the WireGuard protocol, to packet interception and mangling.
• Nearly all of your work will be public — our codebase is 100% open source.
• Be a founding engineer - you’ll make core architecture choices, shape company culture, and help set the bar for quality and execution.
• We're a remote-first team, but we also value human interaction: we meet regularly for fun offsites, conferences, or hackathons.

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. Technical screening call - A more in-depth call to chat about technical concepts and possibly a live-coding exercise that would resemble your day to day work.
3. 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 day-to-day work.
4. Team call - You'll meet with members of the team individually to assess culture fit.
5. Background and reference checks.
6. Offer Decision