Yext Software Engineer II, Full Stack interview questions
based on 1 rating - Updated 1 Apr 2025
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
100%
Applied online
Applied online
Interview search
1 interviews
Yext interviews FAQs
Software Engineer II, Full Stack applicants have rated the interview process at Yext with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 70.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer II, Full Stack roles take an average of 60 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Yext overall takes an average of 20 days.
Common stages of the interview process at Yext as a Software Engineer II, Full Stack according to 1 Glassdoor interviews include:
One on one interview: 50%
Phone interview: 50%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 months. I interviewed at Yext
Interview
I applied online and received the Online Assessment (OA) link on February 6, 2025. The OA consisted of one easy and two medium-level DSA questions.
Round 1 (February 10, 2025) - Debugging + Coding (1 hour)
This round was divided into two sections:
Debugging: A banking application was provided, and I had to debug four issues. With some hints from the interviewer, I was able to solve all four.
Coding: A Minesweeper-like problem was given, which could be solved using the flood-fill algorithm (either via DFS or BFS). I implemented the solution successfully and cleared the round.
Round 2 (March 10 & March 13, 2025) - Debugging (1 hour) + Coding (1 hour)
This round was conducted in two parts on different days.
Debugging Round (March 10, 2025): The problem was a Game of Life simulation. Despite my best efforts, I could only fix the logical mistakes but struggled with other parts. Unfortunately, the interviewer didn't provide much guidance.
Coding Round (March 13, 2025): The task was to print the top 10 leaderboard of a game, where the required data had to be retrieved from an API provided by the interviewer. This round went well.
Final Outcome
I didn't receive a call after this round, so I assume I wasn't selected. Overall, it was a good experience, and the questions were interesting, especially the API-based leaderboard problem.
Interview questions [1]
Question 1
Graph related problems, Game of Life Simulation, Leaderboard Generation