Real, anonymous reports from people who interviewed for Software Engineer at Attentive, newest first and distilled into what to expect across the loop.
After a recruiter call, I ended up going through an unusually long gauntlet—six rounds total—because they were trying to fill only one software engineering opening. The structure stayed pretty consistent across the process: two coding rounds, two system design rounds, and two behavioral rounds. I felt like I performed well throughout, and it was frustrating because the recruiter kept communications responsive.
I started with a recruiter call, then moved into a sequence of conversations with people across the organization: a team member follow-up, a hiring manager conversation, and even a sales-team touchpoint. Those later calls focused heavily on how I handled different situations—what I’d do and how I’d think through scenarios.
The interview process typically consists of six rounds, including two coding rounds, two system design rounds, and two behavioral rounds, providing a comprehensive evaluation of both technical and interpersonal skills.
Candidates can expect a focus on both SQL and Python during technical interviews, with an emphasis on problem-solving and system architecture relevant to the company's needs.
Behavioral interviews are significant, with questions aimed at assessing cultural fit and how candidates handle various scenarios, often involving cross-functional team members.
The interview process includes a final presentation round where candidates demonstrate their ability to communicate effectively, often in front of multiple stakeholders.
Candidates have reported mixed experiences with recruiters, ranging from responsive and helpful to disorganized and unprofessional, which can significantly impact the overall impression of the process.
Candidates noted that despite performing well, decisions can hinge on specific team matching or role fit, which may feel frustrating if not clearly communicated throughout the process.