I had an initial phone call with a recruiter who explained the company, the types of problems they solve, and the projects their developers work on. The recruiter advertised the technical interview process as one where you shouldn't have to study for a coding exam that isn't pertinent to the day-to-day challenges software engineers solve. They stated the interview would reflect real-world problems.
This was false advertising. The coding round consisted of writing a program to convert Markdown to HTML. I'm not sure what developer spends their day-to-day writing such a tool from scratch, as there are plenty of third-party tools to assist with such a need. Therefore, this did turn out to be a very LeetCode-style interview that didn't accurately reflect what a software engineer does in their day-to-day.
Write a tool to convert Markdown to HTML.
The following metrics were computed from 6 interview experiences for the Samsara Senior Software Engineer role in San Francisco, California.
Samsara's interview process for their Senior Software Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very negative feelings for Samsara's Senior Software Engineer interview process in San Francisco, California.