Yext Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 292 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Yext.
Yext
Software Engineer
Entry Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Coding Technical
First up was a recruiter chat to go over my resume, what I'm looking for role-wise, and my interest in the company. Then, the first real round was a 1-hour session with an engineer, tackling a debugging task and a LeetCode-style coding challenge.
Confirmed questions5 questions
- Can you walk me through your background and resume?
- What are your areas of interest?
- Why are you interested in Yext?
Yext
Software Engineer
Mid Average Positive experience No offer 3 rounds
Interview process
Take home Technical screen Technical screen
Interview formats
Coding Technical
I applied online and got an OA link on Feb 6, 2025, which had 1 easy and 2 medium DSA questions. Round 1 on Feb 10, 2025 (1 hour) was about debugging a banking app (4 issues, I fixed them with hints) and coding a Minesweeper-like problem using flood-fill (DFS/BFS, I did this successfully). Round 2 was split on March 10 & March 13, 2025. The first part on March 10 was 1 hour of debugging Game of Life, where I struggled and didn't get much help. The second part on March 13 was 1 hour of coding to get a game's top 10 leaderboard from an API, which went well. I didn't hear back after Round 2, so I guess I didn't make it. It was a good experience though, and the questions were cool, especially the API leaderboard one.
Confirmed questions3 questions
- Graph related problems
- Game of Life Simulation
- Leaderboard Generation
Yext
Software Engineer
Intern Average Positive experience Accept offer 3 rounds
Interview process
Technical screen Phone screen Recruiter call
Interview formats
Coding Technical Behavioral
The interview process started with an in-person round that included a LeetCode-style question and a debugging question, lasting about 45 minutes. The second round was a virtual phone screen where the question was more practical, focusing on problem-solving approach and code quality rather than difficulty, taking around 45 minutes plus 15 minutes for follow-up questions. The third round was a 30-minute behavioral interview, mainly consisting of answering questions from a list. Yext provided very quick feedback after each stage and moved me through the entire process swiftly.
Confirmed questions1 question
- Could you tell me about your personality?
Yext Software Engineer Interview Questions
Quoted word for word from Yext interview reports.
“Find all cousin nodes to a target node in a tree, ensuring they don't have the same parent as the target node.”
Read reports →“Given a 2D array representing a minefield, count the total detonated cells, where a 1 signifies a bomb that detonates surrounding cells”
Read reports →“Can you determine if a given string can be formed by concatenating words from a provided dictionary?”
Read reports →“Regarding Python data structures, what is the effect of assigning one object to another like "object1 = object2"?”
Read reports →“Given an array of integers (numbers), like [1, 2, 3], and a target sum number, such as 5, return an array of elements that add up to that target sum number.”
Read report →“What is the most efficient method for traversing a 2D array in a snake-like pattern?”
Read report →“For the Boggle Game word checker, given a 2D character matrix, how would you check if a given word exists by moving up, down, left, or right?”
Read report →“Find 3 bugs in some code related to Tree Traversal using recursion instead of iteration”
Read report →“Can you form a target string by traversing a character matrix in a snake-like pattern (up, down, left, right), ensuring no cell is visited more than once?”
Read report →Formats, difficulty and experience
Across all 292 Yext interview reports.