The team at Samsara is world-class. It's rare that a business has this breadth of expertise across the organization.
We're poised to build anything the customer needs, whether it is a new piece of hardware, cloud features, or a mobile solution.
Engineers are encouraged to visit customer sites and learn about their needs and complaints. The customer feedback loop is very strong at this company, and I feel you can rise in the organization if you work hard and deliver strong results.
We also have a lot of hardware to work on, and the types of hardware we offer are diverse. For firmware/hardware folks especially, that keeps the work fresh and interesting.
Cross-collaboration is great, and there hasn't been much in the way of gatekeeper culture here in my experience.
We have many new people. Our onboarding experience is amazing, but I feel we could do a better job encouraging (requiring?) new folks to dogfood the products and walk through the customer journey at the very beginning. This could include visiting a customer site within the first 3 months of starting, depending on their level.
Otherwise, people get too busy and start to de-prioritize those things. These are critical for building customer empathy and gaining perspective on the end users of our work.
You're doing a great job. Keep up the in-person events (both the larger ones and the smaller team-focused ones), all hands, and roadmap communication. Excited for where we're going!
Online assessment: Generic coding questions (LC easy/medium, which were very easy) were included, but also a bunch of annoying trivia questions about languages. Examples include: How are arrays implemented in Go? Is array length a part of the array
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.
HR contacted me via LinkedIn, and the interview was supposed to be in two phases. I was rejected in the first round, which was the coding round. They mentioned the coding question was open-ended and not necessarily needed to be complete, but I think
Online assessment: Generic coding questions (LC easy/medium, which were very easy) were included, but also a bunch of annoying trivia questions about languages. Examples include: How are arrays implemented in Go? Is array length a part of the array
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.
HR contacted me via LinkedIn, and the interview was supposed to be in two phases. I was rejected in the first round, which was the coding round. They mentioned the coding question was open-ended and not necessarily needed to be complete, but I think