Embedded Software Engineer In Test Interview Experience - Natick, Massachusetts
Process
I applied online and had my first phone interview with a software engineer who asked many questions about C/C++, data structures, and Matlab, lasting about 30 minutes. Two days later, I had a second phone interview with an embedded systems engineer, focusing on RTOS and scheduling algorithms. Three days after that, I was invited for an onsite interview.
The onsite interview began with a 45-minute presentation of my background and work experience. Afterward, I had one-on-one interviews with two software engineers, one embedded systems engineer, the team manager, and HR. The onsite process was quite extensive, running from 9 am to 4 pm. The most frustrating part was that they took over a month to get back to me, which was abnormally annoying.
Questions
What is data alignment?
Analysis interrupt in ROTS.
Composition in C++.
Template in C++.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the MathWorks Embedded Software Engineer In Test role in Natick, Massachusetts.
Success Rate
MathWorks's interview process for their Embedded Software Engineer In Test roles in Natick, Massachusetts is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for MathWorks's Embedded Software Engineer In Test interview process in Natick, Massachusetts.
MathWorks Work Experiences
- 4.0Good experience overallAssociate Engineer • Current EmployeeNatick, Massachusetts, United StatesNovember 26, 2025Pros: Good benefits Good work-life balanceCons: Could be a bit more pay.
- 1.0Business Apps Department | No Importance to Quality, Skill Development | Traditional ApproachSenior Web Applications Developer • Current EmployeeNatick, Massachusetts, United StatesNovember 25, 2025Pros: Free breakfast and lunch. Generally good work–life balance. The Engineering / Product departments seem to have better projects that support skill growth and career development. I honestly can’t think of any pros specific to the Business Apps department.Cons: Obsession with “velocity” and delivery metrics, often at the expense of real value. Claims to follow Agile, but in practice there is very little focus on process, quality, or the end customer. Some managers lack basic professional communication etiquette and tend to be controlling and micromanaging, which makes the team environment stressful. Roles and responsibilities are unclear — there is no real separation between manager, scrum master, and product owner. Below-market pay for a full-stack developer. Very few (if any) projects that actually help with skill development or long-term career growth. Traditional and backward approach to the SDLC, resistant to modern best practices.
- 4.0Good work-life balance, stable but slow career growth, low compensationSoftware Engineer • Current EmployeeNatick, Massachusetts, United StatesNovember 20, 2025Pros: Good work-life balance. Job safety. Nice colleagues.Cons: - Slow career growth - Low compensation - Shrinking project opportunities in Online Product org
MathWorks Interview Questions
