My interview experience with MathWorks was very pleasant.
The process lasted around 6 weeks, from mid-May to June 2019.
The first round was based on my resume.
Following this, there were two technical screens: one video and one phone call.
After that, there was a short HR call where I was asked generic behavioral questions. During this call, I was informed that they wanted me to come on-site.
I had to prepare a 45-minute presentation on any previous project.
After the presentation, I had three technical interviews (around 50 minutes each) and one HR interview.
I received a call the next day to inform me that they were proceeding with my reference and background check.
I received my offer letter the day after these checks were completed.
Overall, the process was pretty fast, and the HR was very responsive.
No fancy algorithm questions.
Have a thorough knowledge of the ins and outs of the language you choose.
OOPS-based questions:
Asked about different keywords: auto, static, const, etc.
Heap & stack memory.
How a source code is built (preprocessor -> compiler -> linker).
The coding questions were pretty basic. Some "What is the output" type questions.
The following metrics were computed from 17 interview experiences for the MathWorks Software Engineer role in Natick, Massachusetts.
MathWorks's interview process for their Software Engineer roles in Natick, Massachusetts is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for MathWorks's Software Engineer interview process in Natick, Massachusetts.