Zywave Software Engineer Interview Questions
& Process

The hiring process kicked off with a tough, multi-part test covering math, IQ, personality, and more, which was challenging because of the tight time limit, though the questions themselves were pretty clear. After passing that test, an HR rep called me for a phone screen – just the typical introductory chat. Then, I had to go back to their main office to retake the test (to make sure I hadn't cheated) and do an in-person interview. The in-person part involved some technical questions, some situational ones, and a good chunk of time discussing the role and the company to see if we were a good match. I got an offer not too long after. The recruiter was really helpful and kept in touch the whole way through.

Initial phone screen with HR, mostly checking communication skills rather than tech. Then an hour-long onsite interview covering past projects and some OOP technical questions.

Overall it was a very pleasant and productive interviewing experience. It started with your standard HR phone screen, which we actually had to reschedule because the HR person was called away on an emergency. They were very apologetic and professional, and that professionalism carried through the rest of the process. I was also a little worried because previous reviews had mentioned those personality and IQ tests that were all the rage in tech for a while... not necessarily because I was worried about passing, but because I don't think they're a great way to assess a candidate's ability to do their actual day-to-day job. This appears to have been dropped in recent years, which to me says that the company is willing to amend their hiring practices and adapt to industry best practices. Green flag. There were three rounds of interviews after the initial screen: an initial technical screen, a leadership/personality fit call, and a final, more in-depth technical interview. There were two engineers in each, and they were all very pleasant to talk to. The last interview was way more tech-heavy, but it was more of "how would you..." questions, not the rote memorization or abstract theory that you get a lot of the time. I also appreciated that while the engineer interviewing me was working on a different tech stack, they had one from the team I'd be working on there as well to help with questions and subjects specific to our stack. Overall, seems like they have their stuff together, and it was a really good process.