Yext software engineer candidates describe a process that mixes DSA, graph problems and code debugging, usually ending with a behavioral conversation. Here is what candidate reports say about the rounds, questions and prep.
$144K
Avg. Base Comp
$169K
Avg. Total Comp
3-5 rounds
Typical Rounds
2-5 weeks
Process Length
If you are preparing for a Yext software engineer interview, plan for more than standard algorithm practice. Across these candidate reports, debugging existing code comes up in nearly every account, alongside DSA, and it often gets its own round. Candidates describe fixing bugs in a banking application and in a Conway's Game of Life simulation. One candidate described the banking task as finding four separate issues in the code.
Graph and grid problems are the other recurring theme. Several candidates mention Minesweeper-style or mines-in-a-matrix questions, which call for DFS, BFS or flood fill. Others describe a standard graph-based DSA question. One SWE II candidate described a top-10 leaderboard task that pulled data from an API. A few candidates also describe a design discussion, either a live system design round or a whiteboard high-level design.
Formats vary by level. Reports range from three to five rounds, and some candidates describe an online assessment first. The last stage is usually a behavioral conversation with a hiring manager or director. One candidate was asked about a characteristic they admired in a team member.
Candidates repeatedly say interviewers were supportive and wanted to hear reasoning, so practice narrating your thinking while you read or write code. Outcomes were mixed. Most reports end in offers, but some candidates did not advance after partial progress in debugging rounds. Time yourself on debugging exercises and on grid-traversal problems.
Synthesized from 12 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 Yext 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 Yext
Compute the expected time for the stranded miner to reach safety given the path probabilities and travel times
| Question | |
|---|---|
| Dijkstra implementation | |
| Sales Leaderboard | |
| Client Solution Pushback | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Largest Salary by Department | |
| Top 5 Turnover Risk | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Prime to N | |
| Minimum Change | |
| Upsell Transactions | |
| Top 3 Users | |
| Find the Missing Number | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| Rectangle Overlap | |
| Scrambled Tickets | |
| Bagging vs Boosting | |
| Flight Records | |
| The Brackets Problem |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with an online coding assessment, often a graph-based DSA or timed frontend problem. One candidate applied through an employee referral, and another says any programming language was allowed. Whether you get this step may vary by level and hiring channel.
Several candidates describe a first technical round that pairs a coding problem with a debugging task. Reported debugging tasks include a banking application with several bugs. Candidates typically say interviewers encouraged them to talk through their reasoning. Coding problems reported include Minesweeper-style grids and DFS/BFS traversal.
Some candidates report one or two more technical rounds that split between coding and debugging. Reported examples include a Game of Life simulation, graph problems, and an API-based top-10 leaderboard task. Round counts vary by candidate, from three to five rounds in total.
A few candidates describe a design component. One candidate had a live system design round, and others had a whiteboard high-level or system design discussion. It may not appear in every loop, so check with your recruiter which rounds to expect.
Candidates commonly report a behavioral round last, with a hiring manager or director. Reported topics include background, team fit and a characteristic admired in a teammate. One candidate also mentions a brief HR follow-up after it.
