Moveworks Software Engineer Interview Questions
& Process

It was a lengthy interview process, spanning 4 weeks from application to offer. I applied directly. First, there was a 30-minute recruiter phone screen about my background and the role. Then, a 1-hour technical interview with a senior engineer, which involved a problem similar to 'word break'. Following that, I had a virtual onsite loop consisting of two coding rounds, two system design rounds, a one-hour session, and a 30-minute product demo. The coding questions were medium-hard, akin to LeetCode, focusing on strings and hashing. System design questions were also medium difficulty, emphasizing core concepts. The overall difficulty was quite high.

The interview process was tough and well-structured technically. It started with two phone screens, one focused on coding and the other on system design. Then came an 8-round onsite interview. This included a demo, more coding and system design interviews, talks with the hiring manager, and leadership rounds. The whole onsite part took over 6 hours, which was quite long and tiring. However, the recruiting and coordination team was really bad at communicating and organizing things. Even before the onsite, they were slow to respond. After I finished the last round, I followed up for three weeks by emailing different recruiters, but no one got back to me. I finally had to ask someone at Moveworks to connect me with recruiting. A recruiter then replied saying the decision was in their internal system and I should have gotten it. This felt like a poor excuse after weeks of silence. Even if automated emails failed, they had plenty of chances to reply to my many follow-ups. When a candidate puts in so much time and effort, the least they can do is provide timely closure and communicate respectfully. A lack of transparency and follow-through really hurts the candidate experience, no matter how high the company's technical standards are.

The interview process for the Software Engineer role in Bangalore involved several rounds. It started with introductory calls with the TA head and Site head. This was followed by two rounds focused on Data Structures (DS), two design rounds, one product demo, and concluded with a Hiring Manager (HM) round. Most of my interactions were with people from the US, and their energy was infectious, particularly Matthew and Vaibhav. They were very thorough in providing all necessary information for candidates to make an informed decision about accepting an offer. While the overall experience was good, it was quite lengthy and some parts felt repetitive. The compensation structure is also good, with a strong emphasis on ESOPs for long-term wealth creation.