I applied online. I interviewed at Flatiron Health
Interview
I had a call with a member on the team and then was asked to come onsite. The interview was 4 hours long and it went ok, after 2 days I got an email stating that I was rejected because the interviewer felt I did not have enough experience working with customers directly.
I applied online. The process took 1 week. I interviewed at Flatiron Health (New York, NY) in Nov 2021
Interview
Technical interview with manager (Spotlight):
It was too friendly to begin and the air of politeness creates a barrier between the candidate and the interviewer. Simple: tell-me-about-yourself, then 1 Python question (which was really long and clumsy) and you only have 10 minutes for this one. Then another 10 minutes for SQL (really Flatiron Health based), which is not easy to understand by common sense. I was really annoyed and nervous.
They should not throw these scenario-based questions to interviewers and expect them to come up with a clean set of code within 10-mins timeframe. Instead, throw them on Hackerrank and let candidates work through their assignments on their own terms.
Their technology stack is quite unique and not applicable for anyone in the long term. Please avoid!
Interview questions [1]
Question 1
Two HackerRank assignments prior to interview with manage:
* Python: Sort consonants vs vowels
* SQL: Medium leetcode. You need to know isnull, window functions, group by and CTE.
I applied online. I interviewed at Flatiron Health (New York, NY) in Apr 2020
Interview
The initial screening was a HackerRank test which had a rather basic Python portion and an SQL portion which 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.
Interview questions [1]
Question 1
Mostly live coding SQL questions which were fairly difficult and had a heavy emphasis on optimization and more complex functionality.
