Skip to content

MathWorks Interview Experiences

These MathWorks interview notes are rewritten from public student posts and prep-site summaries. Your panel can still look different.

Usual flow: Online assessment → Group discussion → HR → Managerial → Technical (order can vary; knockout)

EDG process mixes OA, GD, HR, managerial, and technical - often not in a fixed order.

Preferred language coding on HackerRank, OOPs, compilers/linkers, strong C basics, resume/CGPA discussion, projects.

Separate HR and managerial conversations (internships, why not higher studies, failure stories). GD topics like education policy appear.

Student report 1 - [gfg MathWorks edg on-campus fte] (2021)

Section titled “Student report 1 - [gfg MathWorks edg on-campus fte] (2021)”

CS vs Core track choice. Knockout rounds in any order after PPT: GD (new IITs topic), HR, managerial ‘conversation’, technical. Selected among FTE+6mo intern offers.

Student report 2 - [gfg MathWorks edg intern]

Section titled “Student report 2 - [gfg MathWorks edg intern]”

OA aptitude+2 coding+pseudocode → GD → HR (EDG role depth) → managerial → ~1.5h technical with live coding and C/OOPs fundamentals.

These notes come from public reports and can differ by campus, year, and role. If your college placement email or the official careers/notification PDF says something different, follow that.

After technical rounds, MathWorks usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.

Google · Microsoft · Intel · Siemens