I spoke with the QE team manager in a one-hour, one-on-one interview. Then, I spoke with an HR person about MathWorks for about 30 minutes.
Next, I participated in a technical interview with a future team member regarding the use of the MATLAB test infrastructure.
Finally, I gave a 30-40 minute presentation on a technical topic and met several team members as well as two managers. I estimate about 8 hours of total interviewing time.
1st interview: Why MathWorks, what are you looking for, what are you passionate about, what's your experience?
2nd interview: This is what the MathWorks culture is like (no real "questions").
3rd interview: A basic overview of the MATLAB test infrastructure, and then some simple questions on MATLAB syntax, error messages, and seeing how quickly I learn something new.
4th interview: Basic verbal questions on how I'd sort something, or how I'd search for something in a large data structure. Some Simulink questions, like how to make a differential equation (more to see how fast I learn, rather than actually already knowing how to use Simulink).
5th interview: Then I also had open-ended questions on how I'd improve a product I use a lot, what kind of work would need to be done to support it, etc.
The following metrics were computed from 20 interview experiences for the MathWorks Software Engineer In Test role in United States.
MathWorks's interview process for their Software Engineer In Test roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for MathWorks's Software Engineer In Test interview process in United States.