
Nextiva Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Nextiva.
Software Engineer
I had a pretty bad time interviewing with Nextiva, honestly, I'd say skip it. The whole thing felt all over the place and the people interviewing me didn't seem very knowledgeable. First up was a coding round with two problems. I asked for a tiny bit of clarification and the interviewer just said to 'read the question again,' which felt like they weren't sure about it themselves and maybe a bit junior. Anyway, I got both problems done and had working code. The next part was meant to be LLD, but it just dragged on. The interviewer was late by about 5 minutes. Then they spent almost half an hour talking about how my role might not be a fit, even though I applied for Staff and the interview was set up for Senior. Once we finally got going, they threw one LLD question at me, which I finished fast. Then another design question about browser history came up, and I solved that too. The catch was they wanted me to handle the override situation. I suggested a doubly linked list (or a graph if multiple branches were a thing) because it lets you go back and forth easily in O(1) time and is a better model for browser history than a basic stack. Even after I explained why and showed I got it, the interviewer kept repeating the same thing. They ended up pushing for a stack because it was 'easier to code.' It felt like they weren't looking for deep problem-solving, just a textbook answer. On top of that, the interviewer seemed weak technically, turned a 1-hour chat into nearly 2 hours, and I had to chase them multiple times for any feedback. All in all, it was disorganized, a waste of time, and lacked any real technical depth.
- Two medium LeetCode-style problems
- Low-level design for a task manager
- Low-level design for browser history
Senior Software Engineer
So, I went through 4 rounds of interviews: 3 technical and 1 managerial. After I passed those, the HR mentioned they had another candidate and kept delaying the offer with strange excuses. On the day an offer was expected, they fed me lies about slow approval processes. Then, suddenly, they claimed they couldn't extend an offer because the position was on hold. Ironically, a few months later, I saw the same role still advertised. It seems like they interview many candidates, and after you pass, the HR just picks one randomly and ghosts the rest. I felt deceived and want to warn others.
- What are your core Javascript concepts?
- Tell me about your experience with React.
- Can you walk me through how you'd approach solving problems?
Software Engineer
It was a bit challenging, but a good interview. They focused on algorithms and problems related to everyday programming tasks. It's important to have a solid understanding of your stack's core. They really test your knowledge of your stack in depth.
- Can you solve problems related to daily programming activities using algorithms?
- How well do you know the core of your technology stack?
- Demonstrate your ability to handle various architectural challenges.
Nextiva Software Engineer Interview Questions
Quoted word for word from Nextiva interview reports.
“Implement browser history using a stack”
Read reports →“Design a solution for browser history overrides”
Read reports →“Can you define SOLID and explain its principles?”
Read reports →“How would you design a todo list application that includes due dates?”
Read reports →“Can you speak English?”
Read report →“Could you discuss best practices for Object-Oriented Programming and give examples?”
Read report →“Did you use Java?”
Read report →“Did you use Spring?”
Read report →“What are your core Javascript concepts?”
Read report →Formats, difficulty and experience
Across all 11 Nextiva interview reports.