Candidatei-me online. O processo levou 2 meses. Fui entrevistado pela MathWorks em mar. de 2025
Entrevista
Very streamlined process, applied somewhere in the beginning of February and immediately got an OA, which consisted of 2 LC type questions (one graph based, and the other based on intervals) and Matlab MCQ questions. Later was contacted by the manager to schedule a quick 15 minute interview where she talked a bit about the company and asked BQ + some questions about resume. The last round included 3 back to back interviews over 4 hours (Technical-> Manager -> HR). Technical round involved an OOP based question and a LC styled question along with some questions about projects. The next two rounds were strictly behavioral based. The interview process was very smooth! Received a verbal offer within 3 working days followed by the formal offer. Whole process took around two months.
Perguntas de entrevista [1]
Pergunta 1
Explain one project from your resume that you worked on.
Candidatei-me online. Fui entrevistado pela MathWorks (Boston, MA) em abr. de 2023
Entrevista
Two hard questions in the on-site interview, do they really want to hire people? They expect you to write two hard leetcode problems within half an hour, which is impossible.
Perguntas de entrevista [1]
Pergunta 1
very hard problems which do not come from Leetcode
Candidatei-me online. O processo levou 6 semanas. Fui entrevistado pela MathWorks em jul. de 2022
Entrevista
I spoke with the QE team manager in a 1hr 1-on-1 interview. Then, I spoke with an HR person about MathWorks for 30 minutes or so. Then I took a technical interview with a future team member on using the MATLAB test infrastructure. Finally, I gave a 30-40 minute presentation on a technical topic, and met several of the team members as well as two managers. I'd say about 8 hours total of interviewing time.
Perguntas de entrevista [1]
Pergunta 1
1st interview: why mathworks, what are you looking for, what are you passionate about, what's your experience? 2nd: this is what the mathworks culture is like (no real "questions") 3rd: a basic overview of the MATLAB test infrastructure, and then some simple questions on MATLAB syntax, error messages, and seeing how quickly I learn something new 4th: basic verbal questions on how I'd sort something, or how I'd search for something in a large data structure. some Simulink questions like how to make a differential equation (more to see how fast I learn, rather than actually already know how to use Simulink). 5) Then I also had open-ended questions on how I'd improve a product I use a lot, what kind of work would need to be done to support it, etc.