Wicked smart people. Stable. Personal offices, with good equipment. Nice campus, good expected company growth. Ability to weather tough economic storms. Advanced use of programming languages to solve difficult problems. Good atmosphere. Flexible with core hours. Great coworkers, some of the brightest around, and very polite/respectful.
To ensure quality, getting code into the final product is a long and painful process. This leads to great, quality, low-bug products, but slows down programmers. It's a necessary pain for the end result; just be aware that slowdowns in development exist and can't be avoided.
Telecommuting policy is lagging behind where modern software companies tend to be.
Overall, people love the company and its products.
Find ways to reduce the drag on programmers' time getting code in without sacrificing product quality. Everyone respects quality is #1; just focus on ways to get programmers to get code in safely at a faster rate.
The environment is great, but we need to vastly improve the telecommute policy.
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.
I was referred internally by a MathWorks employee. The overall process took about 3 weeks. I had a short phone call with a manager first and scheduled the on-site interview two weeks later. The interview started with a morning presentation about my
The interview process typically involves phone screens by a recruiter and hiring manager. This is followed by a presentation to the team and higher managers. Next, there is a full day (or two half-days) of interviews with the hiring manager and team
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.
I was referred internally by a MathWorks employee. The overall process took about 3 weeks. I had a short phone call with a manager first and scheduled the on-site interview two weeks later. The interview started with a morning presentation about my
The interview process typically involves phone screens by a recruiter and hiring manager. This is followed by a presentation to the team and higher managers. Next, there is a full day (or two half-days) of interviews with the hiring manager and team