Mezmo logo

Mezmo Interview Questions
& Process

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

Based on 14 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
35.7% Positive experience

Which role are you interviewing for?

8 roles · 14 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Mezmo.

Showing 4 of 14
Mezmo logo
Mezmo

Product Management Director

Product · more than a year ago

Director Average Negative experience No offer 3 rounds
Interview process
Recruiter call Background check Offer
Interview formats
Behavioral

Talked to the recruiter who liked me. Then chatted with the CEO, it was a good meeting and mostly them trying to get me to join, and they wanted me to meet the eng and PM teams next. Then I got a generic rejection email. This company is all over the place. They seem to be making big changes.

Confirmed questions2 questions
  • Can you tell me about the ARR?
  • What was your previous team size?
Mezmo logo
Mezmo

Senior Security Engineer

Engineering · more than a year ago

Senior Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Onsite Background check Offer
Interview formats
Technical Behavioral

After applying online and getting through the initial interviews, a 5-hour interview session was scheduled with different teams, though it was offered to be split up. It involved meeting several people who asked questions. The questions weren't perceived as very difficult, but the back-to-back nature made it tough to switch between topics like compliance, release engineering, management, pipelines, encryption, and security tools like SIEMs. Despite being told feedback would be given within 3 business days, I had to follow up twice. The feedback wasn't very helpful for future improvement, as I was rejected based on 'nice to have' qualifications rather than 'required' ones.

Confirmed questions8 questions
  • Tell me about different types of encryption.
  • What's your experience with pipeline management?
  • How do you approach securing code?
Mezmo logo
Mezmo

Front End Developer

Engineering

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Behavioral Technical Coding

First, there was a quick 15-minute chat with the recruiter about the company and my background. They asked some standard questions like why I'm looking to leave my current role. After that, they sent over a technical assignment. It was a design-focused task where I had to build a clone of the Slack app using HTML, CSS, and JavaScript, with the option to use frameworks. I spent a few days completing it and sent it back. I followed up a couple of times over the next few weeks but never got a response, which felt like a complete waste of my time and quite disrespectful.

Confirmed questions1 question
  • What's motivating you to seek a new position?
Mezmo logo
Mezmo

Software Engineer

Engineering

Senior Easy Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Coding

The interview process was pretty standard. Started with a recruiter call where they went over the job description and talked about my background. Next up was a video call with the Engineering manager, who was great and introduced himself really well, I liked that call. Then, a video call with a senior developer where I got asked some Java coding questions, like reversing a string, which were pretty easy and I nailed them. Even though I thought it went well, I got a rejection email the following day.

Confirmed questions2 questions
  • How would you reverse a string?
  • What is the maximum subset sum in an integer array?

Mezmo Interview Questions

Quoted word for word from Mezmo interview reports.

Can you describe how you would architect an auto-complete search feature?

Read report

Formats, difficulty and experience

Across all 14 Mezmo interview reports.

Interview formats

Technical 34.5%
Behavioral 31%
Coding 24.1%
Other 3.4%
Presentation 3.4%

Interview difficulty

Easy 28.6%
Average 50%
Difficult 21.4%

Candidate experience

Negative 57.1%
Positive 35.7%
Neutral 7.1%

Reports by job function

Engineering 9
Operations 2
Product 1
Analytics 1
Design 1