Nextiva Staff Software Engineer interview questions

I had a really disappointing experience interviewing with Nextiva, and I would suggest not wasting your time as the process lacked structure and the interviewers seemed underqualified. The first round was a DSA round with two coding questions. When I asked for a small clarification, the interviewer simply said, “read the question again,” which made it clear he wasn’t confident about the question himself and seemed quite junior. Still, I solved both problems and provided fully working code. The next round was supposed to be an LLD (Low-Level Design) interview, but it turned into a time sink. The interviewer joined almost 5 minutes late and then spent nearly 30 minutes discussing a role mismatch with the recruiter — I had applied for Staff Software Engineer, but the interview was scheduled for Senior Software Engineer. Once the round finally began, he gave me one LLD question which I solved quickly. Then he moved on to another design problem based on browser history, which I also solved. However, he wanted me to handle the override scenario as well. I proposed a doubly linked list (or a graph for multi-branching scenarios) as the most suitable data structure, explaining that it supports O(1) back/forward navigation and models real-world browser history much better than a simple LIFO stack. Even after I explained my reasoning and demonstrated understanding, the interviewer kept re-explaining the same scenario multiple times. In the end, he insisted I use a stack because it was “simpler to implement.” It felt like he wasn’t evaluating problem-solving depth but rather expecting a textbook answer. To add to that, the interviewer appeared technically weak, extended a 1-hour session into almost 2 hours, and I had to follow up multiple times just to get feedback. Overall, the experience was poorly organized, time-inefficient, and lacked meaningful technical depth.