
Mindbody Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 67 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Mindbody.
Senior Software Engineer
It kicked off with a quick chat with the technical recruiter, which was helpful for understanding things better. After that, I did a one-hour coding test on Codility, not a pair programming thing. Then, I had a 45-minute meeting with an Engineer manager. The last part was the panel interview, which was split over two days and included five separate interviews: one on reading and refactoring code (like a PR review), another on implementing code that had bugs or missing pieces (kind of like pair programming but with existing code), a 45-minute session on non-technical and cultural fit stuff, a one-hour session on API design and system decomposition, and finally, a one-hour technical design review where I had to look at a design doc and give feedback as if I were helping another engineer. Even though it felt like a lot and some parts were repetitive, the format did a good job of showing what the job would actually be like day-to-day. A few days later, less than a month from when I first connected, I got the rejection, just a standard 'we're moving forward with someone else' without any specific feedback. I put in about 7 hours total for the interviews and didn't get any details on how I did, even after asking via email.
- Code Reading and Refactoring
- Technical Implementation, pair programming
- API design
Software Engineer
Had a great interview experience, the interviewers were strong technically. This company doesn’t ghost candidates. I got feedback when I asked for it, which helped me improve. Thanks to Neha for a smooth process, similar to FAANG recruiters. I think it’s a great place to work. Most people I talked to were passionate and knowledgeable.
- Two questions about System design for iOS, focusing on writing good testable software. Your daily coding skills are enough if you focus on craft.
- A round with the VP.
- A behavioral round with the manager.
Software Engineer
It began with a recruiter chat to gauge cultural fit and my background. Then, a technical 1:1 with the hiring manager. The last stage was a multi-part interview including a debugging session on CoderPad, a systems design discussion on CoderPad, an Android-focused technical interview, and finally a chat about team, culture, and leadership.
- Can you tell me about a project you worked on that had a notable impact?
- What metrics or methods did you use to quantify the impact of that project?
- Describe your approach to collaboration and how you get buy-in from others for your concepts.
Mindbody Software Engineer Interview Questions
Quoted word for word from Mindbody interview reports.
“How do you determine if an integer is a palindrome?”
Read reports →“How do you find the middle element of a linked list?”
Read reports →“Can you write an algorithm in C# that counts how many times each word appears in a given string?”
Read reports →“How do you convert an array of Objects to an object?”
Read reports →“Could you write an SQL query to find the second largest salary from the employee table?”
Read report →“Can you write code to find duplicate words in a sentence and count them?”
Read report →“Can you explain the difference between a stack and a queue?”
Read report →“Could you write some simple methods, around 10-20 lines long, to do things like capitalizing all vowels in a string?”
Read report →“Can you debug and fix a complex algorithm without a debugger?”
Read report →Formats, difficulty and experience
Across all 67 Mindbody interview reports.