Pager Health Software Engineer Interview Questions
& Process

The interview process was quite lengthy and thorough, but genuinely enjoyable because everyone involved was incredibly kind, professional, and keen to understand me as both a person and a professional. They wanted to see how my skills could help achieve the company's goals. The stages included: 1. An HR interview with a technical recruiter to go over the role, my background, and anything I wanted to know about Pager. 2. An interview with an engineering manager where we discussed general software engineering topics like hash tables, scaling, performance, and stack vs. heap, plus some behavioral questions. 3. A live coding session, like pair programming with a senior engineer, to check my problem-solving, data reasoning, and communication skills. 4. An architecture interview with two senior engineers or tech leads where I had to propose a high-level architecture for an app description, using diagrams, database design, etc., without coding. 5. A hiring manager interview. 6. A People Ops interview. 7. An interview with the SVP of Engineering. The last three interviews (Manager, People Ops, SVP) were more about meeting people from different departments I'd work with, focusing on open conversation and cultural fit. 8. Finally, the offer letter and negotiation, though no negotiation was needed as we agreed on the compensation upfront.

It started with a recruiter call, which was pretty standard. They asked about my background and a challenging project I worked on. After that, I had to complete a technical self-evaluation form. Then, I had a call with the technical hiring manager where we discussed my self-evaluation answers. The vibe was chill. We were on Zoom, and there was a coding exercise. We used a shared editor, but no screen-sharing, and the code wasn't actually run. It was more about seeing how I approached the problem. I think I messed up pretty bad on the javascript and sql parts, even though the coding itself was alright.

First, there was an initial recruiter call. Then, I had to answer some coding questions on Coderbyte. The last part was an architecture interview where I had to design or reverse engineer a common fintech domain. I didn't pass this last part.