
MX Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at MX.
Software Engineer
I talked to the Recruiter first, and it went well. Then, the following week, I had a tech screen. It was mostly just discussing my past experience. The Q&A was fast-paced and felt a bit impersonal, without much enthusiasm for the company. The week after that, I did a full day of four panel interviews. The interviews themselves were a mixed bag – some good, some really dull. It felt disorganized, one-sided, and took up a lot of time. I only found out about my tech screen the day before, with just an email containing the interviewer's LinkedIn and a Zoom link, saying 'be here at this time tomorrow,' with no calendar invite. This is tough when you're already working full-time. For the all-day interviews, I was told it might be later in the week, but the recruiter didn't answer my questions. Then, the day before, at the end of the day, I got the confirmation and schedule, again with no calendar invite. After that, I didn't hear anything else. Given the current job market, I'd probably skip this interview process.
- Are you familiar with standard interview questions?
Software Engineer
The talent team at MX was great. Even though I didn't talk to a recruiter until the end, I worked with a recruiting coordinator who gave me her personal cell number for faster communication. She was really patient with my questions and requests and went out of her way to accommodate me. The front desk staff were also friendly, making me feel welcome. The onsite interview was long, as expected. I enjoyed talking with the interviewers who seemed genuinely interested in me and got to know me. I was impressed with the team and process, but I didn't accept their offer because the compensation was surprisingly low.
- Can you share how your personal values align with our company values?
Software Developer
The interview process wasn't too tough, but it did take a while, with three separate interviews. It started with an email asking for a phone interview, which was set for the next day. This initial call was pretty basic, mostly just getting to know each other. The interviewer even admitted he didn't know the answer to one of the technical questions he asked and questioned why he was the one asking it. A few days later, I got another email for an in-person interview, scheduled for two days after that. This turned into two interviews: first, a technical one with two developers that lasted about an hour. I really liked this part; they were good at checking technical skills through talking and questions, not just typical whiteboard stuff. Then, another hour-long interview with two other developers focusing on culture and fit. They asked a lot about my work and leadership style and spent time selling the company, mentioning how much better their hiring is now and how their careful process helps them hire better people. During this, they explained the rest of the process: my scores would go into a system, and if they were high enough, the final step was meeting the CTO, who had a veto if he didn't think I was a good fit. I followed up via email and heard back in under a week, setting up the CTO meeting. The next day, I was told he was out of town and we'd reschedule in a few days. I gave my availability for the following week and waited. After another 5 days of no response, I emailed asking if they still needed my schedule and for an update. Four days later, I reached out to the HR rep I'd been talking to on LinkedIn to see if everything was okay. They accepted my connection, so I figured that would get a response. Four more days passed, and I messaged on LinkedIn asking about the position and if it was still open or if I could expect to hear back. Almost two days later, a different HR person emailed saying the position was filled and I wasn't selected. They also asked me to connect on LinkedIn and apply for other roles. They talked a lot about company values like transparency and trust, which seemed contradictory to the lack of communication and being ignored for two weeks before getting the rejection email. The people I met seemed fine, but the company seems to have major issues with organization and consistency in hiring.
- If you had 100 million dollars, what would you do?
- What distinguishes a manager from a leader?
- Describe the most challenging problem you've encountered as a developer and how you resolved it.
MX Software Engineer Interview Questions
Quoted word for word from MX interview reports.
“Could you fix a bug in the loan payoff calculator feature?”
Read reports →“What distinguishes a manager from a leader?”
Read reports →“If you had 100 million dollars, what would you do?”
Read reports →“Why should I join MX?”
Read reports →“What are the key things you look for when reviewing a pull request?”
Read report →“Tell me about your favorite Ruby keyword.”
Read report →“What is your main motivation?”
Read report →“What's your approach when you have a disagreement with a coworker?”
Read report →“Can you tell me about your experience with postgresql?”
Read report →Formats, difficulty and experience
Across all 12 MX interview reports.