
Mixmax Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 39 interview experiences · FREE TO READ
Which role are you interviewing for?
15 roles · 39 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Mixmax.
Data Analyst
The interview process took about seven weeks. It started with a talent screening, then a hiring manager interview. After that, there was a technical case study with a deep dive. Next, I interviewed with an Engineering Manager, and finally, with the CEO and co-founder. The interviews were friendly and thought-provoking. I got good vibes early on, and some interviewers even connected with me on LinkedIn. The CEO interview was super intense with lots of questions, making it hard to ask my own, but it was still fun. I got positive feedback again and was told to expect an answer soon. But then, after 21 days of silence, even after I followed up, I heard back. They said I was their best candidate but decided not to hire me because they weren't sure if the role needed to be full-time. They wanted to check if a dedicated data person was needed first and went with someone who could start part-time. They never asked if I'd do part-time, though. This news right before another interview really messed me up, and that next interview was a disaster. The Mixmax interview was great until the very end.
- Were your questions mostly about product analytics?
- The final interview with the CEO was really tough with the most questions I've ever gotten, leaving no time for me to ask any questions back, but I still enjoyed it.
Product Manager
This was genuinely the best interview experience I've had in ages, I felt compelled to leave a review. They might've improved from past mistakes based on feedback I've seen. I went through two stages: first with their recruiter, then with the CEO. Unfortunately, they decided not to move forward after the second round, but they were super clear about why, giving me incredibly detailed feedback, which is rare. I really appreciate that, hence this review.
- Can you share your experience with creating tools for sales and marketing teams?
Senior Software Engineer
This hiring process was really confusing and inconsistent, even after six interviews for a Senior Full-Stack Engineer role. Initially, the interviewers were friendly and gave positive feedback, and I felt my technical solutions were good and scalable. However, the rejection email stated I wasn't product-focused enough, which contradicts the feedback during the interviews. I even added extra features to the live code challenge, which was well-received, but later received written feedback complaining about duplicated code that wasn't there. My System Design interview feedback was also contradictory; I was told my solution was working and scalable, but then later told I needed guidance on scalability and reliability. The process dragged on with 6 interviews and a homework assignment, and they judged a developer role on product leadership criteria without being clear upfront. Leadership's response to concerns was defensive. If you're a developer here, expect to be judged on leadership and product strategy over technical execution, and be aware that feedback is inconsistent and the process is longer than usual. Decisions might be based on uncommunicated factors.
- How would you add a bunch of features to a calendar app?
- In terms of system design, how would you implement an "undo" feature in an email system?
QA Lead
Applied online and got a quick recruiter call within 30 minutes to schedule the first meeting. The first meeting was a standard HR chat covering my background, motivations, expectations, and salary. Then came an unpaid assignment: create a 90-day roadmap to set up Mixmax's QA function from scratch. After that, I had a second interview with someone from engineering, focusing on both technical and soft skills, which was pretty chill. The third interview involved presenting my assignment to two engineering folks and answering their questions; this one was easy. The final, fourth interview was with a C-level exec, mostly about cultural fit and long-term vision. Despite getting great feedback at each stage, I got a rejection email saying they went with someone else. They mentioned the job description changed during the process, but that it was too minor to inform me. Honestly, felt like a waste of time and disrespectful.
- Can you tell us about yourself, what motivates you, and what you're looking for?
- What are your salary expectations?
- Please outline a 90-day plan for establishing the QA function at Mixmax from scratch.
Mixmax Interview Questions
Quoted word for word from Mixmax interview reports.
“Implement a simple web application for calendar matching.”
Read reports →“Can you implement a function to generate a histogram from data, focusing only on the logic?”
Read reports →“In terms of system design, how would you implement an "undo" feature in an email system?”
Read reports →“Can you explain how to implement rate limiting?”
Read reports →“Could you please code the search/filtering functionality?”
Read report →“Solve a timed coder-pad problem involving logic for back-end middleware that serves client data.”
Read report →“How would you add a bunch of features to a calendar app?”
Read report →“Implement a minor enhancement for their current product.”
Read report →“What is your understanding of Mixmax?”
Read report →Formats, difficulty and experience
Across all 39 Mixmax interview reports.