Starts with a phone screening, then a take-home coding exam. Once the hiring team takes a look at the exam, they will either approve or not. If approved, you interview with the team, and do a basic interview with a code review as well.

The interview process at Mindex was very organized and overall a good experience. Here’s how it went for me: 1. Recruiter Call: I applied through their website, and about a week later, a recruiter reached out to schedule a phone screen. The call lasted about 25–30 minutes. It was pretty casual — we talked about my work background, why I was interested in Mindex, and some basic logistics like salary expectations and when I could start. The recruiter also gave me a quick overview of the role and what the next steps would look like. 2. Online Coding Test: A couple of days after the recruiter call, I received a coding assessment through HackerRank. It had two questions — one on arrays and hash maps, and the second one was a bit harder, more like dynamic programming. I had 90 minutes to complete it. The problems weren't crazy difficult but definitely required careful thinking under time pressure. 3. Technical Interviews: Once I passed the coding test, they scheduled three back-to-back technical interviews, all done virtually over Zoom. The first round was live coding with a senior engineer. They gave me a tree traversal problem and asked me to code it while explaining my approach. The second round was a system design interview with a tech lead. I was asked to design a basic ride-sharing service backend. They weren't expecting production-level code, but they were looking for a good discussion around trade-offs and scalability. The third round was a technical deep dive. They asked questions about my recent projects, focusing on how I handled performance issues, database design, and debugging real-world problems. 4. Behavioral Interview: The final interview was a behavioral round with the hiring manager and one of the senior engineers from the team. It was mostly about how I work with others — questions like "Tell me about a time you handled a tough situation with a teammate" and "How do you manage deadlines when priorities shift?" They also shared a lot about Mindex’s work culture and what it’s like day-to-day. 5. Offer: About a week after the final interview, the recruiter called to tell me they were moving forward with an offer. The written offer came later that day and included base salary, bonus details, and a strong benefits package. They were open to a little negotiation too after I mentioned a competing offer. Overall Thoughts: The entire process took about three to four weeks from application to offer. Everyone I interacted with was respectful, clear, and responsive. I never felt like I was left hanging. The technical rounds were definitely challenging, but fair — no trick questions or unrealistic expectations. The process felt balanced between technical skills and culture fit. If you’re interviewing with Mindex, I’d recommend brushing up on data structures, system design basics, and being able to clearly walk through your past work. Communication and explaining your thought process matter a lot here.