
Netlify Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 22 interview experiences · FREE TO READ
Which role are you interviewing for?
14 roles · 22 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Netlify.
Engineer
It was a total mess, but I got referred and fast-tracked. They offered me part-time to start, and even with all that, my first interview was just a chat with another teammate. After six more interviews and a homework assignment, they passed me. They clearly didn't know what they were looking for.
- What makes you want to join Netlify?
DevOps Engineer
This whole thing took like 7 weeks from the start to when they rejected me. It started with an application, and 4 days later I got the first contact. The first interview was with the directory of infrastructure, 6 days after that. Then, 4 days after round 1, I had the second round with two engineers from the team. That went really well, though one engineer seemed a bit smug, which gave me pause. The other engineer was great to chat with. After that, I got a take-home project. The instructions were really vague – the technical stuff was mostly clear, but I didn't know how much time I had, how detailed it needed to be, or what tools I could use. They put me in a private Slack channel with other team members, but it wasn't clear what the point was. Could I ask for help? Was it supposed to be collaborative? I spent a week on the project, working evenings. Sometimes it took a day to get answers to my questions, maybe because of the time difference. Again, I wasn't sure how long it was supposed to take. They also didn't pay me for it. In the end, they said they'd keep my resume for future openings, but I never heard back.
- Can you explain in detail the sequence of events that occur when a URL is entered into a browser and the enter key is pressed?
Front End Developer
I talked with the CTO, did a coding exercise, and then chatted with two team members. They mentioned that they changed their hiring process to be in batches to address issues with not hearing back, which some people mentioned on Glassdoor. The people I interacted with were super quick to respond and really nice. Even though I didn't have the exact skills they needed, I still felt good about the experience. My only suggestion is that they should give a clearer reason in their emails when they decide not to move forward with a candidate.
- Can you tell me about your experience with accessibility?
Product Manager
Honestly pretty disappointing. I had a phone screen scheduled with a recruiter, but they never showed up to the interview. Kinda should have taken that as a sign. They did reach back out and reschedule though. The recruiter was nice, but they overpromised. They said they'd recommend me for the next interview, but the follow-up was never scheduled and they ghosted my additional follow-up emails. I ended up withdrawing my application a month later. All in all, it was a waste of 1 month of my time.
- Could you tell me about yourself?
Netlify Interview Questions
Quoted word for word from Netlify interview reports.
“Can you explain in detail the sequence of events that occur when a URL is entered into a browser and the enter key is pressed?”
Read reports →“Can you explain what Active Directory is?”
Read reports →“Regarding project work, can you explain the reasoning behind using synchronous methods for file system operations instead of asynchronous ones?”
Read reports →“How would you go about updating a legacy checkout system?”
Read reports →“Describe a situation where X happened.”
Read report →“Could you deploy a website on Netlify and then write up your process?”
Read report →“What makes you want to join Netlify?”
Read report →“Describe your experience using Airflow for data pipelines.”
Read report →“Describe your approach to debugging a ticket.”
Read report →Formats, difficulty and experience
Across all 22 Netlify interview reports.