MX logo

MX Backend Engineer Interview Questions
& Process

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

Based on 6 interview experiences · FREE TO READ

3.7 Rounds average
Average Typical difficulty
100% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at MX.

Showing 3 of 6
MX logo
MX

Backend Software Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 4 rounds
Interview process
Phone screen Technical screen Onsite Panel Group Presentation Background check Offer
Interview formats
Behavioral Technical Coding

The interview process was a bit long, with a phone interview, a couple of panel interviews, individual interviews with people from different departments, and a final interview with the hiring manager. They really seem to focus on finding the right people who fit the company culture and values. The interviews were pretty laid-back, with a lot of questions about culture and some technical ones. No whiteboard coding, but they asked more open-ended 'how' and 'why' questions to understand your problem-solving approach. Overall, it was a really nice experience, and everyone I met was very friendly.

Confirmed questions1 question
  • Can you walk me through the functionality of Rails controllers within an application?
MX logo
MX

Backend Software Engineer

Engineering

Mid Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Panel Onsite Background check Offer
Interview formats
Behavioral Technical System Design Coding

After applying, I had an initial phone screen with the technical recruiter. It was a relaxed chat about the company, the job, and my background. They said they'd pass my info to the leadership. A few days later, I got a call to schedule an interview with the hiring manager. This one was more technical, focusing on my resume details. It was still friendly and conversational. Next was a panel interview over Zoom (due to COVID). I met four people: a team lead, a leader from another department (both for cultural fit), and two engineers from the department. This last part was the longest and most technical. No whiteboarding. They're good at assessing technical skills and adapting. The final interview was with two leaders from different departments. It was very non-technical, all about my experiences and alignment with MX. We had insightful talks, and I learned about their career paths. I got the offer the day after. I really enjoyed the whole process. It felt different and not like an interrogation. It's a long process, but MX seems serious about finding people who fit their mission. The recruiter was also great – friendly, clear, and responsive.

Confirmed questions3 questions
  • Could you explain asynchronous JavaScript to someone new to it?
  • Can you discuss high-level system design concepts?
  • What are some high-level computer networking concepts?
MX logo
MX

Back End Engineer

Engineering

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical Presentation

I applied online and got an email the next day to set up a phone screening. After that, there was a technical chat with the hiring manager, and then a video call that included both technical and cultural fit questions. I was then invited for an on-site interview. They covered my travel expenses since I wasn't local to Utah. My recruiter was really helpful and worked with me to arrange travel. The on-site involved three panels, feeling more like a casual chat about my background and some cultural fit aspects. They also gave me more time to learn about MX and what to expect there. It was a great interview overall, and everyone I met seemed genuinely interested in getting to know me.

Confirmed questions2 questions
  • What interests you about MX?
  • What does success look like to you?

MX Backend Engineer Interview Questions

Quoted word for word from MX interview reports.

Can you explain the difference between the window object and the document object in JavaScript?

Read reports

Could you explain asynchronous JavaScript to someone new to it?

Read reports

Can you walk me through the functionality of Rails controllers within an application?

Read reports

Formats, difficulty and experience

Across all 6 MX interview reports.

Interview formats

Behavioral 35.3%
Technical 35.3%
Coding 17.6%
System Design 5.9%
Presentation 5.9%

Interview difficulty

Easy 0%
Average 100%
Difficult 0%

Candidate experience

Positive 100%