Good company, but getting too process-intensive
Good company, but getting too process-intensive
Teams are small and extremely collaborative. Opportunity to work on challenging technical problems. Good work-life balance.
No work from home policy.
Becoming increasingly process-intensive over the past few years.
Conflicting demands on getting new, flashy features out the door versus updating legacy features that are in serious need of refactoring/redesign. The latter usually ends up being sacrificed for the former.
Lower salaries compared to similar tech companies.
Be careful with too much process; it often impedes people from getting real work done.
Provide more transparency on how decisions on feature prioritization and strategic direction are made.
Was this helpful?
MathWorks Interview Questions
MathWorks Interview Experiences
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 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
I was referred internally by a MathWorks employee. The overall process took about 3 weeks. I had a short phone call with a manager first and scheduled the on-site interview two weeks later. The interview started with a morning presentation about my
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 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 StatesJuly 1, 2014I was referred internally by a MathWorks employee. The overall process took about 3 weeks. I had a short phone call with a manager first and scheduled the on-site interview two weeks later. The interview started with a morning presentation about my
