Applied Intuition interview notes, page 5 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·Machine Learning Engineer·Technical Phone Screen

Jun 2026

Applied Intuition ML engineer interview with a deep technical question on Transformer attention masking. Single question but it went pretty far into implementation details, edge cases, and debugging, more thorough than I expected for what felt like a phone screen.

Implement attention masking for an autoregressive Transformer that handles variable-length sequences with padding. Build both a causal mask and a padding mask, show how to combine them, and explain what bugs look like in practice and how you'd test for them.

“This one went deeper than I was ready for.”

View Post

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

Jun 2026

Applied Intuition system design round, focused entirely on building a task scheduler from scratch. The discussion went pretty deep into data structures and extensibility, which I wasn't fully prepped for.

Design a task scheduler with two methods: one to add a task and one to run all scheduled tasks. Walk through your choice of data structure, execution semantics, and how you'd extend it to support concurrency, retries, and cancellation.

“Started with a basic queue and FIFO execution, which felt right but they pushed back pretty fast asking why not a priority queue.”

View Post

Applied Intuition·Software Engineer·Take-home Assignment

Jun 2026

Applied gave me a take-home style coding problem for a Software Engineer role. It was a physics simulation question, which I did not see coming at all. Pretty niche stuff for a typical SWE interview.

Build a multi-agent 2D collision simulator where each agent moves using a unicycle motion model with constant speed and turn rate. Advance all agents in fixed timesteps using forward Euler integration and report the first timestep at which any two agents overlap, or report no collision if none occurs within the simulation horizon.

“I had not touched unicycle kinematics since a robotics elective years ago and the muscle memory was not there.”

View Post

Applied Intuition·Software Engineer·Technical Phone Screen

Jun 2026

Interviewed for a software engineering role at Applied Intuition and got a coding question that was a twist on a classic LeetCode problem. The variation kept me on my toes more than I expected.

Given a file system represented as a list of directory strings, find all duplicate files. Instead of comparing file contents, use file size as the basis for identifying duplicates.

“I knew the original problem so my first instinct was to group by content hash, then I had to mentally recalibrate because they wanted size-based grouping instead.”

View Post

Applied Intuition·Software Engineer·Technical Phone Screen

Jun 2026

Applied Intuition SWE interview with a geometry-heavy coding problem that looked deceptively clean on the surface. The edge cases are where it gets messy.

Given a list of 2D line segments (each defined by 2 or more floating-point points), merge any segments that are collinear AND whose projections along the shared line overlap. The output should preserve all original points, sorted along the line direction.

“The base case clicked fast for me: group by slope and intercept, check overlap, merge.”

View Post

Applied Intuition·Machine Learning Engineer·Technical Phone Screen

Jun 2026

Applied Intuition ML engineer interview, technical phone screen focused entirely on Transformer internals. One meaty question about positional encodings that took up basically the whole session.

Implement positional encodings for a Transformer language model. Walk through sinusoidal vs learned approaches, write PyTorch code to compute and add them to token embeddings, explain the math and tensor shapes, integrate into the full model, and describe what breaks if you skip positional info entirely and how you'd verify the fix.

“This was a lot to unpack in one question.”

View Post

Applied Intuition·Software Engineer·Technical Phone Screen

Jun 2026

Applied Intuition coding round, one meaty design-and-implement question about a transactional key-value store. The problem sounds manageable until you get into nested transactions and the edge cases start piling up.

Build an in-memory key-value store that supports nested transactions with SET, RETURN (read), BEGIN, APPLY (commit to parent), and DISCARD (rollback). Reads and writes should reflect the most recent value in the current transaction context. Walk through your data structures, API design, time/space complexity, and edge cases like reading an unset key or calling APPLY with no active transaction.

“My first instinct was a stack of hashmaps, one per transaction layer, and reads walk up the stack until they find the key.”

View Post

Applied Intuition·Software Engineer·Technical Phone Screen

Jun 2026

Interviewed for a software engineering role at Applied Intuition and got a file system problem that looked straightforward until the follow-ups started stacking up.

Given a file system, find all groups of duplicate files based on their content.

“I knew the general shape of the answer: group by file size first, then hash the contents to confirm duplicates.”

View Post

Applied Intuition·Software Engineer·Recruiter / HR Screen

Jun 2026

Screened for a software engineer role at Applied Intuition. Pretty standard recruiter-style conversation, mostly background and motivation questions, nothing technical.

What is your reason for looking for a new job right now?
What drew you to Applied Intuition specifically?
What are you currently working on and what technologies are you using?
Why did you go to graduate school instead of going straight into industry after your undergrad?

“Pretty routine but I always fumble this a little.”

View Post

Applied Intuition·Software Engineer·Technical Phone Screen

Jun 2026

Applied Intuition technical phone screen for a software engineer role. One meaty coding question about schema validation on nested objects, and they really wanted to see how you handle the edge cases, not just the happy path.

Write a helper function called validate(object, required_style) that checks whether a possibly nested object conforms to a given schema. The function should return a boolean plus an explanation when invalid, including the offending path and the reason (missing key, wrong type, etc.). You also need to decide how to handle extra fields, nulls, and arrays, and demonstrate it on a concrete example with fields like name, age, school, and nested attributes.

“This looked like a straightforward type-checker until I started thinking about nested objects.”

View Post