Matroid Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 20 interview experiences · FREE TO READ
Which role are you interviewing for?
6 roles · 20 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Matroid.
Matroid
Computer Vision Engineer
Mid Average Positive experience No offer 1 round
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical
They introduced themselves and then I introduced myself. Then they asked questions about my projects and basics of computer vision, ML and DL. Later they finish the interview after about 30 minutes.
Confirmed questions5 questions
- Can you describe an interesting project you've worked on?
- Tell me about your projects.
- Explain the fundamentals of computer vision.
Matroid
Software Engineer
Entry Difficult Neutral experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding
Had an online coding assessment on CodeSignal, which was proctored. There were 4 questions and 70 minutes to finish. It's like their standard proctored general assessment. The first two questions covered basic stuff like arrays. The next two were Leetcode medium difficulty. For the third question, you had to brute force it, but they told you how. The last question required you to figure out a clever and efficient solution on your own. If you don't know the solution right away or need to debug, you won't finish. The problems themselves weren't too hard, but I felt short on time. Matroid needs you to get all 4 questions right to advance.
Confirmed questions1 question
- Were there Leetcode medium questions, including one on 2D arrays?
Matroid
Backend Software Engineer
Entry Difficult Positive experience No offer 2 rounds
Interview process
Technical screen Technical screen
Interview formats
Coding Technical
So first, there was this Codesignal Assessment, it lasted 75 minutes and had 4 problems. After that, I had a 1-hour technical interview. The first part of that was a coding question where I had to modify some hypothetical code. The second part was a bunch of technical questions, mostly about networking and cloud stuff.
Confirmed questions5 questions
- Given a file storage system with slow but large disk storage and fast but small memory, how would you use the memory to speed things up?
- When is it appropriate to use threads versus processes?
- Compare and contrast TCP and UDP.
Matroid
Deep Learning Field Engineer
Entry Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Coding Behavioral
The interview process included three stages: first, a 30-minute chat focusing on resume details and fundamental ML concepts. Then, another 30-minute session covering resume points and basic ML topics (like CNNs, Linux commands, and explaining ML simply), plus a LeetCode coding challenge. Finally, an interview with the CEO.
Confirmed questions5 questions
- Can you tell me about CNNs?
- What Linux commands are useful for monitoring GPUs?
- Explain Machine Learning to a non-technical person.
Matroid Interview Questions
Quoted word for word from Matroid interview reports.
“Build binary search tree (including nodes)”
Read reports →“How do I count the number of islands in a 2D array?”
Read reports →“What Linux commands are useful for monitoring GPUs?”
Read reports →“Build program to make every third word uppercase”
Read reports →“Can you explain the difference between a Docker image and a Docker container?”
Read report →“Explain the fundamentals of computer vision.”
Read report →“Could you fine-tune a VGG classifier for a particular task?”
Read report →“Implement a grocery shopping list in React that lets you enter, delete, and cross off items.”
Read report →“Explain the fundamentals of deep learning.”
Read report →Formats, difficulty and experience
Across all 20 Matroid interview reports.