Pros: 1. Some part of the outside world thinks you are working on a well-known product. 2. If you are interested specifically in using MATLAB/Simulink to solve MATH/Engineering problems, you might enjoy the job. 3. Good work-life balance. You are working based on a fixed schedule; there is no flexibility, but also no overtime. 4. There are many smart and nice people working here. 5. Part of the benefits is good, e.g., 401K match, unlimited sick days, and there are some nice small perks.

Cons: The cons part is only for EDG, and more specifically it is for the experience of computer science people in EDG. 1. MathWorks’ pay to ASE role might not be that bad compared to many mid to small-size companies, but it is still much lower than most large software companies. 2. If your career goal is to do software development, don’t have very high expectations for the EDG program, because it is mainly a technical support role. EDG is part of the technical support department, and your technical support job always has higher priority than all of your other tasks in EDG. Most managers will purposely avoid this fact when they talk to you before you join. 3. MathWorks is an extremely procedural company, so for anything you do, there will be some step-by-step documentation, which is good for many people. However, for some reason, they never make the procedure of transferring out of EDG to a development role clear. The time you spend at EDG actually depends on the number of opening positions in other parts of the company, and they do over-hire sometimes. When this happens, again, your manager will avoid the fact and tell you to not focus on whether there are any open positions, but to focus on improving yourself so an opportunity will come to you. 4. The performance review process is very unclear and inconsistent. The performance rating is from 1 to 6 points, and I have seen someone get praised by his manager and promised a raise, while someone from the same team with a rating just 0.5 lower got warned by the same manager that his career is at risk. 5. Most managers are not from the appropriate technical background, so do not expect them to help you much from the technical perspective. The management is highly technical support oriented, and if you say you have a computer science degree and are very good at software development, your skills will not be much appreciated here. 6. The expected amount of bonus for new hires listed on the hiring material that HR gave to me was way higher than the bonus I actually received, and since all new hires get the same amount of bonus regardless of performance, the information from HR was just not true. 7. Some actions from management are questionable in terms of work ethics. Managers use the threat of not filing working visa applications to push engineers.

Pros: These are only my personal opinions after half a year in MW. 1. Benefits are sort of competitive. There are rather frequent social gatherings across departments. 2. Everybody, I mean literally everybody, in my department is nice and helpful. Great dynamics in the team. 3. The training process is smooth and helpful. You would find yourself quickly improving along the process. 4. Overall work-life balance. Light workload for most of the time.

Cons: These are the cons that are specific to my department: 1. While the ASE department (i.e., the technical support department) has good working dynamics overall, you would sometimes find yourself in difficult situations when dealing with the actual development team. You could definitely feel their attitude toward you because you were just trying to hang out with them for the purpose of transferring to their team. 2. The reviewing process is VERY unclear. They would tell you everything they would consider but not exactly how they review you (basically, nothing useful). 3. The transfer process is totally random and uncontrollable. This is kind of frustrating because you are sometimes good enough for a team, but there is just no opening. This encourages turnovers frequently. 4. The position essentially means you will provide customer service while doing some corner project works for other people. However, I felt it was described as mostly doing projects when you occasionally write people emails. This is not communicated well in the interviews. Not that they were trying to lie to you or hide it. When they have been in the company for a long time, they might have different views on how much time the technical support work would take. But you will be the TECHNICAL SUPPORT; you will pick up phone calls for a large portion of your time. DO NOT assume the support part of your job is negligible. 5. Not trying to be an *hole here, but the percentage of a certain nationality has been increasing. You would notice a lot of them are actually friends who know each other. Yes, referral has its magic here, but the current situation is too much. I mean, like 70% of the new hires are from a particular country. I don't have the evidence to say that the hiring process is rigged or something, but the company needs to investigate it. Mathworks has a limited interview question pool, which makes this even more suspicious. Overall, I think it is a great position for you if you are from an engineering-related area and want some super entry-level job to get onramp to software engineers. If you already have enough development experience, this might not be a good place for you to improve yourself. Mathworks is a good place for you to stay for the rest of your life, so if you are ready to commit in the long term, this is also a good position for you.

Pros: Great team structure. Good work ethics. Nice group engagements.

Cons: Not a lot of growth. Natick is not so happening.