Taro Logo

Senior Software Engineer II Interview Experience

November 15, 2025
Negative ExperienceNo Offer

Process

I applied online, and the process took 3 weeks. There was a quick chat with a recruiter, a quick chat with a hiring manager, and a basic coding interview with 2 engineers on CoderPad. Then they scheduled 4 more interviews for coding, system design, product, and a meeting with the Director of Engineering.

Early in the process, the recruiter also sent me some links to do Predictive Index's Behavior and Cognitive assessments. The recruiter mentioned there was no rush on these, as they mostly just needed to be done before the final stages of the hiring process. For the most part, scheduling and early interactions were done quickly. Chatting with the hiring manager was nice, and I got to learn about the position and projects. The coding interview was pretty basic but generally fine.

From there, things were a little bit messy. The second coding interview was structured as a Ruby on Rails problem, but in CoderPad it wasn't actually set up in a Rails app. This was fine, just a little unrealistic in how you would actually solve the problem because you don't have all the tools of the framework. Other than that, it was an easy test. It did feel a little thrown together last minute, though, rather than something they might have prepared for candidates properly.

After that, I met with a Director of Product. This was fairly straightforward, and we discussed things related to how engineering and product work together. He did show up to this call 5-10 minutes late. Immediately after, I had a call with a Director of Engineering. Like the previous chat, he also showed up about 10 minutes late. This was a little annoying considering you're taking hours out of your day to get these interviews done. This chat was pretty basic, just talking about some previous experiences dealing with specific situations. He seemed slightly distracted, but I get it, he's probably a super busy guy. But that on top of being late wasn't a great look.

Finally, the next day I had the system design interview. I showed up and waited 10 minutes on Zoom, thinking "Okay, I guess it's just normal that everyone shows up late, but just in case let me email the recruiter/interview coordinator". I let them know that I'd been in the call for 10 minutes and that I'd give it another 5 or 10 minutes just in case, and if not we could reschedule. They never showed up, and I didn't hear back from the recruiter for over a day, only to be told that they decided to move forward with another candidate instead. I don't mind if they didn't think things went well during part of this process, but just not showing up to a scheduled interview and then not saying anything about it is pretty sloppy and unprofessional. Some feedback would be to make sure everyone who does interviews is properly prepared and trained, and try to make sure they prioritize showing up on time (or at least within a few minutes, as having 2 people show up 10 minutes late and one not at all is not great). Alternatively, on the scheduling side, make sure everyone has enough buffer between their meetings so that they have time in case certain things run long so that they don't run over other meetings.

Questions

Determine if a string is a valid IP address.

Given an array of strings, return a list of all unique valid IP addresses.

Was this helpful?

Interview Statistics

The following metrics were computed from 3 interview experiences for the Spring Health Senior Software Engineer II role.

Success Rate

0%
Pass Rate

Spring Health's interview process for their Senior Software Engineer II roles is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Spring Health's Senior Software Engineer II interview process.

Spring Health Work Experiences