En la entrevista para Senior Software Engineer en JumpCloud suelen preguntar sobre diseño de sistemas, APIs, debugging, arquitectura escalable, liderazgo técnico, experiencias resolviendo incidentes, trabajo colaborativo, decisiones técnicas, pruebas, seguridad, cloud computing y manejo de proyectos complejos bajo presión.

The interview started with a phone screening where I talked with a contact from HR who had contacted me through LinkedIn. That went well and they just got a feeling of me and my background. I had then talked with a hiring manager who went over the work history and my fit with the team. it covered basic questions about the work they do and how well I could perform with them. Overall, no surprises there. Next up was a take home assignment that I was told would take about 4 hours. It was very easy, all things said and done. I knew what needed to be done within a minute of looking at it, even considering it needed to handle multithreading. With comments, cleaning up, and pushing to github, this took me about those 4 hours they estimated. I may have gone over purely for fixing style choices. After the take home assignment, I had 3 separate interviews. The first was discussing the coding assignment and basic software principles. The second was talking architecture and system design, going through a mock scenario, given ambiguous requirements and talking out how to narrow down choices we'd make. Finally, I had an interview with hiring manager again just to have a final chance to ask questions and provide feedback. I was provided an offer within an hour or two of the final interview but I unfortunately turned it down. JumpCloud did seem like a nice company to work for and offered a very competitive salary with decent benefits (no 401k match *yet*) but it would be 100% remote for my location and I wasn't sure how that would fit and if I'd be able to cope with it.