HR Interview (~15 minutes), Technical Interview (45 minutes), Onsite Interview (2 hours technical + discussions with 2 HR staff).
In terms of the overall structure of the interview process, it was very standard. You should expect some typical behavioral interview questions.
The technical interviews had an unusual emphasis on knowledge of syntax instead of knowledge of programming concepts. I'm not saying it's unacceptable to do that, but be prepared for these interviews as they were not like any of my other software engineer interviews.
There were some math questions, and my choice of two from C/C++, Java, Web Dev, of which I chose the former two.
Questions touched on:
Pigeonhole Principle
NFAs/DFAs
Basic Set Theory
Probability/Counting
Virtual Functions
Structs, Classes
Pointers, References
Stacks
Arrays
Basic OOP concepts (inheritance, encapsulation, recursion, polymorphism)
Storage Classes
Inline Functions
How NULL differs in different languages
JRE and JDK
Garbage Collection/Memory Management
Definitions/Import (Typedef, Meaning of #, <>, "")
Scope
Searching/Sorting algorithms
Call by Value vs by Reference
Break vs Continue
Exception Handling
A lot of questions involved being presented with egregiously erroneous or incorrect code and expected to be able to tell what they do and how certain fixes would change that.
They gave a few examples of code where many variables were given the same name in different scopes or different classes that form some hierarchy, and then asked what a test driver accessing variables by those names would do.
I later found by testing by hand that I did not completely answer these correctly, but I don't know why they would penalize me for not being able to answer questions about something I could figure out in a few minutes if I were on a computer at the time.
It is at least my opinion that there was too much emphasis on questions where I was not asked to write any code or design an algorithm. Obviously, a programmer should also have knowledge of the basics, but is the goal to find someone who can regurgitate definitions from a textbook or someone who writes code?
I can't remember all the questions right now, but the above description is pretty thorough regarding the style and topics of questions they asked.
The following metrics were computed from 29 interview experiences for the MathWorks Associate Software Engineer role in United States.
MathWorks's interview process for their Associate Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for MathWorks's Associate Software Engineer interview process in United States.