Real, anonymous reports from people who interviewed for Software Engineer at Abnormal Security, newest first and distilled into what to expect across the loop.
Get your personalized Abnormal Security 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 call, the process moved pretty quickly. I eventually met the hiring manager, and it felt more like a structured conversation than a checklist: they walked me through what the company did and what my day-to-day might look like. They also asked about my background and why I was switching, including how I’d used AI in my day-to-day work.
A week or so later I did a technical screen that was AI-assisted. I was handed a large codebase and a feature requirement. The expectation was that I’d understand the existing structure using AI help, then implement the feature with AI assistance and add tests. The overall vibe from everyone I spoke with was welcoming, and even though the task was substantial, it didn’t feel adversarial.
3 months ago
Average Negative United States
My process started with a take-home assignment that ended up being the hardest part of everything. I was asked to build a file-upload or file-storage style application with deduplication and search, and I had to lean on AI to get through the work. In my case, AI tooling was allowed but I wasn’t given everything needed—at least not in the moment—so I had to rely on my own setup. I also had to record how I used AI while developing.
Once I submitted, I moved into a review round where the conversation turned into architecture and reasoning. They wanted me to explain the design decisions and how AI played into the implementation. What really threw me off was a follow-up feature request: they asked to extend the take-home so the app could search the file content. I had already spent a lot of time in the discussion, and I didn’t have enough time to fully implement that added requirement.
6 months ago
Average Positive New York, NY
My loop started with a recruiter screen and then moved into technical interviews that were different from the usual LeetCode framing. I remember being…
6 months ago
Average Negative London, England
My loop started with a recruiter screen and then shifted into technical evaluation. I expected it to lean backend-focused, without classic LeetCode-st…
> 1 year
Average Negative Bengaluru
After a recruiter phone call, I moved into a hiring manager conversation and then two technical rounds. The process felt straightforward while it was …
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
Recruiter & Hiring Manager Interaction
The initial stages typically involve a recruiter screen followed by a conversation with the hiring manager, focusing on the candidate's background and fit for the role. Candidates noted varying levels of professionalism and engagement during these discussions, which set the tone for the rest of the process.
Recruiter callHiring managerCandidate fit
Technical Evaluation Structure
Candidates experienced a mix of technical rounds that emphasized practical coding skills rather than traditional algorithm questions, often involving real-world scenarios and AI tools. However, there were inconsistencies in expectations, with some candidates feeling unprepared for the specific technologies or formats used during evaluations.
Technical screenReal-world codingAI tools
Project and System Design Discussions
Later rounds often included discussions around past projects and system design, where candidates were expected to articulate their design decisions and enhancements. Some candidates found these discussions challenging due to misalignment with their actual work experiences or the expectations set during earlier stages.
Project discussionSystem designDesign decisions
Communication and Feedback
Candidates reported mixed experiences regarding communication throughout the interview process, with some feeling well-informed while others faced delays and a lack of closure after interviews. The absence of constructive feedback post-interview was a common frustration.
CommunicationFeedbackClosure
Overall Process Experience
The interview process was described as lengthy and at times chaotic, with scheduling issues and unclear expectations contributing to a stressful atmosphere. Candidates noted that the overall experience could feel more adversarial than collaborative, impacting their perception of the company culture.
Process lengthChaosCompany culture
Candidate Expectations vs. Reality
Several candidates expressed disappointment when the actual interview content did not align with their expectations based on initial communications. This mismatch often led to confusion and a feeling of being evaluated on criteria that were not clearly communicated.