Working at Fly.io

​

Where we hire

Fly.io is a distributed company, and remote work and asynchronous communication are important parts of how we operate. We currently focus our hiring in Australia, Brazil, Canada, France, Germany, Greece, New Zealand, Poland, Portugal, the United Kingdom, and the United States. These locations help us build working-hour overlap across teams and support employees consistently. Eligible locations vary by role, so please check the individual job posting before applying. We may consider exceptional candidates or referrals outside these countries on a case-by-case basis, depending on the role and our ability to employ and support someone in that location.

​

We’re committed to diversity and mutual respect

We believe in diverse and equitable teams. We’re working together on a hard problem, the work itself gets challenging, and our teams won’t work without mutual respect. Fly.io is used by people of all skill levels, all over the world, from many different backgrounds and with many different goals. We’re believers in the value of glue work and empathy, with each other and our users.

​

Visa sponsorship

We don’t make it a practice to sponsor work visas for new employees. If you’ll need sponsorship, please let us know early in the hiring process. Sponsorship should not be assumed.

​

We prefer small teams and bottom-up decisions

We like single-pizza teams: 3-4 people is a happy number for us. We’re a product for developers, by developers. We have a thriving community and everyone is expected to keep up with it and develop a sense for what’s worth doing and what needs fixing. We don’t have formal product roadmaps or schedules; we ship stuff when it’s ready.

​

We’re ruthless about doing customer-visible work

We want our teams to set their own direction as much as possible, but we’ll shoot things down if they’re not going to move the dials for our users. We’re vigilant about tar pits and projects that spin our wheels and will do our best to keep you out of them. We’re not big believers in “tech debt”. We have a 3-month “no refactoring” rule for new hires. This isn’t everyone’s preferred work style! We try to be up front about stuff.

​

Everyone shares an on-call rotation

Fly.io is a platform for shipping our customers’ apps. It’s on 24/7/365. We made a decision early on not to stick ops teams with the whole on-call challenge. So we all share it. At our current team size, on-call is 1 week roughly every 9 months or so. Most on-call is quiet! Because we all share the rotation, noisy alarms would drive all of us batty. If you get socked with a rough on-call, we’ll ask you to take the next day off.

​

Team flexibility

We get asked this a lot. Moving from a “big” category, like from Elixir UI to Rust platform work, will take some conversation and planning. But within a category, especially for platform work, you’ll get opportunities to work on multiple things.

​

Open source work

We’d open source the whole platform if we could (it’d take a year just to beat some of these components into releasable shape). We’re thrilled at opportunities to open source stuff. If something you’re working on can be open, we’ll work with you to open it up. We don’t have a lot of secrets.