Phone screen: Behavioral interview - was asked to explain my PhD topic in layman terms.
Phone technical interview: Regular questions from the MathWorks list (memorize, memorize, memorize; you can't wing an interview that requires greater memory powers than intellect).
Onsite interview: I was accidentally assigned the same person as the phone interview. They swapped themselves for another interviewer. The new person was a smug youngster who unnecessarily made it a part-behavioral interview (the dude literally said, "Well, you got ahead of me there for an innocuous additional statement I made about a problem he posed."). The questions are super-easy if you memorize the right things. Be prepared for some architecture/C++ nuances, and you'll be good to go (that is, if you really want to work at MathWorks).
Explain the first-order hold on a given signal.
Direct Form-II versus Direct Form-I for a given filter (hard question if you didn't memorize what MathWorks expects you to memorize).
The following metrics were computed from 170 interview experiences for the MathWorks Applications Support Engineer role in Natick, Massachusetts.
MathWorks's interview process for their Applications Support Engineer roles in Natick, Massachusetts is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for MathWorks's Applications Support Engineer interview process in Natick, Massachusetts.