
MANTL Software Engineer 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
Candidate interview experiences
First-hand accounts from people who interviewed at MANTL.
Software Engineer
This was a big waste of time. It looked good at first, but after 7 interviews, I got a different impression. I went through everything and answered all the questions, but I never got specific feedback on why they decided not to move forward. I probably would have declined an offer anyway.
- Could you build a Node app that calls an outdated API?
Software Engineer
The Head of Talent hit me up on LinkedIn. We clarified some initial stuff like pay, remote work, and what the company does. Then we set up a call to go over more details, and also a 45-minute technical screen over video. After passing that, I had 3 final round interviews. They got back to me pretty quickly, like 1-2 days, with a verbal offer. Before making it official, they scheduled two more chats, one with the CTO and one with the CEO. These were more for me to get info about the company, where they're headed, and how they plan to get there, which helped me decide between offers. After that, I got the written offer. The whole thing was smooth, and everyone seemed smart and nice. The process took about a month, starting with setting up interviews in week 1, then the tech screen in week 2 and scheduling final rounds, doing final rounds and getting a verbal offer in week 3, and finally talking with my future manager, CEO, and CTO in week 4 to get the written offer.
- First round: 45 min technical screen, typical Leetcode stuff
- Final round: 3 interviews - Coding Session (2hr): longer hands to keyboard exercise with real world examples of the problems they work on, it was more collaborative. They tested me on something you wouldn't really expect, which I think tested more my general ability to think and adapt what I know, but they did help out with the intricacies, so I didn't feel too thrown off and could appreciate the problem.
- Technical Deep Dive (45min): Discuss past projects you in detail, talk about the trade offs and what worked and what didn't work. More about larger-picture technical knowledge and ability to communicate.
Software Engineer
The interview process moved pretty quickly, the recruiter kept me well informed throughout, and all of the interviewers were really nice people. There were 4 parts to the interview process: a 30 minute recruiter screening call, a 45 minute technical screening interview, a 4 part panel interview, which included a general overview of my experience, a technical deep dive on a recent project, a system and design interview, and a React coding interview, and a 30 minute meeting with the co-founder/CTO.
- The technical screening was an easy level Leetcode question.
- The system design interview was to design the system for a feature of a well known app, including data storage, servers, client, data fetching, etc.
MANTL Software Engineer Interview Questions
Quoted word for word from MANTL interview reports.
“Build REST API endpoints with Node.js and a SQL Query Builder.”
Read reports →“How do you set up a PostgreSQL table?”
Read reports →“Could you build a Node app that calls an outdated API?”
Read reports →“Could you design a card creation API?”
Read reports →“What are the tech milestones?”
Read report →“Can you explain SQL?”
Read report →“How would you test functions and endpoints?”
Read report →“Can you explain routes?”
Read report →“How would you create endpoints?”
Read report →Formats, difficulty and experience
Across all 14 MANTL interview reports.