 <dl> <dt> Now Hiring </dt> <dd> <span></span> Intern </dd> <dd> <span></span> Level 1 </dd> <dd> <span></span> Level 2 </dd> <dd> <span></span> Senior </dd> </dl> <section> <div><p>We’re building something ambitious at Fly.io: a new public cloud, running on our own hardware all over the world, built to make it easy to run apps close to users everywhere.</p></div><p>Don’t just skim this post. There are lots of different kinds of full stack engineers, and we’re on the hunt for someone very specific.</p> <p>For the past five years, we’ve been working on a public cloud platform that has the ergonomics of “platform as a service” offerings like Heroku, but the power, flexibility, and economics of a hyperscaler cloud. Those goals are in tension, which makes working on UX here especially challenging.</p><h3><a></a><span>This Role</span></h3><p>A full stack engineer at Fly.io is primarily an Elixir/Phoenix developer. The work is front-end and interaction design as much as it is stitching APIs together for new features.</p> <p>But Fly.io isn’t primarily written in Elixir, and every decision we make from button sizes to distributed consensus algorithms is driven by user needs. So you won’t just be thinking in Elixir: our CLI is a Go program, as is our API, and other components are in Rust and Ruby. You won’t own these components. But you’ll need to understand them and drive changes in them. It’s a daunting problem, so this is a senior role.</p> <p>Fly.io has historically been a CLI-first company. The CLI isn’t going anywhere, but our emphasis is shifting. So, when we think about full stack development, what’s in our head is: someone who makes sure our team is shipping tightly scoped features and continuing to refine them with rapid iterations, all in a strong browser-based interface.</p> <p>Finally, Fly.io is weird about product management, and that’s especially the case with the type of UX work you’ll be doing. You will not have a PM to rely on for feature breakdowns or roadmaps. You’d need to be prepared to come out of the gate with strong ideas about what’s going to make our users’ lives better, and what’s going to make them happy in the long run.</p><h3><a></a><span>Seriously, This Is a Fussy Role</span></h3><p>We’re not afraid to talk you out of it. You’d need to be:</p> <ul><li>Attuned to the needs of users who ship things on public clouds. Check out our public community if you think that’s easy to do consistently.</li><li>Relentlessly focused on cutting scope to ship the most important thing for customers and then iterating from there based on user feedback. We work with 2-week horizons here; 6 months from now might as well be the year 3000.</li><li>Rock solid with Elixir/Phoenix. Unafraid of Go.</li><li>Able to keep a model in your head of ambitious features that are implemented across many layers of software, many of which you don’t own. You have to be willing to get your brain dirty.</li></ul> <p>To us, all these things that make this job complicated also make it interesting. If we’ve held your attention this far, let’s see if we can make something work.</p><h3><a></a><span>How We Hire</span></h3><p>This is a senior, fully remote, full-time position.</p> <p>In order to optimize for pay equity, Fly.io doesn’t negotiate salaries. We have standardized salaries for each employee level. The salary for this role is $190k USD. We offer competitive equity grants with a long exercise window. We provide health care benefits, flexible vacation time (with a minimum), hardware/phone allowances, the standard stuff.</p> <p>Our hiring process may be a little different from what you’re used to. We respect career experience but we aren’t hypnotized by it, and we’re thrilled at the prospect of discovering new talent. So instead of resumes and interviews, we’re going to show you the kind of work we’re doing and then see if you enjoy actually doing it, with “work sample challenges”. Unlike a lot of places that assign “take-home problems”, our challenges are the backbone of our whole process; they’re not pre-screeners for an interview gauntlet. (We’re happy to talk, though!)</p> <p>There’s more about us than you probably want to know <a>at our hiring documentation</a>.</p> <p>If you’re interested, email <a>jobs+fullstack-phoenix@fly.io</a>. In the body of your email, please include your location (country), and your GitHub username for work sample access. We’d also like to know your favorite food! We probably won’t respond to emails that don’t include all three, because we’re trying to concentrate our hiring efforts on folks who are super detail-oriented.</p> <p>If you’re considering applying to multiple positions, please send separate emails for each one.</p> </section> <dl> <dt> Work From </dt> <dd>      Anywhere </dd> </dl> 