Four candidates describe Otter.ai software engineer interviews that start with a recruiter call and a timed coding screen. They report graph, stack and array problems, and none of the four received an offer.
$183K
Avg. Base Comp
$240K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Across four candidate reports, the Otter.ai software engineer interview centers on timed algorithmic coding, and the screen is where the pressure shows up. All four candidates ended without an offer, so the reports are more useful as a view of where the process gets difficult than as a model of success.
Timed screens vary. One candidate had two LeetCode mediums in 30 minutes and finished only a stack-based problem. Another had a 45-minute CoderPad session on a medium-style problem and could not reach the optimal solution. A third, for a senior role, spent about 15 minutes of an hour-long screen on a project walkthrough before a LeetCode Hard on matrix island connectivity with a dynamic programming element.
Graph traversal is the clearest repeated theme. Two candidates mention island-style matrix problems, and one describes DFS and BFS questions, including counting islands, in later technical rounds. That candidate also reports a hiring-manager conversation, two technical rounds and a behavioral round. Another candidate heard secondhand of an onsite with coding, system design and behavioral parts, but did not reach it.
To prepare, practice graph and matrix traversal, stack and array problems under a strict timer, and aim for the optimal solution rather than the first working one. Also be ready to explain a past project concisely, because that discussion can cut into coding time.
Synthesized from 4 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 Otter.Ai process.
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 Otter.Ai
Given a 2D terrain array, calculate the total amount of trapped rainwater with O(n) time and O(n) space
| Question | |
|---|---|
| 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 | |
| Job Recommendation | |
| Rolling Bank Transactions | |
| Bagging vs Boosting | |
| Customer Orders | |
| Minimum Change | |
| Top 3 Users | |
| Scrambled Tickets | |
| 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 | |
| Size of Joins | |
| Upsell Transactions | |
| Download Facts | |
| Find Bigrams | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter call of about 20 to 30 minutes. It covered their background and past projects, and in one case the role requirements and salary expectations. Two candidates describe it as straightforward. It typically works as a fit check before the technical screen.
One candidate reports a 45-minute hiring-manager screen that was mostly experience, past projects and conceptual questions, leaving little time for coding. Another reports about 15 minutes of project walkthrough at the start of an hour-long coding screen. Be ready to summarize your work concisely so it does not eat into problem-solving time.
This is where candidates report the most difficulty. Reports include two LeetCode mediums in 30 minutes, a 45-minute CoderPad medium-style problem, and an hour-long screen with a LeetCode Hard on matrix island connectivity. Pacing and reaching an optimal solution were the main challenges, so practice under a timer.
One candidate reports reaching final rounds consisting of two technical interviews and one behavioral interview. The technical rounds focused on DFS and BFS graph problems at LeetCode-medium level, including counting islands. Another candidate heard secondhand of an onsite that may include coding, system design and behavioral parts, but did not reach it.
