Moveworks logo

Moveworks Customer Success Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 12 interview experiences · FREE TO READ

4.4 Rounds average
Average Typical difficulty
50% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Moveworks.

Showing 3 of 12
Moveworks logo
Moveworks

Customer Success Engineer

Engineering · a year ago

Mid Difficult Negative experience No offer 8 rounds
Interview process
Technical screen Presentation
Interview formats
Coding Presentation

So, I had 8 interviews total for the Customer Success Engineer role. It included 2 live coding challenges and a technical demo presentation. Honestly, it felt pretty cold. Nobody seemed welcoming or engaged, they were all bored and distracted, and no one bothered to get to know me. For a job that's all about implementation, it would make more sense to give a take-home assignment and then go over the solution together. That'd be more like the actual job and how we'd collaborate. Lots of people seem to agree with this, and even though they say they've heard the feedback, they haven't changed anything.

Confirmed questions2 questions
  • Imagine a customer gives you API access to their user data. They need a CSV report containing only active users who have a .test email address. Each line in the report should list the user's ID and email, like this example: id,email 4478538,dhan@gmail.com.
  • Could you create a Slack bot that takes employee data from a JSON file and answers HR questions? It needs to handle a /list command to show all first names and their departments, and a /query command to get specific user info like email or phone. Not all details might be present, but department is a must. You'll have an hour to do this.
Moveworks logo
Moveworks

Customer Success Engineer

Engineering · a year ago

Entry Average Positive experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Take home Presentation
Interview formats
Technical Coding Presentation Behavioral

It started with a phone interview, then I talked to the team lead. After that, there was a technical interview with someone from the team focusing on JSON and APIs. This was followed by a marathon of technical interviews, including a demo, speaking with a Customer Success Manager, a take-home assignment, a presentation, and a personality assessment. They were in touch throughout, sending materials via email and checking my understanding.

Confirmed questions2 questions
  • How would I sell to someone who is not technical vs. someone who is?
  • How would I sell to a non-tech person versus a tech person?
Moveworks logo
Moveworks

Customer Success Engineer

Engineering · more than a year ago

Mid Average Negative experience Decline offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Presentation Background check Offer
Interview formats
Behavioral Technical Coding Presentation

It began with a recruiter chat, then a quick meet with the Hiring Manager to go over the role, my background, and the daily tasks. After that, we had a live coding round, which was pretty basic – just calling a public API and showing the output as requested. Then came what they called an 'On-site' interview, which felt overly complicated. This 'on-site' had four interview rounds and a product demo by the Moveworks folks. Round 1 involved loading data from a JSON file and displaying it in Slack. Round 2 was a presentation about a tech product I chose. Round 3 was about CSM partnership. Round 4 was the product demo from the Moveworks team. Round 5 was with the Hiring Manager again. Honestly, they could have streamlined this whole thing. Two coding rounds for a job that's mostly about implementation and integration seems like overkill, and they should use a standard tool for coding tests instead of this drawn-out process.

Confirmed questions4 questions
  • Can you tell me about your role at your previous company?
  • Could you use the provided public API and display the response in the mentioned way?
  • Describe the projects you have worked on previously.

Moveworks Customer Success Engineer Interview Questions

Quoted word for word from Moveworks interview reports.

How can you extract specific data from a given public API?

Read reports

Could you use the provided public API and display the response in the mentioned way?

Read reports

How would you load the data and present it in a Slack channel?

Read reports

How would I sell to someone who is not technical vs. someone who is?

Read reports

How would I sell to a non-tech person versus a tech person?

Read report

Could you create a Slack bot that takes employee data from a JSON file and answers HR questions? It needs to handle a /list command to show all first names and their departments, and a /query command to get specific user info like email or phone. Not all details might be present, but department is a must. You'll have an hour to do this.

Read report

Describe a situation where you resolved a customer's issue.

Read report

Can you tell me about a time you messed up and had to tell a client about it?

Read report

Formats, difficulty and experience

Across all 12 Moveworks interview reports.

Interview formats

Technical 28.6%
Behavioral 25.7%
Coding 25.7%
Presentation 14.3%
System Design 2.9%

Interview difficulty

Easy 16.7%
Average 58.3%
Difficult 25%

Candidate experience

Negative 41.7%
Positive 50%
Neutral 8.3%