JupiterOne Software Engineer Interview Questions
& Process

The interview journey consisted of a 1-hour session with the hiring manager, followed by a 4-hour take-home project that seemed to reflect actual job duties. Then there were two 1-hour technical interviews with engineers. The first technical interview felt a bit rushed, but manageable. The second one was quite challenging; I was asked to design a system within a tight 15-minute timeframe. It felt unfair because defining requirements alone should take at least 5 minutes of discussion. When I tried to take more time, I was pressed for specific database design details, making it hard to justify choices without any given requirements or assumptions. It felt like I was just spouting buzzwords. Despite the system design hiccup, the rest of the process felt fair and job-related, which I appreciated. The total time commitment was 9 hours spread over 2.5 weeks, which felt like a lot for a rejection.

The interview involved a 1hr session with the engineering manager, followed by a take-home project. After that, there were two 1hr technical interviews with engineers, and finally a 1hr behavioral interview with management. The total time spent on the take-home and interviews was about 9hrs. During one of the interviews, I was asked to design a system for a non-trivial application, but only had 15mins left. It felt impossible to properly assess my thought process or have a meaningful technical discussion in such a short time; I just had enough time to throw out buzzwords with brief justifications.

I got referred and the whole thing took about a month. It started with a get-to-know-you chat, then a take-home assignment, and finally a meeting with the team to check out my technical skills.