Applied Intuition Software Engineer Interview Guide

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.