← Back to Directory

Attentive interview notes, page 2 of 2

Mid-sized

Screna has 12 Attentive interview write-ups. The most reported round is the technical phone screen (8).

12 interview notes · updated Jul 2026

Attentive·Software Engineer·Onsite - System Design / Architecture

Jul 2026
Attentive software engineer interview with a meaty system design question built around a backend worker service. The whole thing was one extended scenario that kept layering on constraints, which I wasn't fully expecting.
  • A backend worker reads large objects from object storage, applies a string transformation, and writes the result back. Workers have 1 GB of memory and a 10-minute timeout, but some inputs are several GB. Jobs are crashing in production. Walk through how you'd triage the crashes and figure out whether the root cause is malformed input, a bug, memory pressure, timeout, or a dependency problem.
  • How would you redesign the service to process very large input objects without loading the entire object into memory at once?
  • When processing input in chunks, how do you ensure correctness if a character run spans the boundary between two chunks?
  • What observability, testing, and recovery mechanisms would you add so that failures like this are easier to catch and fix going forward?

“This part I actually felt okay about.”

View Post

Attentive·Data Scientist·Technical Phone Screen

Jul 2026
Attentive DS interview that was basically a live incident triage case. They dropped a real-sounding SMS delivery degradation scenario on me and wanted the whole nine yards: metrics, slicing, hypotheses, experiment design, rollback. Pretty intense for a single session.
  • US SMS delivery rates dropped ~6.5 percentage points starting at a specific time window, affecting two major carriers but not Canada or UK. A new link-shortener domain and updated carrier registrations had just rolled out. Walk through how you'd triage this.
  • How would you slice the data to isolate where the delivery drop is coming from?
  • What artifact or system-level checks would you do before jumping to statistical analysis?
  • How would you design an experiment to test whether the new link-shortener domain caused the drop?
  • What would your rollback plan look like, and what evidence threshold would you need before declaring the incident resolved?

“This was the whole interview basically.”

View Post