MathWorks interview notes, page 1 of 5

“I fumbled the setup a bit.” The rest of the author's notes on Software Engineer interview at MathWorks, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went in thinking I could just tell a few decent stories and that would be enough.” The rest of the author's notes on Software Engineer interview at MathWorks, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The part that tripped me up was the trade-offs.” The rest of the author's notes on Software Engineer interview at MathWorks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The part that tripped me up wasn't describing the challenge, I had that ready.” The rest of the author's notes on Software Engineer interview at MathWorks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight into cycle detection without asking which variant they wanted, which was a mistake.” The rest of the author's notes on Software Engineer interview at MathWorks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I had an answer prepared but it felt a bit generic when I said it out loud.” The rest of the author's notes on Software Engineer interview at MathWorks, Recruiter / HR Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Said my piece, covered the usual projects and coursework.” The rest of the author's notes on Software Engineer interview at MathWorks, Recruiter / HR Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was brute force O(n^2) and I said so out loud, which I think was fine.” The rest of the author's notes on Software Engineer interview at MathWorks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The brute force answer basically writes itself, so of course they want you to do better.” The rest of the author's notes on Software Engineer interview at MathWorks, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I had an answer ready but it felt generic the moment I said it out loud.” The rest of the author's notes on Software Engineer interview at MathWorks, Recruiter / HR Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.