I applied online. I interviewed at MathWorks in Sep 2019
Interview
first one is OA an hirevue, about 5 video questions
then is an phone interview, about 1 hour
hr phone call, asking basic information, nothing tech
onsite, go to Natick
the whole process is fast and effective
I applied online. The process took 6 weeks. I interviewed at MathWorks (Natick, MA) in Oct 2019
Interview
1. Applied online through the online university recruiting form
2. Received request for pre-recorded video interview. Had 3 attempts to answer 5 questions, some basic HR (gpa, work status, etc.), some behavioral.
3. Was given an online coding assessment. Four questions of which you have to complete two within two hours
4. Phone interview with current engineer in EDG discussing an answer from the online coding assessment, making changes to the question, and then one basic OO design question.
5. Onsite interview that consisted of four rounds: a 2-hour technical interview, an interview with a manager in the EDG, lunch with two EDG engineers, and a final HR interview.
I received my offer within a day of the onsite, which was contingent upon a background check and professional references.
The online assessment consisted of two easy algorithmic problems and 2 medium algorithmic problems. The onsite technical interview included some basic probability questions, two medium algorithm questions, and one OO design question.
Overall, not a bad experience, just long. Everyone who interviewed me was kind and polite, I really enjoyed every conversation I had with all the different people at MathWorks throughout the whole process.
I applied online. The process took 4 weeks. I interviewed at MathWorks in Sep 2019
Interview
Started with a Behavioral Interview on HireVue, then HackerRank challenge, then phone technical interview. Behavioral was recorded video responses, coding challenge was pick 2 out of 4 questions, and the technical interview asked to explain code from the coding challenge and answer an additional question.
Interview questions [1]
Question 1
Explaining your code from the HackerRank challenge, analyzing runtime