Nextiva Interview Questions
& Process

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.

The interview process was handled really poorly. I went through 3 rounds with interviewers who were managers and senior managers. Nobody used their cameras, which is super unexpected from management. In the third interview, the interviewer kept cutting me off and wouldn't let me finish a single sentence, not even for 30 seconds. After trying for 10 minutes to get a word in, I just lost it and said I didn't want to continue and was okay with a negative outcome because I couldn't deal with the disrespect. My self-respect is more important. The interviewer didn't even apologize, just blamed internet issues. I feel bad for the people who report to him. They also rescheduled interviews last minute without checking if I was free and expected me to just be there. The whole experience felt toxic.

So, the whole process had like 3 technical rounds, not counting the HR bit. They were all about Java, Data Structures and Algorithms (DSA), basic system design stuff, and how to tackle real problems. Round 1 was heavy on Core Java, DSA, and SQL. We did a DSA problem: finding the max product of three numbers in an array. Then, some Java questions on Collection Framework, differences between List/Set/Queue, JVM/JRE/JDK, and Java 8 features. Also coded Binary Search and its time complexity. For SQL, it was writing a query for the 3rd highest salary. Round 2 focused on DSA, Java internals, and a bit of culture fit. LeetCode problems included 'Longest Substring Without Repeating Characters' (they wanted printing and time complexity analysis too) and 'Balanced Parentheses' where I managed to use O(1) space, which they liked. More Java questions popped up: Iterable vs Collection, how HashMap works (again!), multithreading, and garbage collection. We also chatted about some Linux commands and my college life at NIT Agartala, Tripura's culture, and local languages. Round 3 was more managerial and conceptual. We coded the Fibonacci Series and discussed Java OOPs concepts like Constructor vs Interface, and ArrayList vs LinkedList. Other topics covered were REST API basics, Spring Boot intro, backend scenarios, and role expectations plus culture fit questions. It was a good experience overall, the interviewers were really nice and interested in both tech and me as a person.

Got contacted by a recruiter, who then set up my first interview with another tech lead. That interview involved a system design task for a room booking service that was supposed to take 30 minutes but ended up taking 45. After that, there was a coding round with what I thought was an easy question. I used a list which gave me O(1) time complexity because I'm good with collections, but I still got rejected. Maybe the interviewer wanted me to use a stack instead of a list. The interviewer felt more like a supervisor than a collaborator, unlike the great interviewers I've had at Google.