Real, anonymous reports from people who interviewed for Software Engineer at Moveworks, newest first and distilled into what to expect across the loop.
Get your personalized Moveworks Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After a recruiter call, I ended up going through a pretty standard technical sequence. About a week later I had a coding interview on Zoom where I worked through DSA-style problems and talked through how I was thinking as I implemented. The process then continued into more technical rounds, and I remember it feeling fairly judged on accuracy and completeness rather than conversation alone.
Next came system design in a more hands-on way. I was asked to explain core concepts and structure tradeoffs, with the design questions feeling medium level and focused on fundamentals. The overall vibe was that it was getting harder: one DSA round was string/DP adjacent for me, and the rest of the technical flow pushed me to be clear about reasoning, not just produce code.
5 months ago
Average Negative New York, NY
My process started like it would be straightforward, but it dragged on in a way that made it hard to stay confident. The recruiter had initially set expectations around timing, yet the total run stretched far beyond what I was told. By the time I got deep into the interviews, the sessions felt disorganized—there were multiple interviewers who seemed unprepared or disengaged, and I barely received any signals about how things were going while I was in the middle of it.
The technical portion itself was demanding and structured, but the scheduling and coordination around it were the bigger problem. I went through multiple rounds that included coding and system design, plus an onsite-style loop with a hiring-manager and additional deeper technical discussions. Even with that intensity, I wasn’t getting much feedback during the work, and it left me guessing about where I stood.
> 1 year
Difficult Neutral Santa Clara, CA
My first step was a Zoom coding interview that started with small talk—introducing myself and answering follow-ups about my background. Then the inter…
> 1 year
Difficult Neutral San Francisco, CA
My first contact was a recruiter screening call, followed by a coding interview. The recruiter interaction was kind and easy-going, but the coding rou…
> 1 year
Easy Negative Austin, TX
My process felt uneven from the start. I made it through early HR screening into the hiring-manager portion, but that round didn’t run smoothly and le…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical / Coding Screen
The initial coding interviews focus heavily on data structures and algorithms (DSA), with questions often being medium to hard in difficulty. Candidates are expected to demonstrate clear reasoning and correctness under time pressure, and performance in these rounds significantly influences overall outcomes.
DSALeetCodeTime pressure
System Design Round
Candidates will face system design interviews that assess their understanding of core concepts and trade-offs, typically at a medium difficulty level. These rounds require clear communication of design choices and reasoning.
System designTrade-offsCommunication
Interview Structure & Coordination
The interview process can vary significantly in structure and organization, with some candidates experiencing disorganized sessions and delays, while others report a more streamlined and efficient flow. Communication about the process and timely feedback can be inconsistent.
CoordinationFeedbackStructure
Behavioral & Values Assessment
Interviews often include behavioral components where candidates discuss their past experiences and fit within the company's culture. Some candidates noted the importance of engaging with leadership during these discussions.
BehavioralCultural fitLeadership interaction
Overall Experience & Communication
Candidates have mixed feelings about the overall experience, with some appreciating the friendly atmosphere and timely communication, while others felt the process was chaotic and lacked respect for their time. The outcome often left candidates wanting more clarity and closure.
CommunicationCandidate experienceClosure
Difficulty & Outcome
While many candidates faced challenging technical questions, the overall difficulty varied, with some finding the questions too easy for the number of rounds involved. The final outcome often felt disconnected from their perceived performance, leading to frustration.