← Back to Directory

Applied Intuition interview notes, page 2 of 7

Mid-sized

Most of these Applied Intuition write-ups come from Software Engineers (50), then Machine Learning Engineers (12) and Mobile Engineers (2). The most reported rounds are the technical phone screen (42), the system design round (14), the hiring manager screen (4) and the recruiter screen (2).

64 interview notes · updated Jul 2026

Applied Intuition·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Applied Intuition focused entirely on building a distributed job scheduler from scratch. The scope was massive and they clearly wanted to see how you'd prioritize under pressure.
  • Design a scalable job scheduler that supports immediate and delayed execution, recurring jobs, priorities, retries with backoff, and job dependencies.
  • What are the tradeoffs between at-least-once and exactly-once execution semantics in a distributed job system, and how do you handle idempotency and deduplication?
  • How would you design multi-tenant isolation and horizontal scaling to handle high job throughput across tenants?
  • What strategies would you use for multi-region deployment of a job scheduler, considering persistence and durability?
  • How would you approach monitoring, alerting, and failure handling for a job scheduler at scale?

“This question ate up the whole session.”

View Post

Applied Intuition·Software Engineer·Onsite - System Design / Architecture

May 2026
Applied Intuition system design round, one meaty question about building a timeout detector for a job scheduler. Spent most of the time on edge cases and data structure tradeoffs, which I think is where they actually wanted to see me go.
  • Design and implement an event-timeout detector for a job scheduler. You get a global timeout T and a stream of events with an ID, a type (start, end, or ping), and a timestamp. An event times out if it started but never ended and the time since its last update exceeds T. Pings reset the update clock, ends remove the event. Implement process(event) and get_timed_out(now_ts). Also cover edge cases: duplicates, out-of-order events, events with no prior start, multiple starts, and zero or negative timeouts. Analyze time and space complexity.

“This one took a while to get my footing on.”

View Post

Applied Intuition·Software Engineer·Recruiter / HR Screen

May 2026
Applied Intuition SWE screen, basically just the intro and motivation round. Nothing technical, just them trying to figure out who you are and why you want to be there.
  • Walk me through your background, current role, and a project or two you're proud of.
  • Why are you looking to leave your current company, and what specifically draws you to this team?
  • How does your personal motivation align with what this team is trying to accomplish, and what do you hope to learn or contribute here?

“I rambled a bit here.”

View Post

Applied Intuition·Software Engineer·Technical Phone Screen

May 2026
Applied Intuition SWE interview with a real-time systems coding problem. The question had enough edge cases baked in that it felt less like a coding exercise and more like a mini design discussion.
  • Simulate a real-world button event stream where each button has a binary state. On a press-down event, record a timestamp. On release, compute the elapsed duration and classify the press as 'long' or 'short' based on a configurable threshold. Handle edge cases like duplicate press or duplicate release events and explain your chosen behavior.

“The core logic wasn't bad, hashmap keyed by button ID storing press timestamps, look it up on release and diff against current time.”

View Post

Applied Intuition·Software Engineer·Technical Phone Screen

May 2026
Applied Intuition coding round for a software engineer role. The main problem was building a protobuf-style schema parser, which sounds manageable until you get into the recursive size resolution for nested message types.
  • Build a parser that reads a string defining one or more typed messages (each with named fields), then implement a function to return the total byte size of a given message and another to return the type of a specific field. Primitive types have fixed sizes, and fields can reference other defined messages, so size calculation must be recursive.

“The basic parsing wasn't bad.”

View Post

Applied Intuition·Software Engineer·Hiring Manager Screen

May 2026
Resume walkthrough interview for a Software Engineer role at Applied Intuition. The whole thing was basically a chronological interrogation of every decision I'd made since picking a university, and they weren't shy about poking holes wherever they felt like it.
  • Walk me through your entire resume from the beginning, starting with why you chose your university, and for each role explain why you joined, what you worked on, what you learned, and why you left.

“This sounds manageable until you're 20 minutes in and they interrupt to ask why you stayed at a company for only 14 months.”

View Post

Applied Intuition·Software Engineer·Technical Phone Screen

May 2026
Applied Intuition's software engineer coding round had one question: a KV store with nested transactions. The 45-minute window was tighter than I expected, and parsing the input ate up way more time than the actual logic.
  • Design and implement a key-value store that supports nested transactions, including commit and rollback operations.

“The core idea is a stack of transaction layers, pretty standard if you've seen this before.”

View Post

Applied Intuition·Software Engineer·Technical Phone Screen

May 2026
Applied gave me a system design question for a Software Engineer role that was more algorithmic than I expected. It was a single technical problem but it had a lot of layers once you started pulling on it.
  • Design a monitoring component for many concurrent simulations where each simulation emits start, ping, and end events with timestamps. You need to process events one by one and efficiently detect which simulations have timed out since the last event, where a timeout means no activity for longer than a given threshold T. Describe your data structures and key operations, targeting close to O(log n) per event.

“This one took me a while to even see the core difficulty.”

View Post

Applied Intuition·Software Engineer·Hiring Manager Screen

May 2026
Interviewed for a software engineer role at Applied Intuition. One question in particular stuck with me after, the kind that sounds like a performance review disguised as an interview question.
  • If you joined and were put on a performance improvement plan within your first six months, what do you think would be the most likely reason? What warning signs would you look for early on, and how would you get ahead of the risk?

“This one stopped me cold for a second.”

View Post

Applied Intuition·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Applied Intuition where they basically handed me one big open-ended prompt and let me run with it for the whole session. Dense question, lots of surface area, and I definitely underestimated how deep they wanted to go on the operational side.
  • Walk me through a recent project you led from start to finish: the problem, requirements (functional and non-functional), architecture choices, key trade-offs, scaling, data model, dependencies, observability, deployments, and how you measured success. Also describe a significant failure or bottleneck you hit, how you debugged it, and what you'd do differently in a second version.

“This is basically five questions stitched into one.”

View Post