The interview process included a recruiter screen, two 45-minute technical phone screens (the second was conducted to obtain a second opinion), and a 5-hour onsite interview. The onsite consisted of a product demo, three technical portions (systems design, debugging, and a coding problem), lunch (with one person to whom you could ask questions about the job and company), and an interview with the engineering manager.
I was a bit confused not to receive the offer, as I completed all the coding problems with time left over. Although I did get stuck once or twice for a few extra minutes, I eventually figured out the solutions without help.
They also left a lot of time for questions; in all, I believe over two hours of my interview process was allocated for me to ask questions. This was a bit stressful, as I had to keep coming up with new questions once my initial ones had been answered.
There was also no culture-fit portion, which I thought was odd. However, everyone was really nice and overall gave a great impression of the team and office.
Write an HTML-to-Markdown translator.
Write a Valuable class with weight and name, and then a SafetyDepositBox class with a capacity that can pass Valuable objects and handle capacity according to the Valuable's properties.
Write a command-line argument parser.
Debugging tests in a larger codebase.
Systems design for a page where customers can upload CSVs in a standardized format, and you want to put all that data into the database.
The following metrics were computed from 7 interview experiences for the Samsara Software Engineer role in London, United Kingdom.
Samsara's interview process for their Software Engineer roles in London, the United Kingdom is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Samsara's Software Engineer interview process in London, United Kingdom.