Attentive Interview Experiences

8 results

• 

  Back-to-Back Phone Screens, Binary Search on Logs and a 3 Requests/Second API LimitAttentive · Software Engineer · Technical Screen · Sep 2026

  I had two phone screens back to back. Coding: binary search on logs, a variant of a problem that is already on the forum. The twist is that the log timestamps can be duplicated, and the time window I have to return is all inclusive, [start, end]. Also, start and end can fall outside the time range of the current dataset. System design: it was kind of like pulling data from a third party, and I fi…

• 

  Leveled Up to Senior Bar, Rejected After a Messy System DesignAttentive · Software Engineer · Onsite · Sep 2026

  Rejected

  I applied for SWE II. HR call - 2026-08-26 The questions were: How much do you know about Attentive? Are you actively interviewing right now? Do you have any offer deadlines? Do you need sponsorship? What are the compensation range you are targeting? Then they asked me to introduce myself. Are you able to talk about a feature or product that you work on like end-to-end or a zero-to-one product? W…

• 

  Two Onsite Rounds and an Unexpected Catalog DesignAttentive · Software Engineer · Onsite · Sep 2026

  Rejected

  I was contacted and invited to an onsite. Round 1 combined coding and system design. Round 2 included coding, system design, and behavioral questions. I felt that my system design and behavioral performance in Round 2 was poor, and I was ultimately rejected. There were not many interview reports about this company, so I summarized everything I could find. All the questions I received turned out t…

• 

  Attentive Software Engineer Interview Experience: dismissive managerial conversationAttentive · Software Engineer · HR Screen · Aug 2026

  After a recruiter screening, I had a managerial round. I received the job description, but the details about the structure and expectations turned out to be wrong. Before the questions even began, the interaction felt uncomfortable because the tone did not feel respectful. The conversation came across as skeptical and dismissive. My answers were treated as though they had been discounted from the…

• 

  Attentive Software Engineer Interview Experience: role closed after the phone screenAttentive · Software Engineer · Aug 2026

  I started with an initial phone screen. After that, I expected a fairly standard sequence: a second round with coding and system design, a third round with more of the same assessment, and then a meeting with the team. The role closed before the process could get that far, so I never reached those later rounds. It left me feeling as though the interview process was just about to expand, and then…

• 

  Account Executive interview at Attentive: interview experienceAttentive · Account Executive · Jul 2026

  No response

  The intended process was recruiter screen, hiring-manager round, VP screen, and panel presentation, but my own process ended after the hiring-manager call. I did not reach the later stages. That manager interaction threw me off. She did not build rapport and came across as stand-offish, as though she was checking boxes. The questions were not the problem, but the call felt like a prove-it-fast ex…

• 

  Coding and System Design Blended Into One 75-Minute ScreenAttentive · Software Engineer · New Grad · Technical Screen · Apr 2026

  It was 75 minutes long. They said it would be coding + system design, but in practice the two were mixed together, and the questions were pretty scattered and casual. The last 5 minutes were reverse behavioral questions, where I got to ask them things. The problem wasn't quite like a LeetCode problem — they didn't clearly spell out what the input was. They wanted me to design it myself and then j…

• 

  Nailed Every Round, Still RejectedAttentive · Software Engineer · New Grad · Onsite · Apr 2026

  Rejected

  This was the last round — three interviews back to back: coding + debug + HM. Coding: the interviewer had a straight face the whole time. Gave me LeetCode 1209, first simplified k down to k=3, and I solved it fast — covered edge cases and asked all the clarifying questions. The interviewer saw there was a lot of time left and started following up: first asked how to change it back from 3 to gener…