Attended 3 out of 4 rounds for the Mechanical Engineering Co-Op. I had experience in Control Systems and working on it using Matlab and Simulink.

First round: You needed to video record answers for questions asked through an app or website. You had 2 attempts to record each answer. Questions were general, such as why you are interested in the position, why you think you are a good fit, your GPA, when you would graduate, and if you need visa sponsorship. There was also a question based on information provided before the questions appeared. You had 15-30 seconds to prepare for each response before recording began. It was quite simple if your resume and personal information were sorted out.

Second round: Coding Challenge. You needed to select two languages from the given options. Math was compulsory and easy enough if you knew linear algebra, ODEs, or similar topics (you would be notified). Language choices were C/C++ (combined), Java, Python, and Matlab. Time was allotted for each language separately. This challenge was online, conducted via a website with a built-in compiler. It included basic to intermediate programming questions on syntax, writing programs for specific calculations, patterns, or tasks. If you have experience with programming languages, it should be doable. Otherwise, you should try to learn two languages and complete assignments for about 4-7 days.

Third round: This was a technical interview. You logged into a TeamViewer-like environment where the interviewer typed programming questions, and you typed your solutions for them to see. Questions were on the same languages you selected earlier, though asking for different language questions might be possible. Simple math questions, including a few simple derivations, were also asked. Since you needed to select one Mechanical Engineering topic to work on at Mathworks, I chose Control Systems, as I had experience with it. You were asked about your knowledge of the subject and related projects listed on your resume.

Fourth round: This was likely an HR round. I did not make it to this round due to some incorrect programming solutions and silly mistakes in math questions.

Also, make sure to answer without taking too much time after a question is asked. I took time to work out solutions on paper, which was fine with the interviewer, but it took longer and made the interviewer feel I was searching for answers, even though some answers were incorrect.

The programming questions were unexpected for me. It appeared as if we could select either C or C++, and I had prepared well for C. However, the challenge required selecting C/C++, and the questions were mostly in C++.