These are only my personal opinions after half a year in MW.
These are the cons that are specific to my department:
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.
The reviewing process is VERY unclear. They would tell you everything they would consider but not exactly how they review you (basically, nothing useful).
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.
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.
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.
Simple HR 20-minute phone interview, which was pleasant and easy. Then, a week later, I scheduled a 40-minute technical phone interview. Fairly basic questions were asked: * What are linear differential equations? * Explain exception handling in C+
1st phone call: Technical rapid-fire questions. On-site: * Write code for drawing an arc of a circle. * Check if a number can be expressed as 2^a + 2^b. * Find errors in code. * Predict output. * Explain the steps from source file to exec
The process took about 2-3 weeks. I applied online. The first round was an HR round. You will be asked a few general questions, such as: * Why MathWorks? * Tell me about a situation where you handled multiple complex tasks. * Justify your GPA. Thi
Simple HR 20-minute phone interview, which was pleasant and easy. Then, a week later, I scheduled a 40-minute technical phone interview. Fairly basic questions were asked: * What are linear differential equations? * Explain exception handling in C+
1st phone call: Technical rapid-fire questions. On-site: * Write code for drawing an arc of a circle. * Check if a number can be expressed as 2^a + 2^b. * Find errors in code. * Predict output. * Explain the steps from source file to exec
The process took about 2-3 weeks. I applied online. The first round was an HR round. You will be asked a few general questions, such as: * Why MathWorks? * Tell me about a situation where you handled multiple complex tasks. * Justify your GPA. Thi