MathCo logo

MathCo Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 5 interview experiences · FREE TO READ

2 Rounds average
Average Typical difficulty
80% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at MathCo.

Showing 3 of 5
MathCo logo
MathCo

Engineer

Engineering · nearly a year ago

Entry Average Positive experience No offer 1 round
Interview process
Technical screen
Interview formats
Case Technical Behavioral

The interview started off with a case study that had four questions that tested problem-solving and reasoning skills. After that, we had detailed discussions about my projects, with a special focus on machine learning, to show my technical depth and how I apply it in practice.

Confirmed questions1 question
  • Tell me about a case study concerning KPIs.
MathCo logo
MathCo

Product Engineer

Engineering · a year ago

Entry Average Positive experience No offer 2 rounds
Interview process
Technical screen
Interview formats
Technical Coding Behavioral

It was a good interview process with 2 rounds. Each round had a DSA question and resume-based questions. They also asked logical thinking questions. I think they're more likely to hire someone good at Python, LLM training, chatbot development, AI, ML, etc.

Confirmed questions1 question
  • Rate yourself in Python, LLM training, chatbot development, and DSA.
MathCo logo
MathCo

Product Engineer

Engineering

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral

I applied for the Product Engineer II - Backend job on LinkedIn. About a week later, the hiring manager contacted me, confirmed my application details, and scheduled a follow-up call for two days later. I was informed that there would be three interview rounds: two technical and one HR. The first technical round involved discussing my past work experience and then solving two coding problems – one easy and one medium. I managed to solve the easy one but struggled with the medium problem. The second technical interviewer seemed confused about the role, asking frontend-related questions despite my application being for a backend developer position. When I pointed this out, they mentioned it was a Fullstack role, which I had to correct them on, stating that wasn't the case. The hiring manager had initially told me to prepare for backend technologies and even sent an email listing the required tech stacks. I discussed the discrepancy with the hiring manager, who acknowledged the unfairness and promised to address it. However, I never heard back. Ultimately, I received a rejection email even before the interview concluded. It seems like some interviewers treat this process as a minor task rather than a significant opportunity for the candidate, which makes for a terrible experience, arguably the worst I've encountered.

Confirmed questions3 questions
  • Can you tell me about your previous work experience?
  • Solve the 'Valid Parenthesis' problem, which is a Leetcode question.
  • I need you to solve a problem involving nested JSON data manipulation.

MathCo Engineer Interview Questions

Quoted word for word from MathCo interview reports.

What would this pseudocode output? ' ' * 10 is assigned to value, then print value.

Read reports

Solve the 'Valid Parenthesis' problem, which is a Leetcode question.

Read reports

Can you tell me which data structure offers O(1) time complexity?

Read reports

Formats, difficulty and experience

Across all 5 MathCo interview reports.

Interview formats

Technical 33.3%
Coding 33.3%
Behavioral 25%
Case 8.3%

Interview difficulty

Easy 40%
Average 60%
Difficult 0%

Candidate experience

Positive 80%
Negative 20%