Overall, the company is working on some interesting and valuable work, and the people seemed sharp, for the most part.
But there were two major red flags for me.
First is that they describe the role as a "data science" role throughout the whole process. But once you get through all the interviews, it's clear from the questions they ask you that this is actually a SQL jockey role. The most technical thing I was asked was some simple Python stuff (think easier than Leetcode easy). The rest had to do with pulling data and designing product metrics. If the company is going to be this misleading to candidates up front, I worry about what else they would lie about.
Second, several of the interviews were broad and open-ended case interviews, but the interviewers were clearly looking for specific answers to most of their questions and weren't able to adapt if I gave them a valid but alternative answer. Not only is this frustrating, it's a sign that Flatiron isn't investing in smart interviewing.
Product analysis questions, behavioral ("tell me about a time when...") questions, light SQL and Python coding.
The following metrics were computed from 10 interview experiences for the Flatiron Health Data Insights Engineer role in United States.
Flatiron Health's interview process for their Data Insights Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Flatiron Health's Data Insights Engineer interview process in United States.