Signify Health Software Engineer Interview Questions
& Process

I was contacted by a recruiter on hired which led to a 30 minute conversation with them to talk salary. Then a 30 minute conversation with a director to talk about my current position and why I'm looking. This was followed by a 1 hour and 15 minute technical conversation and coding question that would "go over my C# skills". This was split into a 50 minute conversation followed by 10 minutes to solve a problem on a coding site, then 15 minutes for my questions. There wasn't enough time to complete the coding question in that little time frame. I was told I got further than most. I was able to answer every question and their follow-up questions without being prompted. Their segues are very obvious. SOLID, DI, interfaces, database structures, etc. (all things a senior engineer should know). The next step would have been another 30 minute conversation with someone higher up. From my questions, all the con reviews were made more obvious. Do research and ask the correct questions.

So I interviewed for a Software Engineer role at Signify Health. It was a pretty long process, took over three months with three interview rounds. I put in a lot of time and effort, and then they hit me with another round request. But then, I got rejected out of the blue, no explanation given. The biggest headache was the terrible communication and how unclear everything was. If a hiring process drags on for three months, they should at least give you some feedback or tell you why you didn't make it, especially after you've done multiple interviews. Candidates spend their time on technical tests and interviews, and a good hiring process should respect that. I'm hoping Signify Health gets better at this, maybe by making the process smoother and keeping communication clear and on time.

So, first there was a phone screening, then another phone interview. After that, I had a 2 hour long Google Meets interview where they asked me some technical questions and about my background working with others and other parts of my resume. Oh, and there was a little coding challenge before the 'in person' interview too.