Software Development Engineer In Test (SDET) Interview Experience
Process
First call with HM, discussion regarding the role, get an idea of my work.
Second call with the same person, this time it was a 1-hour technical round focused on OOP concepts, C++ programming skills, and MATLAB questions.
Third call with the recruiter, discussion about the role, salary, and interview process.
Final onsite interview: 45-minute presentation in front of a panel, followed by 5 interview rounds (45 minutes each). Four of them were technical, and one was behavioral. These rounds again focused a lot on OOP concepts, MATLAB questions, OOP in MATLAB, and domain knowledge in Robotics.
Questions
- Virtual destructor
- Loop closure in SLAM
- OO Design problems
- Unit testing debugging in Matlab
Was this helpful?
Interview Statistics
The following metrics were computed from 2 interview experiences for the MathWorks Software Development Engineer In Test (SDET) role in United States.
Success Rate
MathWorks's interview process for their Software Development Engineer In Test (SDET) roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having very good feelings for MathWorks's Software Development Engineer In Test (SDET) interview process in United States.
MathWorks Work Experiences
- 3.0Good starting companySoftware Development Engineer In Test (SDET) • Current EmployeeNovember 3, 2025Pros: Work-life balance Plenty of learningCons: Slow-paced Low salary rise
- 5.0Good Culture, Low PaySoftware Development Engineer In Test (SDET) • Current EmployeeJuly 12, 2024Pros: Good culture Free lunch Decent wlbCons: They don’t pay much. WLB can be bad once in a while too.
- 5.0Great Balance, Low SalarySoftware Development Engineer In Test (SDET) • Current EmployeeNatick, Massachusetts, United StatesDecember 14, 2022Pros: Work-life balance is great.Cons: Salary is a little low.
MathWorks Interview Questions
