We are (almost) the ideal Elixir/Phoenix hosting infrastructure because:
* Built in encrypted private networking means simple and secure clustering
* Running app processes close to users minimizes LiveView latency
* HA PostgreSQL clusters are the default
We are hiring an Elixir dev advocate to improve our tooling and show people how to get the most out of Elixir on Fly.io. This is important – our primary goal is to attract more Elixir devs as customers.
## The Work
We do content based developer outreach, this is not a high travel job. We think the work will break down like this:
* 20% working on the Fly.io UX for deploying and operating Elixir apps. This will mean working in Go and wrangling Docker – so Elixir folks don't have to.
* 80% community engagement: examples, blog posts, and community outreach. Hopefully you like working with open source projects and showing other people how to get the most out of them.
That 80% covers a lot! If you are actively working on a relevant open source project, you could theoretically spend almost all that time developing your work, posting about it on our blog, and showing people in the community how to use it.
Some of your content might be useful for talks. We want you to help us decide how valuable meetup and conference talks are. Later. When the pandemic is over.
This is our first attempt at focused developer relations. There is a lot to figure out. Your work will determine how we spend money on future marketing. If you're the type of person who wants to try a bunch of outreach to see what works, help build a dev relations organization from the bottom up, and even hire people to do the same work in other communities, you might _really_ like this job.
## The Hiring Process
Our hiring process is project based. We want to let you try the job on, see your work, and pay you to do a little more work.
1. Email jobs+elixir@fly.io, tell us in a few sentences what you like about Elixir.
2. Schedule a call with us so we can pitch the company to you and answer all your questions. We'll also tell you the bad parts.
3. Sample project: we have a small Phoenix + LiveView demo we want you to improve. This should only take about 2 hours, but you can spend as much time on it as you want: https://github.com/superfly/elixir-hiring-project#flyio-elixir-hiring-project
We rate the sample projects as objectively as possible. The best projects do what they're supposed to, use idiomatic Elixir, and are read-to-show.
In our experience, the hardest part of a sample project like this is just getting it done.
## A Larger, paid project
If we like your sample project work, we want to pay you to work on a larger project. We will offer a paid project ($1,000 flat rate) to about half the people who submit complete sample projects.
The goal here is to get a real, firm idea of what doing the job will be like. We'll get you setup with Slack access, a channel to work in, and future coworkers to collaborate with.
We want you to do four things for us:
* Write "Elixir community report" describing where Fly fits well with a plan for community outreach.
* Come up with a bunch of sample project ideas (like, 10). Single sentence descriptions of projects to demo Elixir on Fly.
* Build a from-scratch Elixir app to demo.
* Write a blog post about the demo app.
When you're done, we'll ask you if we can publish it.
## Working at Fly.io
We are a remote-first company with people in Chicago, Montreal, Boulder, and London. We're hoping we can take field trips to visit each other soon, right now all our work happens over chat with periodic audio breaks.
We're not a family, but we do _have_ families and try to keep work prioritized from dominating our lives.
Benefits are pretty typical for a company of our size – pretty-good healthcare for US based employees, flexible vacation time, and a hardware/phone allowance.
But, we're small! We all wear many hats and sometimes multiple hats at the same time. Come wear a hat for us.
To apply, email jobs+elixir@fly.io and tell us in a few sentences what you like about Elixir.
0 comments