Real, anonymous reports from people who interviewed for Software Engineer at Flatiron Health, newest first and distilled into what to expect across the loop.
I tried to interview for a Software Engineer role and the experience was exceptionally frustrating and hard to complete, with no meaningful timeline communication after an emailed coding test.
I interviewed for a Software Engineer role with a standard assessment-then-collaboration flow, where the main work was an online test followed by a practical engineering pairing a few stages later.
Candidates often start with an automated coding test sent via email, which serves as an initial filter before any further discussions. This stage can lead to frustration if there is a lack of communication regarding outcomes.
The interview process typically includes multiple technical interviews, often featuring coding challenges that range from medium to difficult, with a focus on data structures and algorithms. Candidates should be prepared for both timed assessments and live coding sessions.
Many candidates experience a Karat-based interview format, which involves a structured coding interview that emphasizes completion and correctness. Success in this stage often hinges on effectively solving problems under time constraints.
Interviews often include behavioral questions that assess candidates' past experiences and alignment with company values. Candidates should prepare to discuss their backgrounds and how they handle various work scenarios.
The overall structure of the interview process can vary, with some candidates noting a lack of clear communication regarding timelines and outcomes, which can lead to a feeling of being 'ghosted' post-interview.
Candidates often report that the final decision stage can feel opaque, with some experiencing delays or unclear feedback after multiple rounds of interviews. Understanding that internal hiring may affect outcomes can be crucial.
