J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Fly.io (New York, NY) en août 2023
Entretien
I see all the other reviews, I did my test assgnment and got an automated reply (very clear my work wasnt review, it was a standard reply that made no sense). BUT YOU CAN KEEP YOUR TEST CREDITS. To test them in this very dishonest and dodgy marketing ploy. I sent them a CV with a last date working 15 years ago. And also another blank one from alternate email addresses. Both got the same reply (conveniently they have a well scripted line about not looking at resumes, we’re a bit weird and yadda yadda yadda) Both test applications received the same scripted email, I passed (I DIDNT EVEN DO IT THE 2nd and 3rd times) But guess what? Lucky you! You get to keep their credits. Man these guys are arrogant. Don’t waste your time. No respect for the applicant, just a very arrogant ploy to suck you in. You know what, they’re right. They are very very weird. Just dont waste your time on these job ads. One other thing I noticed, theyve been “interviewing” the same roles for many many months. Further proof.
2
Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez Fly.io
J'ai postulé en ligne. Le processus a pris 2 jours. J'ai passé un entretien chez Fly.io (Sydney) en nov. 2025
Entretien
It's a very interesting process that respect our time. I haven't gone through the final phases, but we can clearly see that I've aligned on the concerns they raise about traditional hiring process. Also, they make it clear what are the expectations for the interview itself and the role.
Also, they try to mimic problems that they have on their daily bases, not a synthetic kind of challenge.
Questions d'entretien [1]
Question 1
I only went through the initial System Design. Which consisted of improve their system that create their machines.
J'ai postulé en ligne. Le processus a pris 2 jours. J'ai passé un entretien chez Fly.io en août 2023
Entretien
Had a coding task and a product-related problem that I needed to scope down and solve. I limited my time on the coding task and passed after writing a small amount of code. The coding task is vague, so it's important to quickly figure out what you want to solve, otherwise you will waste time. The product-related problem was very open-ended, which is intentional to reflect the real-world environment, but it felt like the person on the other end wasn't necessarily collaborative. I've had other interviews with a similar approach and they were a lot more enjoyable. It felt like I was battling against instead of working together with someone, so I bowed out.
Questions d'entretien [2]
Question 1
Come up with a solution for an issue in an Elixir application. The application is a mock, you need to figure out how you'd solve the issue in real life, and (hopefully) demonstrate it by writing some code using the mock application.
Design a solution to solve a problem that some users have with an application. No coding, just need to ask questions and come up with a potential solution.
