Candidates describe a Signify Health Software Engineer process with a recruiter or HR screen, manager conversation, live coding, and system design, plus slow communication. Both Software Engineer candidates ended without an offer.
$149K
Avg. Base Comp
$165K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Two candidates who interviewed for the Signify Health Software Engineer role describe different processes. One reports a screen, a manager interview, and a technical board round with live coding. The other describes a face-to-face first round, a high-level system design discussion, and a request for a further round. Both ended without an offer.
The clearest technical signal comes from the candidate with a Java background. The manager round went deep on object-oriented fundamentals, including why strings are immutable in Java and what that design implies. When that candidate mentioned the MERN stack, the questions moved to API calls and how requests and responses move between client and server. Be ready to explain anything on your resume at that level.
The other candidate faced a scenario question about designing test cases with a lab environment in mind, then a system design conversation. A separately reported Senior Software Engineer interview used a pizza delivery system for design, so practice walking through a service end to end.
Timing varied. One candidate reports about a month, partly stretched by holidays. The other reports more than three months. Both mention slow communication between rounds, so ask each interviewer about next steps and the expected timeline. Coding problems were not recalled in detail, so cover general live-coding practice rather than targeting specific problems.
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 Signify Health process.
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 Signify Health
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Prime to N | |
| Weighted Keys | |
| Top 3 Users | |
| Hurdles In Data Projects | |
| Employee Salaries (ETL Error) | |
| Bagging vs Boosting | |
| Detecting ECG Tachycardia Runs | |
| Size of Joins | |
| The Brackets Problem | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Sort Strings | |
| String Mapping | |
| Precision and Recall | |
| Most Repetition | |
| Valid Anagram | |
| Find Duplicate Numbers in a List | |
| Success Measurement | |
| Target Indices | |
| Priority Queue Using Linked List | |
| Customer Success vs. Free Trial | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Prime Numbers Identification | |
| RAG Strict Source Control | |
| String Palindromes | |
| Concurrent LLM Serving | |
| Type I and II Errors | |
| Swap Variables |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports an HR screening focused on their background, previous work, and the projects they had built. It was described as fairly straightforward. Expect to summarize your experience concisely, and a tell-me-about-yourself opener may come up, as another candidate reported in a first-round conversation.
A candidate with a Java background reports in-depth object-oriented questions, including why strings are immutable in Java. After mentioning MERN experience, they were asked how API calls work and how data flows between client and server. Prepare to explain the fundamentals behind technologies on your resume.
One candidate reports a technical board round that included live coding, with an expectation to write and discuss code in real time. They did not recall the specific problem, so the exact topics are unknown. Practice talking through your approach aloud while coding, not just reaching an answer.
Another candidate reports a face-to-face round with a scenario question about test case design for a lab environment, followed by a high-level system design discussion. A Senior Software Engineer candidate reports a pizza delivery system design prompt. Format and depth may differ by team and level.
Both Software Engineer candidates report slow communication between rounds and no offer. One reports being asked to schedule an additional round and then being rejected without feedback. Candidates may want to confirm timelines after each round and follow up politely, since closure was not always clear.
