Round 1: The first interview was with the software manager. It was code-based, which wasn't communicated until the actual interview. Questions focused on classes, structs, and pointers.
Round 2: The take-home coding problem involved developing a buffer for a text-editing tool.
Round 3: A conversation with the Senior Technical Recruiter covered salary expectations, immigration topics, and the next steps in the interview process.
Round 4: The on-site interview included a presentation of a project I had done, followed by four rounds of interviews and a final talk with the Senior Technical Recruiter.
Overall, everyone was friendly and nice. I was quite nervous and stumbled on some questions. When I was stuck or had questions, the interviewers guided me in a non-condescending manner.
I recommend studying everything on Glassdoor and practicing on LeetCode extensively. The presentation is also very important, so if you get an on-site interview, ensure you are well-prepared, especially for answering questions. Many quick programming questions, such as those on time complexity, are available on Glassdoor.
Difference between a directed acyclic graph and a binary search tree?
What would Reference1 say is your greatest strength?
What would Reference2 say is your greatest weakness?
Find the maximum contiguous sum in this array.
The following metrics were computed from 148 interview experiences for the MathWorks Software Engineer role in United States.
MathWorks's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for MathWorks's Software Engineer interview process in United States.