Real, anonymous reports from people who interviewed for Software Engineer at SentinelOne, newest first and distilled into what to expect across the loop.
Get your personalized SentinelOne Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After a recruiter reach-out, I filled in my availability and the interview invitations came quickly. The process moved fast and felt pretty straightforward from the start. I had a recruiter conversation first, and then the technical part happened online in English.
I ended up with two technical interviews back-to-back on video. The first focused on classic programming topics—standard problem-solving and coding fundamentals. The second shifted toward system design, where I had to reason through a design-style question rather than just implement an algorithm. Overall the difficulty felt reasonable, and the whole experience had a professional, efficient vibe rather than anything drawn-out or chaotic.
4 months ago
Difficult Positive Bengaluru
My process felt well organized and predictable. It started with an initial recruiter call where I was kept in the loop about timing and what would come next. After that, I moved into the technical rounds.
The first two interviews were both technical and centered on my skills and experience, and each interview was about an hour long. Questions were practical and meant to probe how I think and code, not just whether I could recite theory. The final step was a techno-managerial discussion, where the interviewer asked a mix of questions that ranged from simpler to harder depending on my background.
11 months ago
Average Neutral Bengaluru
I went through a fairly technical sequence that leaned heavily on DSA and then moved toward deeper system thinking. My first conversation was with HR …
> 1 year
Average Negative United States
After getting a referral, I was contacted by an internal recruiter and did a video call phone screen that felt like it went well. I then got scheduled…
> 1 year
Difficult Negative Czech Republic
My very first interview was a live, LeetCode-like problem-solving exercise. Even though I’d solved lots of similar problems before, this one was diffe…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process is generally well-organized, starting with a recruiter call followed by multiple technical rounds that include coding and system design interviews. Candidates appreciated the clear communication regarding the timeline and next steps, although some experienced delays and lack of follow-up.
Recruiter callTechnical roundsClear communication
Technical / Coding Interviews
Candidates faced a mix of coding challenges, often involving data structures and algorithms, with some interviews requiring live coding and real-time problem-solving. The difficulty varied, with some finding the questions to be tricky and focused on specific patterns, while others felt they were evaluated on practical skills and reasoning.
LeetCode-styleData structuresLive coding
System Design & Architecture
Interviews included system design questions that required candidates to discuss architectural choices and trade-offs, often at a high level. This aspect was emphasized as important, with interviewers looking for depth in understanding and reasoning.
System designArchitectureTrade-offs
Behavioral & Values Assessment
Behavioral questions were incorporated into the interviews, often framed in a STAR format, allowing candidates to showcase their experiences and thought processes. The emphasis on cultural fit and values was noted, though some candidates felt the behavioral aspects were less emphasized in certain interviews.
Behavioral questionsSTARCultural fit
Communication & Professionalism
While many candidates reported a professional and respectful interview atmosphere, some experienced disorganization and poor communication, particularly regarding scheduling and follow-up. This inconsistency affected the overall impression of the interview process.
ProfessionalismCommunicationDisorganization
Feedback & Outcome
Candidates expressed a desire for clearer and more constructive feedback following their interviews, as some felt the reasons for rejection were vague or tied to non-technical factors. The outcome of the interviews varied, with many not receiving offers but appreciating the experience overall.