The project work is often very engaging. Many colleagues are very smart and carry their weight in projects. It's awesome to see thousands of customers using the products.
There are plenty of unofficial leadership opportunities, but since MathWorks has such a flat hierarchy, there are limited opportunities for promotion to leadership positions if you start as an individual contributor.
The hiring process for me was as follows: * It started with an initial email from the recruiter. * A phone interview with the hiring manager. * A phone interview with a colleague. * An onsite interview, which included a presentation followed by inte
This was a while ago, so I don't remember exactly. There was an online coding question, and then a phone call along with a few coding questions. One was an algorithm question, and one was to design an object-oriented model.
Referral. Many phone interviews, then a small project and more interviews. They showed what they were working on. There was a lot of overlap between interviews, and it looked like they were just passing the time.
The hiring process for me was as follows: * It started with an initial email from the recruiter. * A phone interview with the hiring manager. * A phone interview with a colleague. * An onsite interview, which included a presentation followed by inte
This was a while ago, so I don't remember exactly. There was an online coding question, and then a phone call along with a few coding questions. One was an algorithm question, and one was to design an object-oriented model.
Referral. Many phone interviews, then a small project and more interviews. They showed what they were working on. There was a lot of overlap between interviews, and it looked like they were just passing the time.