← Back to Directory

Attentive

Mid-sized

Screna has 4 Attentive interview write-ups. The most reported round is the system design round (2).

4 interview notes · updated Jun 2026

Attentive·Software Engineer·Technical Phone Screen

May 2026
Coding round at Attentive for a software engineer role. The interview was heavy on a single sliding window problem but then pivoted hard into production and scaling follow-ups that I was not expecting at all.
  • Given an array of positive integers and a target value, find the minimal length of a contiguous subarray whose sum is greater than or equal to the target. Return 0 if no such subarray exists.
  • The function you wrote is deployed to production and it's crashing. Walk me through how you'd troubleshoot it.
  • The input to this function is being read from S3 and it's too large to fit in memory. How do you adapt your solution?
  • Write pseudocode for a 2D matrix variant of the problem: find the smallest sub-rectangle whose sum is greater than or equal to the target. Also discuss how you'd handle crashes in this version.

“They started me with a simplified version where the target was fixed at 3, which felt easy enough.”

View Post

Attentive·Software Engineer·Hiring Manager Screen

May 2026
Behavioral round with the hiring manager at Attentive for a Software Engineer role, split into three blocks: standard behavioral questions, a deep project dive, and a future goals conversation. The project block apparently runs longer than you'd expect, so come ready to defend your decisions in detail.
  • Walk me through a project from your resume. What technical decisions did you make, what trade-offs did you consider, and what was your specific contribution?
  • Tell me about a time you dealt with significant ambiguity on a project. How did you navigate it?
  • Describe a conflict you had with a teammate or stakeholder. What happened and how did you resolve it?
  • Where do you want to be in the next one to three years, and why does this team fit that path?
  • Tell me about a time you had a measurable impact on a project or product. How did you know it mattered?

“This block ran way longer than I expected.”

View Post

Attentive·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Attentive for a software engineer role. The problem started as a straightforward messaging service and then shifted mid-interview into a polling/scheduling design, which kept things interesting but also a bit chaotic.
  • Design and implement a message broadcasting service given a mapping of companies to subscribers and a log of messages with timestamps. How do you route each company's messages to its subscribers?
  • The interviewer introduced a current_time parameter mid-problem. Rework the approach into a polling-based system that, on each tick, broadcasts only the logs whose timestamp falls within the current window.
  • How would you extend the polling approach to support a time range [t1, t2] instead of a single current_time value?
  • Design the API surface for this broadcasting service, covering operations like broadcast, subscribe, unsubscribe, and schedule.
  • What storage model would you choose for the message logs and subscriber lists, and why?
  • Design a scheduling API that fires broadcasts at specified future times. How does the scheduler know when to execute, and how do you handle failures or missed windows?

“Felt pretty comfortable at first, it's basically a fanout problem.”

View Post

Attentive·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Attentive for a software engineer role. The problem was a catalog service with some genuinely tricky constraints around admin overrides and multi-partner ingestion. More moving parts than I expected going in.
  • Design a catalog service that ingests product data from multiple partner sites (each with different formats and update schedules), stores and exposes that data via an API, and allows admins to override any partner-supplied attribute such that those overrides survive re-ingestion.

“I spent the first few minutes just trying to untangle the override requirement because it's the part that actually makes this hard.”

View Post