Mindbody logo

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

3.6 Rounds average
Average Typical difficulty
58.2% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Mindbody.

Showing 3 of 67
Mindbody logo
Mindbody

Senior Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Panel Offer
Interview formats
Technical Coding System Design Behavioral

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.

Confirmed questions5 questions
  • Code Reading and Refactoring
  • Technical Implementation, pair programming
  • API design
Mindbody logo
Mindbody

Software Engineer

Engineering · a year ago

Staff Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Presentation Onsite
Interview formats
System Design Behavioral Technical

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.

Confirmed questions3 questions
  • 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.
Mindbody logo
Mindbody

Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience Accept offer 7 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Technical screen Technical screen Panel
Interview formats
Behavioral Technical Coding System Design Technical

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.

Confirmed questions3 questions
  • 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.

Can you write an algorithm in C# that counts how many times each word appears in a given string?

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.

Interview formats

Technical 33.9%
Coding 26.9%
Behavioral 26.9%
System Design 8.6%
Other 2.2%

Interview difficulty

Easy 20.9%
Average 65.7%
Difficult 13.4%

Candidate experience

Negative 26.9%
Positive 58.2%
Neutral 14.9%