Real, anonymous reports from people who interviewed for Software Engineer at Moveworks.Ai, newest first and distilled into what to expect across the loop.
My process felt like a tight loop of technical testing: two coding rounds, a system design round, and a behavioral round. The interviews were LeetCode-style, with a mix of medium and hard problems. I had the sense they were looking for not just an answer, but for me to be able to walk through the whole approach cleanly and handle follow-ups.
After a recruiter screen, I ended up doing a pretty standard technical sequence on Zoom. A couple of rounds focused on DSA, and those were the main way my candidacy was evaluated—both the difficulty and how I performed across the two coding rounds seemed to matter. After that I moved into deeper design-style interviews: LLD and HLD system design rounds where they expected me to structure the thinking clearly, and then there was an additional hiring-manager style conversation.
The interview process typically includes multiple coding rounds focused on data structures and algorithms, followed by system design interviews that assess both low-level and high-level design skills. Candidates should prepare for a rigorous evaluation of their technical knowledge and problem-solving abilities under time constraints.
Candidates can expect a hiring-manager conversation that assesses fit and alignment with company values, often occurring after the technical rounds. This part of the process emphasizes communication and the ability to articulate one's experiences and thought processes.
The interview environment can vary significantly; some candidates report a friendly and engaging atmosphere, while others describe it as hostile or misaligned with typical interview expectations. It's important to be prepared for different interviewer styles and dynamics.
Many candidates noted a lack of timely feedback and communication throughout the process, which can lead to frustration and uncertainty. Being proactive in seeking clarity and following up can be beneficial.
Candidates often experience significant pressure during coding rounds, where performance can hinge on time management and the ability to think clearly under stress. Practicing coding under timed conditions is advisable.
Rejections can occur despite strong technical performance, often attributed to broader market conditions or misalignment in expectations. Candidates should be prepared for potential ambiguity regarding offer details and overall compensation.
