MathWorks' product is well established, and the company has really good financial performance. Great people are around. The product development process is rigorous. As a developer, you need to have a formal, written definition of the requirements, and it has to go through internal reviews before you can start writing a single line of code. Good documentation supports this. It's a great place to learn software development. It seems to be very stable at MathWorks. People around stay for 10 years or more!
Standard big company, with lots of meetings to attend, even if it's not relevant to you. I have worked in the UK office, and a large portion of your time is spent making phone calls with people in the MathWorks US office, trying to explain what your code means. Or the other way around, when you have problems using others' code. People stay there for long, which means it's hard to have a change there. My manager there has been a developer for 9 years before transferring to his management role. Another QA guy has been there for 5 years. These are actually young guys in the office. There are ones who have worked for MathWorks for 20 years.
MathWorks is actually quite friendly to graduates. They have regular open events where students attend. I attended their open day event and then chatted with various people there. I handed my CV to a person and introduced myself. The next day, I rec
Managed to get through the first round of phone interview, where I was asked a series of standard questions, e.g., leadership skills, coding experience, time management skills, and visa status. I was also given the chance to ask questions about the
The interview process was pretty relaxed. Here's a breakdown of the stages: * There was a code test online, including maths and programming. * Then, I had to submit an extended response regarding my motivations. * Next, there was a technical
MathWorks is actually quite friendly to graduates. They have regular open events where students attend. I attended their open day event and then chatted with various people there. I handed my CV to a person and introduced myself. The next day, I rec
Managed to get through the first round of phone interview, where I was asked a series of standard questions, e.g., leadership skills, coding experience, time management skills, and visa status. I was also given the chance to ask questions about the
The interview process was pretty relaxed. Here's a breakdown of the stages: * There was a code test online, including maths and programming. * Then, I had to submit an extended response regarding my motivations. * Next, there was a technical