MathWorks reviews

1. While work-life balance is promoted as one of the benefits, that's really only true dependent upon your manager, whether you're in development and if you are held in high regard by your manager and his/her superiors. 2. The company's core values imply an easy going, flatter organizational structure. Nothing could be further from the truth. The company is very hierarchical. Be aware of who the higher-ups are, and be smart about your interactions with fellow employees. 3. The review process is onerous, and ultimately unsatisfying. Self-reviews are part of the process, as is a lengthy review completed by your direct manager. Do not expect to be recognized for going above and beyond or for picking up difficult work that others won't or can't do. If you pick up such work and it impacts another area of your job or your "metrics", it will negatively impact your review. 4. Do not expect your review to reflect the type of raise or bonus you may receive. It's very likely you will receive a glowing review, and a small raise or bonus due to a variety of reasons: your stakeholder rating drives your bonus and raise amounts, not your review; there's is a complex compensation structure with defined limits particular to your staffing level, of which you are

Low salary. Company moves at a slow pace. The new grad program ("CSDG" / "EDG") is disappointing. At a high level this is a project rotation program combined with tech support, with the intention of transferring out after 1-2 years with strong product/customer knowledge. There are many problems with this program: -The position is advertised as 50% support 50% project. In reality it becomes 50% support and 50% other, where other is project, meetings, support cases left from last week, etc -The support weeks are rigidly scheduled at 8:30-5:30 with a 1 hour lunch break. If you want time for your project (e.g. a 1 hour meeting with your project team) you need to find someone else to cover you on the phone lines while you are away -Within the first 6-8 months you learn most of what you will get out of support, but you have to keep spending >50% of your time on support until you transfer out. -There is a ton of training built around support, and very very little training built around development -Some of the support cases are interesting, but many are just very simple questions that can be answered by looking at documentation -Transferring to a development team still requires going through the whole interview process as if applying from out of the company.