J'ai postulé en ligne. Le processus a pris 3 jours. J'ai passé un entretien chez Samsara (Atlanta, GA) en mai 2019
Entretien
Similar to other interviews mentioned, initial phone screen with the recruiter then a coding exercise using coderpad, which is the most useless tool that can be used for a coding exercise. The instructions mentioned that completing the exercise isn't needed and to be collaborative with the interviewer. I did just that, but the interviewer seemed to be very awkward and I had the impression that I was an interruption to his day. Even though I can tell English is not his first language, he would just give me one word answers and didn't seem at all interested in having a conversation with me. Like other candidates mentioned I have no clue what they're looking for, but if my interviewer was any indication to the type of employees they want, then this isn't a company for me.
Create a Pallet class that has a unique id and weight
Create a Truck class that has pallets with a load and unload methods
Write a method to get the weight of the truck
One of the worst interview experience that I had, the interviewer came more than 5 mins late. Then he gave me a question to solve and then straight away got busy on his phone. Some of the decisions that we
Only had an initial call with a frankly clueless recruiter. Could tell me very little about the role, what I would be working on, or even the tech stack. Interrupted me constantly and kept asking me if I had any more questions when she couldn't even answer the few I did have. Probably the worst HR phone screen I've ever had, and I've had a few.
Recruiter round was smooth and professional. However, the technical interview didn’t match what was described. The prep materials clearly said no Leetcode, and focused on Samsara's system related.
I prepared accordingly, but the interview ended up being a standard Leetcode medium. Disappointed by the mismatch — if algorithm questions are preferred, let candidates know.
Advice to others:
Prepare for Leetcode