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.
I started with an interview conversation where I was asked to explain what I do in my current role. I quickly realized the interviewers weren’t able to follow what I was describing, and I kept getting pushed to repeat myself. The atmosphere turned awkward and negative fast.
What really threw me was how one interviewer reacted when my answers weren’t landing the way they expected—there was a laugh when my response wasn’t what they wanted. I felt like I was being judged more for clarity gaps than for the substance of my work, and the vibe never recovered. By the end, I could tell it wasn’t going in my favor, and I didn’t get an offer.
6 months ago
Average Positive Austria
My process started with a technical screening, then I moved into an interview with the hiring manager. After that, I went through two technical interviews that both involved coding exercises. Everything felt tightly scheduled: each interview lasted about an hour, and the whole flow was pretty structured from start to finish.
The experience itself was fairly standard for software engineering hiring—focused on evaluating how I work through coding tasks and how I handle questions in a live setting. I didn’t feel like the process dragged or got chaotic; the structure was the main thing I remember. Even though it seemed organized, I didn’t end up getting an offer.
6 months ago
Difficult Positive Prague
Recruiter screening kicked things off, then I had a technical interview and a manager/team meeting. What stood out most was the pace—everything moved …
8 months ago
Average Neutral Bengaluru
HR called me first to talk through my background and skills, then we scheduled the rounds. The first technical round was a DSA-style question, a varia…
10 months ago
Average Positive Bengaluru
I went through a campus-style interview sequence: first a technical assessment, then a technical interview, and then a final managerial round or a sec…
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 typically follows a structured format, often starting with a recruiter screening, followed by technical interviews that may include coding exercises and system design discussions. The timeline is generally fast-paced, with some candidates noting that the entire process can be completed in less than a week.
StructuredFast-pacedRecruiter screening
Technical Assessments
Candidates can expect multiple technical rounds focusing on data structures and algorithms (DSA), low-level design (LLD), and sometimes specific technologies like JavaScript and React. The technical interviews often involve live coding exercises, with a focus on both problem-solving and optimization strategies.
DSALLDLive coding
Behavioral & Managerial Rounds
The final stages of the interview process usually include a managerial round that emphasizes behavioral questions and team fit. Candidates should be prepared to discuss their experiences and how they align with the company's values and expectations.
BehavioralTeam fitManagerial
Interview Atmosphere & Communication
The atmosphere during interviews can vary significantly, with some candidates reporting a friendly and respectful environment, while others experienced interruptions and a lack of engagement from interviewers. Clear communication about the process and feedback is noted as a critical factor in the overall experience.
AtmosphereCommunicationEngagement
Expectations for Depth of Knowledge
Candidates should be ready for in-depth questions that go beyond surface-level knowledge, especially regarding specific technologies and problem-solving approaches. Interviewers often expect candidates to demonstrate a strong understanding of the tools and frameworks relevant to the role.
Depth of knowledgeTechnical expertiseProblem-solving
Feedback & Outcome
Feedback can sometimes be vague or delayed, leaving candidates unsure about the reasons for rejection. Many candidates expressed a desire for more direct communication regarding their performance and the decision-making process.