Two Flatiron Health Software Engineer candidates describe a multi-format process: recruiter or manager conversations, online coding, a live coding session, and behavioral rounds. Concurrency and clear communication stood out.
$165K
Avg. Base Comp
$211K
Avg. Total Comp
3-5 rounds
Typical Rounds
Not reported
Process Length
Two Flatiron Health Software Engineer candidates describe different full-time processes, and both ended without an offer. Treat the two reports as a small sample and prepare for variation.
One candidate began with a phone screen involving a recruiter and the hiring manager. That was followed by a take-home HackerRank with three coding problems in about an hour and forty minutes, an asynchronous one-hour LeetCode round, a live coding interview, and a final round with four team members. Two of those four focused on behavioral questions such as overcoming a challenge, and two pressed on technical topics. This candidate said one HackerRank problem involved multithreading, and they felt that was where they lost points. They also thought they could have explained their thinking better in the live coding session. If you are applying, do not overlook concurrency topics before attempting the online assessment.
The other candidate reported no recruiter call and about a week's wait before scheduling. They then had three rounds: a one-on-one with the manager, a behavioral session with a team member and the manager, and a technical component. The behavioral questions covered handling competing deadlines and communicating with product managers and designers. This candidate said all three rounds were completed regardless of earlier feedback, and the rejection came about a week later. They described the questions as straightforward.
Practice timed coding, prepare concrete stories about deadlines and cross-functional work, and rehearse narrating your reasoning aloud.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Flatiron Health process.
The interview process at Flatiron Health cycled through several formats, which I found both comprehensive and exhausting. After a phone screen with the recruiter and hiring manager, I tackled a take-home HackerRank challenge with three coding problems in an hour and forty minutes. One problem involved multithreading, which caught me off guard since I hadn't drilled concurrency issues as much as I should have. Then came an async one-hour LeetCode round, which was pretty straightforward online coding. The live coding interview felt like the more traditional gate, but what really stood out was the final round: four team members, two focused on behavioral questions like "name a time you overcame a challenge," and two who kept the technical pressure on. The whole process felt well-designed to test different angles, but I didn't make it past that final round. If I'm honest, the multithreading problem in the take-home is probably where I lost points, and I also think I could have done better articulating my thought process in the live coding session. For anyone prepping for this, don't overlook concurrency topics — they clearly care about that.
Prep tip from this candidate
The take-home HackerRank includes multithreading problems, so drill concurrency primitives like mutexes and locking before attempting it; that was the most surprising and challenging technical requirement.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Flatiron Health
Write a function to calculate precision and recall metrics.
| Question | |
|---|---|
| Book Combinations | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Top 3 Users | |
| Prime to N | |
| Weighted Keys | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| Google Maps Improvement | |
| Detecting ECG Tachycardia Runs | |
| Type I and II Errors | |
| The Brackets Problem | |
| P-value to a Layman | |
| Ride-Sharing App Schema | |
| Justify a Neural Network | |
| String Mapping | |
| Sort Strings | |
| Most Repetition | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Swap Variables | |
| Success Measurement | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Client Solution Pushback | |
| Customer Success vs. Free Trial | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Prime Numbers Identification |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports a phone screen with the recruiter and hiring manager. Another reports no recruiter call and began with a one-on-one manager conversation after waiting about a week. Expect the opening step to vary, and be ready to discuss your background and role fit.
One candidate reports a take-home HackerRank with three problems in about an hour and forty minutes, including a multithreading problem. They also report an asynchronous one-hour LeetCode round described as fairly straightforward. Concurrency topics may be worth reviewing beforehand.
One candidate describes a live coding interview as the more traditional technical gate and says they could have articulated their thought process better. The other reports a technical component as the last of three rounds. Explain your reasoning aloud as you code.
One candidate reports a final round with four team members, two focused on behavioral questions and two on technical ones. The other reports a behavioral session with a team member and manager about competing deadlines and working with product managers and designers. Prepare specific examples of challenges, prioritization and collaboration.
