Software Engineer applicants have rated the interview process at Samsara with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 39% positive. To compare, the company-average is 50.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 20 days to get hired, when considering 83 user submitted interviews for this role. To compare, the hiring process at Samsara overall takes an average of 24 days.
Common stages of the interview process at Samsara as a Software Engineer according to 83 Glassdoor interviews include:
Phone interview: 42%
One on one interview: 20%
Skills test: 13%
Presentation: 10%
Group panel interview: 5%
Background check: 4%
Personality test: 3%
Other: 2%
Drug test: 1%
IQ intelligence test: 1%
Here are the most commonly searched roles for interview reports -
First a HR call - goes into project details, what you're looking for, etc
Got connected to a Hiring Manager for a project deep dive + TPS round within the hour. TPS question not too difficult - not leetcode.
I applied through a recruiter. I interviewed at Samsara in Nov 2020
Interview
A manager reached out to me on LinkedIn.
I had a 30 min chat with the manager followed by a technical phone screen on an online coding site.
The interview process and scheduling was pretty fast and recruiters were very responsive.
I thought the manager seemed rather inexperienced and was trying to build a new team out.
The phone screen seemed easy, and I thought I wrote well abstracted code and communicated well.
I received the decision that they didn't want to move forward after the phone screen one week after the interview.
I'm assuming they found a more senior candidate they wanted to hire because I thought the interview went well.
Interview questions [1]
Question 1
Design a class that represents a `Valuable` which has a name and volume. Design a `Safe Deposit Box` that holds a list of valuables and implement `add` and `remove ` methods. Each `Box` has a size (small, med, large) so take the volume into consideration when adding or removing.
Question was 3 parts. There may have been follow up parts that I didn't get to.
live coding session, create a md to html translator. It was all live with unique requirements making it more difficult than I expected using regex. The interviewer was not personable and it was a very uncomfortable experience
I made it to the technical screen and didn't proceed further. Recruiter call was the usual experience dive, comp discussion, and why you are looking for a job. The technical screen was a string parsing question.
Interview questions [1]
Question 1
Technical: String parsing. Be comfortable with regex