MathWorks Software Engineer and EDG interviews typically start with a MATLAB-or-coding online assessment, sometimes with a HireVue video, then a resume- and OA-focused technical round and a roughly four-hour final loop mixing coding, design, and behavioral questions.
$120K
Avg. Base Comp
$150K
Avg. Total Comp
4-6 rounds
Typical Rounds
2 months
Process Length
MathWorks' Software Engineer and EDG (Engineering Development Group) interviews usually open with a heavy screening gate. The first step is a HackerRank-style assessment that mixes math or probability questions with a choice between a MATLAB route and a standard coding route. It is sometimes paired with a one-way HireVue asking why you want to join MathWorks. MATLAB-route questions are practical: visualization, loading files, indexing matrix rows and columns, and solving Ax=b. The coding route can include graph, interval, and DP problems, and one candidate found a DP question close to LeetCode hard.
Candidates who advance typically face a technical interview built around your own OA solution and resume projects. Interviewers ask you to explain your OA logic, time complexity, edge cases, and possible improvements. They then hand you a fresh LeetCode-style problem, usually medium but occasionally hard, sometimes alongside a low-level or object-oriented design question. One candidate had only about 20 minutes for the coding portion, so practice solving under a tight clock while talking through your approach.
Final rounds are commonly a roughly four-hour virtual loop split across technical, hiring-manager, and HR conversations. Behavioral questions cover missed deadlines, teammate conflict, and taking initiative. Expect practical questions too, about start date, salary expectations, and relocation. One EDG candidate got an open-ended prompt to design a controller for a system. Have a genuine, specific answer to 'why MathWorks,' since it came up repeatedly. In one successful process, a verbal offer arrived within three working days of the final loop, and the whole process took about two months.
Synthesized from 32 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the The Mathworks process.
I started with a technical coding assessment on an online platform that lasted about an hour. The questions were a mix of easy and medium difficulty, and I had plenty of time to work through them. The first problem was manageable, but I only got a partial solution on the second one — it was on the trickier side, though I don't think the difficulty alone was the blocker. The assessment included questions around sequences and data structures, and I remember having enough breathing room to think through my approach rather than feeling rushed.
After the coding round, there was a video interview component where I had to record responses to behavioral questions. One of them asked about my experience with object-oriented programming languages. The interviewers also mentioned they'd be asking me to walk through my thought process on the problems I'd solved in the assessment, which felt like a way to gauge how I explained my reasoning, not just whether my code worked. They seemed to care about how I articulated my approach.
Then things shifted toward my background. They asked detailed questions about projects on my resume, specifically around MPC and control-related topics. That caught me a bit off-guard — I was expecting more general software engineering questions, but they clearly wanted to understand the technical depth of what I'd actually worked on. Looking back, I wish I'd prepped more thoroughly on explaining the specifics of those projects and the math behind them, because that's where the conversation really dug in.
Prep tip from this candidate
Be ready to explain your thought process in detail for each coding problem you solve — they'll ask you to walk through it — and deeply understand the technical specifics of projects on your resume, especially any control systems, MPC, or domain-specific work. Have crisp explanations ready for both your approach and the underlying concepts.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at The Mathworks
Given two sorted lists, write a function to merge them into one sorted list.
| Question | |
|---|---|
| Hurdles In Data Projects | |
| Loan Model | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Random SQL Sample | |
| Minimum Change | |
| Raining in Seattle | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Rectangle Overlap | |
| The Brackets Problem | |
| Download Facts | |
| Employee Project Budgets | |
| Integer to Roman | |
| P-value to a Layman | |
| Find the First Non-Repeating Character in a String | |
| Employee Salaries (ETL Error) | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Google Maps Improvement | |
| Lowest Paid | |
| Find Bigrams | |
| Real-Time Transaction Streaming | |
| Level Of Rain Water In 2D Terrain | |
| Longest Increasing Subsequence | |
| Get Top N Frequent Words | |
| Binary Tree Conversion | |
| Target Indices |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates start with a HackerRank-style assessment that mixes math or probability questions with a choice between MATLAB problems and a standard coding route. One report also included DSA and MATLAB multiple-choice questions. Some candidates also complete a one-way HireVue with a 'why MathWorks' question. One candidate found a DP-style question genuinely hard but noted that plenty of time was given.
Candidates describe a short phone or manager screen, one of about 15 minutes. It covers resume follow-ups, a technical project, behavioral questions such as times you took initiative, and a company overview. One candidate described it as more of a vibe check than a deep interview.
The technical round opens with resume and project questions. Candidates then explain their OA logic, time complexity, and possible improvements before solving a new LeetCode-style problem live, usually medium and occasionally hard, including edge cases. Some reports add a low-level or OOP design question. One candidate had only about 20 minutes for the coding portion.
Candidates who advance describe a roughly four-hour virtual loop of technical, manager, and HR interviews. The manager and HR portions are behavioral, covering conflict, missed deadlines, fit, start date, salary expectations, and relocation. One EDG candidate also designed a controller for a system and discussed OA solutions.
One candidate who received an offer heard verbally within three working days of the final loop, followed by the formal offer; that process took about two months overall. One rejected candidate saw their portal status change to 'not a match this time.'
