I had a call with a recruiter, then a tech screen, followed by an on-site. Everything was fine, but the preparation was poor.
My main issue is that they claimed I would be working on "similar, everyday problems" in the technical portions. However, the truth is that I was still solving LeetCode-style problems with hidden data-structure solutions underlying them. 'Merge ranges' was obvious, and I was literally building a tree data structure from the ground up.
It's the same as most other large tech companies in the sense that generic LeetCode practice is valued.
Tech Screen: Build a search input field with React that communicates with an API. How would you optimize it (throttle, cache, etc.)?
Build a filter search function given a list of dates. This is very similar to merging ranges.
Build a class-based Tree data structure. (This is a very generic LeetCode problem; I wanted to walk out the moment I was given this problem.)
System design a CSV upload/save API. How would you store CSV files, and how would the client upload and retrieve those files?
The following metrics were computed from 4 interview experiences for the Samsara Full Stack Software Engineer role in United States.
Samsara's interview process for their Full Stack Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Samsara's Full Stack Software Engineer interview process in United States.