Round 1 - Hiring Manager (30 mins) Discussion about the current project and the roles and responsibilities for the open position.
Round 2 - Offline problem-solving (1 day to submit solution) An offline C++ code was provided, and the task was to improve its runtime by at least 100 times. The task was completed within 6 hours.
Round 3 - Technical Screening (1 hour) C++ questions:
Round 4 - HR (45 mins) Discussion about education, work experience, reasons for leaving previous roles, and career aspirations.
Round 5 - HR (45 mins) Behavioral questions. Discussion about salary and benefits at Mathworks.
Round 6 - Presentation (1 hour) Prepared and presented previous work with in-depth technical architecture. Questions were based on the project.
Round 7 - Technical Round (45 mins) C++ based questions. Implemented a Circular Queue using a fixed-size array.
Round 8 - Technical Round (45 mins) C++ based questions. Problem-based shuffle of elements in an array.
Round 9 - Technical Round (45 mins) Interviewer shared Polyspace code (a Mathworks product) and asked to identify potential issues.
Round 10 - Hiring Manager (45 mins) SURPRISE! HR sent all invites for a Team Lead role, and I presented myself as a candidate looking for a Team Lead position. However, the hiring manager expressed uncertainty about how the HR published the Team Lead role, as they were looking for a Senior Software Engineer candidate who could be an individual contributor. He then asked me to justify my suitability for the Senior Software Engineer role. I was shocked but still attempted to present my case, though I am unsure if I was convincing.
Basic DS and Algo and OOPs.
The following metrics were computed from 1 interview experience for the MathWorks Performance Engineer role in India.
MathWorks's interview process for their Performance Engineer roles in India is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for MathWorks's Performance Engineer interview process in India.