Intellias Interview Questions
& Process

First off was an HR chat about my background, why I want to work here, and if I'd fit in. We talked about what I've done before, what I expect from the role, and what I know about the company. They wanted to see if I could communicate well, work with others, and was on the same page as them. Then came the technical part, covering C++ theory and practice. Started with basic C++ stuff like OOP, how memory works, and modern C++ differences. Then we dove into STL, containers, iterators, algorithms, and how fast they run. The big part was a coding challenge, about 20-30 mins, solving some algorithm problems to see how I think, write clean code, and handle stress. Lastly, I chatted with the Project Manager about solving problems in the real world, working with the team, and getting project requirements. We discussed workflow, what's important, and how I could help with current projects.

So, first I had a call with HR, then another meeting with HR on Teams. After that, there was this technical 'task' thing we all did on a call together, like, everyone interviewing for the role. Finally, the main technical interview with a senior person. The feedback was terrible, practically non-existent. They said they'd let me know either way, but then they just totally ghosted me!

So, there were 4 rounds in total. First, an online test covering basic programming, problem solving, and coding. Then, Technical Round 1 (T1) was all about backend stuff, data structures, and talking about my past projects, with some theory and coding. Technical Round 2 (T2) dug into system design, architecture, and advanced Node.js/NestJS, plus some scenario questions. Lastly, Technical Round 3 (T3) was a deep dive into code quality, debugging, testing, and real-world project challenges.

The interview process felt pretty random and not very structured. They seemed way more focused on testing aspects like TDD, BDD, and integration testing, which was surprising since I expected more focus on development. It was almost like they were hiring for testing roles, not development ones. I heard about a friend who had a really good resume and experience but got rejected just because he didn't know TDD and BDD, even though he was great with unit and integration testing. It's wild because he got shortlisted by Amazon and Walmart, but Intellias passed on him. Weird and a bit of a bummer. The first step was an MCQ test and a simple Spring Data JPA project, which wasn't too tough. Then, in the first technical interview, I had to do a coding problem. It was a bit rocky at first, but I got it done. Honestly, the interviews were just confusing and didn't have a clear point. Usually, interviews check for DSA, Java, Spring, and system design, but it wasn't clear what they were actually looking for here. To make things worse, the HR team totally went silent after the interviews. No feedback, no word on if I passed or failed, which is pretty basic professional stuff.