I applied through an employee referral. The process took 7 weeks. I interviewed at MathWorks (Natick, MA) in May 2016
Interview
Applied via employee's reference. Had two phone screening and one on-site interview.
In the first phone screening, I was asked about experiences on my resume and simple questions about programming languages they used.
Before the second phone screening, I was asked to write a simple code. The second phone screening was a discussion about the code I wrote.
The on-site interview started with a presentation about a project I worked for before, followed by 1:1 interviews (including one with an HR) and lunch with team members. They asked questions about my experiences based on the presentation and some more technical questions.
Preparing presentation was time consuming (it took a week for me) but you can lead the topic of interviews because 1:1 interviews are based on presentation.
I applied online. The process took 4 days. I interviewed at MathWorks in Apr 2016
Interview
1. Online Hr round. Its a pre-recorded video interview. You will be asked behavioral questions in it. They give the option to practice some of the questions before you start. It helps a lot. For 3.5 CGPA was the must.
2. coding challenge.
Interview questions [1]
Question 1
1. Its basic HR questions.
2. You can choose your own language for this test
I applied through college or university. The process took 1 week. I interviewed at MathWorks in Dec 2015
Interview
The interview consisted of mostly general Java programming questions, such as inheritance and polymorphism. Additionally, I was given the opportunity to choose between web development and C++ for the second part of the interview. For the web development section, I was asked basic questions on Javascript and HTML. Lastly, I was given logic problems on on tautologies. Overall the interview was very laid back and my interviewer was friendly.
Interview questions [1]
Question 1
Program a class that extends another class and overrides its methods. Say the expected output of running each method based on what was overridden.