I have been working at MathWorks for a decade now. Overall, it is a good company with lots of good and smart people. There is a decent work-life balance. When working at MathWorks, you have the opportunity to help create something that scientists and engineers will use to make the next big discoveries.
There are some very bad apples at MathWorks. These are incompetent people, who are in middle management only because they joined the company early on, and MathWorks values loyalty more than competency.
Some of these managers suffer from an inferiority complex because they can clearly see that they are not as competent as the people they pretend to manage. My manager is one such person. If there is any issue, he likes to blame it on others and does not take responsibility for the overall quality of the product or its direction. His people skills are as abysmal as his technical skills.
He often talks badly about other people in the team when talking with me, and I am sure he badmouths me behind my back. Even though it is clear that the product that he is managing is going nowhere and is stuck in time, MathWorks rewards his loyalty by letting him continue.
He also insults people in team meetings and is blatantly sarcastic. He routinely comes late to one-on-one meetings or skips them altogether and pretends as if nothing happened. His demeanor is aggressive.
Some of the things that he is doing may be corporate bullying, but complaints from people go unheeded. As a result of his bad treatment, many people have left the team in the last few years. I think some people have made this known to the senior management, still, there is no action. I will leave as soon as I get a good offer.
People interviewing at MathWorks should avoid such teams. If you are observant during the interview and ask the right questions, you will be able to figure out if you are interviewing with such a team.
Recognize such people and take action.
Talk with manager. Talk with colleagues. Practice coding problems (e.g., LeetCode). Review C++ knowledge. Talk with HR and manager again. Discuss the offer and all details with HR. Accept the offer. You have three days to consider it.
1. Initial phone interviews 2. Video interview 3. Interactive coding test 4. Presentation of work to the hiring team, followed by multiple interviews with individual members of the hiring team (6-hour day).
After initial screening, I spoke with the manager and HR. This was followed by a virtual, day-long interview that included a 45-minute presentation. They asked me to send my slides for feedback. I did, and they suggested adding more of my 3D work.
Talk with manager. Talk with colleagues. Practice coding problems (e.g., LeetCode). Review C++ knowledge. Talk with HR and manager again. Discuss the offer and all details with HR. Accept the offer. You have three days to consider it.
1. Initial phone interviews 2. Video interview 3. Interactive coding test 4. Presentation of work to the hiring team, followed by multiple interviews with individual members of the hiring team (6-hour day).
After initial screening, I spoke with the manager and HR. This was followed by a virtual, day-long interview that included a 45-minute presentation. They asked me to send my slides for feedback. I did, and they suggested adding more of my 3D work.