Applied Intuition Software Engineer candidates report a recruiter screen, a live coding screen, and a multi-round onsite mixing LeetCode-style coding, design and career-focused conversations. Speed and clean, working code matter.
$179K
Avg. Base Comp
$232K
Avg. Total Comp
3-8 rounds
Typical Rounds
1 month
Process Length
Candidates describe an Applied Intuition Software Engineer loop that begins with a recruiter conversation, moves to a CoderPad-style technical screen, and then to an onsite or virtual onsite. Two candidates said recruiters set expectations early about working in the office five days a week, and one was told to expect 50 or more hours a week. Know where you stand on those before you apply.
The coding bar is the most consistent theme. Candidates report LeetCode medium-to-hard problems with a strong emphasis on finishing quickly and correctly. Reported problems include a graph question, an interval variant, Sudoku, Minesweeper, a lane merger algorithm, and an O(1) data structure for retrieving top-K logs. Others were more applied. These included parsing nested JSON from an API with max velocity and range follow-ups, decoding a CAN frame, and debugging existing code to get it working. Some candidates were asked to use C++ or to explain how they would clean up their code for production, so practice writing complete, tested solutions rather than outlines.
Design discussions reportedly lean toward the company's domain. One candidate was asked how they would design an offroad autonomous vehicle, with the focus on system-level tradeoffs, and another received autonomous driving learning materials in advance. Candidates report manager or lead conversations that walk through career history and motivation, so prepare a clear story about why you want to work on autonomous systems. Experiences with interviewers varied, from engaged and helpful to distracted. Most reports here ended without an offer, and one candidate declined an offer.
Synthesized from 29 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Applied Intuition process.
The part of this process I think about most is the behavioral interview, and I was not ready for how much of it there would be. It was with the hiring manager, and instead of going through a set of standard questions, he did a deep dive into my backstory starting from late high school. He kept asking why I made certain decisions, and I got the sense he was trying to understand my reasoning and gauge how well I'd fit the culture. Near the end he asked what would be the reason if I joined and left within six months. I hadn't prepared an answer for that.
The process began when the hiring manager reached out to me on LinkedIn. I had an informal chat with him where I mostly asked questions about the company, and then I spoke with the recruiter. The next step was a one-hour technical screen built around an algorithmic coding problem that required topological sort. The final round was a half-day onsite with two coding interviews, one system design interview, and the behavioral interview. One of the coding problems involved some math that I found tricky. The other was closer to problems I'd seen on LeetCode.
I did not receive an offer.
Prep tip from this candidate
Prepare a clear narrative of your background from late high school onward and be ready to explain the reasoning behind major decisions, since the hiring manager used the behavioral round to probe that thinking. Also practice math-heavy coding problems alongside graph problems like topological sort, because one onsite question leaned on math.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Applied Intuition
Design an end-to-end retraining and production pipeline for a machine learning model without dedicated infrastructure or support staff.
| Question | |
|---|---|
| Underpricing Algorithm | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Raining in Seattle | |
| Random SQL Sample | |
| String Shift | |
| Bagging vs Boosting | |
| Job Recommendation | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Minimum Change | |
| Top 3 Users | |
| Comments Histogram | |
| Find the First Non-Repeating Character in a String | |
| The Brackets Problem | |
| First Touch Attribution | |
| Flight Records | |
| Prime to N | |
| P-value to a Layman | |
| Level Of Rain Water In 2D Terrain | |
| Size of Joins | |
| Upsell Transactions | |
| Download Facts | |
| Find Bigrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter call covering their background, motivation for Applied Intuition and the role. Two say the recruiter raised in-office expectations early, and one was told to expect 50 or more hours per week. Expect this to be mostly behavioral rather than technical.
Candidates describe a live coding screen, often on CoderPad. Reported tasks include a medium LeetCode question with follow-ups, nested JSON parsing from an API, a graph problem, decoding a CAN frame, and debugging existing code. Interviewers reportedly care about working, clean code.
Onsite reports describe multiple coding rounds with medium-to-hard problems, sometimes with domain variations. Examples candidates mention include Minesweeper, Sudoku, interval problems, a lane merger algorithm and an O(1) top-K log structure. Some candidates say speed mattered a lot, and C++ was requested in some cases, so practice finishing and testing within the time limit.
Some candidates report a design round. One was asked how they would design an offroad autonomous vehicle, with the focus on product thinking and system-level tradeoffs. Another described the onsite as covering systems design and domain expertise. Be ready to reason about requirements and tradeoffs.
Several candidates report a conversation with a hiring manager, tech leads or leadership about their career path, achievements and why they want this role. One candidate did not advance over role fit. Prepare a coherent story and concrete reasons for your interest in autonomous vehicle software.
