Maze Fullstack Engineer Interview Questions
& Process

The interview process was great. Everyone I met was calm, kind, and had a thoughtful approach. First, there was an intro with talent and a meeting with the hiring manager. Then, a pairing interview with a straightforward exercise that led to in-depth conversations. Finally, a system design interview with a realistic problem, which was a collaborative discussion and gave a good idea of what working at Maze is like.

First I had a call with a recruiter who told me all about the company, the tech they use, and the teams. They explained each interview step super clearly, making it seem really organized. They even sent me study stuff beforehand. After that, I had a tech interview with one of the developers. We did a live coding thing in React, which was pretty simple, just fetching and showing data. They mostly wanted to chat about React and frontend development, which was cool. The next part was a Karat interview, done by an outside company. It felt like a timed test. First, I picked two subjects from a list and answered three questions for each. Then, there were two coding problems: one was about refactoring a function with new JS syntax, and the other involved some object-oriented code where I had to explain an error. Finally, there was an algorithm challenge. I got rejected a week later, but the next step was supposed to be a chat with the CTO.

I really liked the whole interview process. It's more about testing product-building skills than just algorithms. It started with a brief chat with HR, who was super helpful throughout. Then, there was a tech interview where I had to do a straightforward data fetching task, which took about 15 minutes to code, followed by discussions. After that, I had an interview with Karat, who assess fundamental programming abilities. You get to pick from subjects like testing, frontend, and so on, which I thought was great because it didn't feel like they were trying to trick you. The last interview was with the CTO, and it was more of a high-level chat about how to build a specific feature on their platform.