The initial screening was a HackerRank test, which had a rather basic Python portion and an SQL portion that was significantly more complex.
If it were a normal HackerRank problem, I'd say that it would go in one of the more advanced categories. It tested rather complex subquery and joining knowledge, but it did give 90 minutes to complete the two sections.
I was selected for a Zoom meeting following my performance on the initial screen, which was basically 30 minutes of typical interview questions, clarifying experience, and a brief case study before moving on to another live HackerRank problem-solving session/live coding demo.
Again, the SQL problem that they presented here was quite complex, and the interviewer was very interested in techniques used to make SQL queries more efficient. So, just getting something that worked was not enough.
I did not proceed past this round, but the next round would have been a block of more coding demos with several different Flatiron employees over the course of a few hours.
Mostly live coding SQL questions, which were fairly difficult and had a heavy emphasis on optimization and more complex functionality.
The following metrics were computed from 2 interview experiences for the Flatiron Health Data Reporting Engineer role in New York, New York.
Flatiron Health's interview process for their Data Reporting Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Flatiron Health's Data Reporting Engineer interview process in New York, New York.