Kinaxis Software Engineer Interview Questions
& Process

I applied for a Software Engineer role and made it clear I'm not a React expert, emphasizing my strengths lie elsewhere. The recruiters still moved forward and set up a technical interview. It was supposed to be 1.5 hours, but the interviewer cut it short at 35 minutes, focusing solely on deep React concepts. No questions touched on my actual experience, skills, or the technologies I've used for years. Their expressions and tone suggested I was already dismissed. The interview ended abruptly, without a proper wrap-up or basic courtesy. It wasn't hard, just a total mismatch that could've been avoided if they'd read my profile or listened initially. Spending days preparing and blocking my schedule just to be met with obvious disdain felt disrespectful and unprofessional. Pros: Nothing from the interview process. Cons: Bad communication, wasted candidate time, rude and dismissive interviewers. Advice for management: If a candidate states they lack expertise in a specific technology, either screen for relevant skills or save everyone's time. Basic respect is free.

It was a three round process. The first round was purely DSA and OOPS based with a few questions on puzzles. The second round was to write react/ JS code on paper of a simple page with three buttons which change color of the other boxes when clicked on it. Apart from that more questions on JS and react. The third round was HR round.

The first round had 40 MCQs on aptitude, logic, and technical topics. Math and logic questions were more about clever thinking than formulas, so practicing problem-solving on sites like GeeksforGeeks and Indiabix is recommended. Technical questions focused on code outcomes and OOP concepts. Round 2 was a 1.5-hour technical interview where I talked about myself, my projects, and internship experience. Then, questions on OOP principles (four main ones, polymorphism, abstraction, virtual functions, abstract classes, interfaces), theoretical data structures and algorithms (trees, linked lists, stacks), and coding questions mainly about strings. Round 3 was a 45-minute interview with two interviewers. We discussed the database I used, differences between SQL and NoSQL, and their applications. Then, advanced data structures like trees, binary search trees, and self-balancing trees. A scenario was given where a sorted list needed efficient maintenance, and I was asked what data structure to use. Round 4 was a 1.75-hour interview with two interviewers. We discussed my projects, including authentication. Then, tough questions on OOP, operating systems (deadlocks, scheduling), more theoretical and coding questions on data structures, and puzzles. Round 5 was an HR round. We discussed something not on my resume, my fit with company culture, reasons for choosing the company, why they should hire me, and the company's office. The interview ended well, and I got the offer. Key takeaways: know yourself, stay calm, and be respectful.