Real, anonymous reports from people who interviewed for Software Engineer at Security On-Demand, newest first and distilled into what to expect across the loop.
My interview process felt unusually drawn out—roughly two months—before it ended without an offer. What bothered me most wasn’t the general length as much as the timing of the final step: I was asked to prepare a one-hour presentation after the company’s leadership had already been aware of the acquisition context. The justification tied to the acquisition and how the company was being integrated, but it still left me feeling like I’d been pulled into work that didn’t align with what was already known.
After a recruiter call, my process ran as a pretty clear sequence: a phone screen with the hiring side, then a demo-style round, and finally a peer/culture check. The phone call was short and to the point, focused on my background and whether I fit what they were looking for, with enough time at the end to ask questions. I then moved into a demo where I was given a technical task with a real deadline window. I had to explain both how I approached the work and why I chose my workflow, and it felt like they were watching my thinking as much as the result.
The interview process typically follows a structured sequence starting with a recruiter call, followed by a technical demo, and concluding with a culture check. Candidates noted that the overall timeline could be lengthy and sometimes ambiguous, particularly regarding project expectations and feedback timing.
Candidates are expected to complete a hands-on technical task, often involving Salesforce, where they build or demonstrate a project and explain their choices. This round is crucial for showcasing both technical skills and thought processes, with a focus on practical application rather than theoretical knowledge.
The interview process places significant weight on cultural alignment, with multiple rounds dedicated to assessing how candidates fit within the company's values and team dynamics. This includes casual interactions and discussions about work-life balance, which can overshadow technical evaluations.
Behavioral interviews focus on past experiences and how candidates handle various situations, emphasizing personality and soft skills over technical prowess. Candidates reported that these discussions were designed to feel comfortable and conversational, often leading to insights about the company's priorities.
Candidates are often required to present their completed projects to interviewers, which can be a challenging aspect of the process. The expectation is to articulate not only the technical execution but also the business rationale behind their work, which can lead to varying levels of success depending on communication clarity.
Candidate experiences can vary significantly, with some reporting positive, personable interactions while others encountered disorganized or unprepared interviewers. This variability can greatly influence overall impressions of the company and the likelihood of accepting an offer.
