Interesting company, interesting products – not for everyone, though, and they are proud to have it this way
Interesting company, interesting products – not for everyone, though, and they are proud to have it this way
There are a lot of smart people here.
Despite its flaws, the software is amazing.
Interesting culture if you fit in. Be prepared to drink the Kool-Aid or don't come here.
Pleasant work environment.
Very stable company.
FAR too much process.
MathWorks is a Linux shop, but the lion's share of its customers are Windows and Mac, so MathWorks engineers, by and large, do not understand their customers, and it shows in the software.
Internal development tools are Unix-based regardless of your platform. This means that you can't leverage tools that would make you productive on your platform, for example, Visual Studio and Xcode.
The MathWorks Build-and-Test (BaT) system is more of a hindrance than a help.
Minor/local decisions are frequently passed up the management hierarchy to VP or CEO level. This is a tremendous waste of an incredible talent pool.
Absolutely no telecommuting. At most 3 days per year.
Lots of lip service to collaboration, but not so much in practice.
To the CEO and Senior Managers:
Even though the organization chart shows a decent hierarchy, the company frequently doesn't work in a hierarchical fashion. With small decisions escalating to the CEO, the incredible talent here is largely wasted.
The purpose of hierarchy is to isolate and effectively harness the skills of your workforce. The CEO and senior managers manage the company the way it was managed in the early days – that is, hands-on with everything.
Does the CEO really need to dictate the precise layout of icons on the conference room computers? Managers and CEO, focus on what you do best; let your employees focus on what they do best.
Was this helpful?
MathWorks Interview Questions
MathWorks Interview Experiences
Senior Software Engineer
I interviewed with two teams. For the first team, I came in for a two-hour on-site "half day." However, I was not found to be a suitable match. The half-day consisted of four 30-minute sessions with team members, where I answered typical software an
Senior Software Engineer
The process was very time-consuming but still pleasant. This was the process: * 1-hour technical phone screen with the manager. * Complete a coding project. I was given a week, and it took me around 10 hours. I could have done it in less, but it was
Senior Software Engineer
I had two phone interviews before having the chance to fly to Natick, MA. The interviews covered many details, including C++, threading, mutex, new/delete, and design questions. You need to prepare your presentation well and convince everyone that
Senior Software Engineer
Natick, Massachusetts, United StatesFebruary 1, 2018I interviewed with two teams. For the first team, I came in for a two-hour on-site "half day." However, I was not found to be a suitable match. The half-day consisted of four 30-minute sessions with team members, where I answered typical software an
Senior Software Engineer
Natick, Massachusetts, United StatesJune 1, 2018The process was very time-consuming but still pleasant. This was the process: * 1-hour technical phone screen with the manager. * Complete a coding project. I was given a week, and it took me around 10 hours. I could have done it in less, but it was
Senior Software Engineer
Natick, Massachusetts, United StatesMarch 1, 2012I had two phone interviews before having the chance to fly to Natick, MA. The interviews covered many details, including C++, threading, mutex, new/delete, and design questions. You need to prepare your presentation well and convince everyone that
