
DoorLoop Fullstack Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 7 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at DoorLoop.
Full Stack Developer
The interview process at this company was quite unprofessional. It started with an HR interview on Zoom where I was immediately hit with 10 React questions before I could even introduce myself. The HR person was late because she forgot about the meeting, and I had to call her to remind her. Then there was a one-hour frontend interview on Zoom, which felt like the interviewer didn't want to be there. After that, a three-hour backend interview took place on-site. The team lead gave me a task but hadn't checked if the code worked, and it failed to run due to a MongoDB connection issue, which I had to fix. The code was also old and used weird libraries. Later, a TypeScript error popped up, which the team lead couldn't fix, so I had to resolve that too. Despite solving the exercise, I was rejected, with reasons like my English or another candidate being faster, ignoring the bugs in their system. The HR person was nice, but the rest showed major issues: unprofessional interviewers, outdated practices, and messy offices. It seemed like they were trying to look more advanced than they are.
- Asked 10 React questions, hooks, etc.
Senior Full Stack Engineer
The interview process was **pretty fast**. First, I had a **Zoom call** with the recruiter. They sent over a **13-question questionnaire** on React and TypeScript, which was kind of odd. We also talked about **expectations** and the company. Then, my **first interview** was a **live frontend coding session**. After that, the **second interview** was **onsite** and involved **two hours of backend coding** and **one hour with the VP of R&D**. The **technical interview** focused on **adding an audit log** to **MongoDB** with **TypeScript**, integrating it with the **user model** for `create/update/delete`. I needed to **define the model structure** first, then code. Since I hadn't used **MongoDB** or **TypeScript** schemas in **years**, I **didn't quite finish** but was **very close**. The chat with the **VP of R&D** was **very general**, covering **my background**, an **architecture I'd built**, **database indexes**, and **personality questions**. The conversation was **great**. I'm **bummed I didn't pass**, but the process was **really well-organized, clear, and efficient**.
- For the first interview, which was a live frontend coding session, how would you implement `useKeyboard` – a custom hook that calls a callback using a keydown event listener on the window?
- How would you handle `TransactionType` using a TypeScript enum and an object instead of a switch case?
- How would you implement `TimerBox`, a countdown component, using React hooks?
Full Stack Developer
First, I had an online chat with HR. She asked me ten questions on JavaScript, TypeScript, and React. Then, in the second interview over Zoom, I was given a task to do in React.
- Could you implement a delay function?
- Can you explain what primitive types are?
DoorLoop Fullstack Engineer Interview Questions
Quoted word for word from DoorLoop interview reports.
“What's the reason we can't put hooks inside conditions in React?”
Read reports →“How would you implement `TimerBox`, a countdown component, using React hooks?”
Read reports →“What is Web Storage?”
Read reports →“How do React hooks work?”
Read reports →“What are the different types in JavaScript?”
Read report →“How would you handle `TransactionType` using a TypeScript enum and an object instead of a switch case?”
Read report →“Can you explain what primitive types are?”
Read report →“What can you tell me about indexes in a database?”
Read report →“Could you implement a delay function?”
Read report →Formats, difficulty and experience
Across all 7 DoorLoop interview reports.