Prefect Software 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 Prefect.
Prefect
Software Engineer
Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Coding Technical Behavioral
The interview process started with a recruiter call, followed by a take-home assignment using Vue. After the take-home was accepted, I met with the team lead and principal engineer. The technical interview was collaborative, where we enhanced the take-home assignment with some features; it was straightforward and engaging. However, the call with the chief of staff to the CTO was impersonal and rushed, feeling like he was reading from notes. This interaction felt off and didn't align with the role, despite the other interviews respecting my time. While Prefect has a strong culture, maintaining interview quality as they grow is key.
Confirmed questions2 questions
- Can you describe how you added a filter for the messages in exercise 1?
- Could you explain the steps you took to fix the CSS bugs?
Prefect
Software Engineer
Mid Easy Positive experience Accept offer 7 rounds
Interview process
Recruiter call Technical screen Onsite Panel Presentation Background check Offer
Interview formats
Technical Coding Behavioral Presentation
The whole thing took a bit but was fun. 7 interviews felt like a lot, but only one was a coding interview that tied into the take-home. It's totally fine to say you're stuck! The others were chatty, aimed at getting to know me and letting me meet the team and managers. The last couple were mostly for me to interview them and the CEO to see if it was a good fit.
Confirmed questions2 questions
- Can you share your previous experience?
- How comfortable are you with various work settings and scenarios?
Prefect
Software Engineer
Entry Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Behavioral Technical
The interview process was quite long and thorough, but it wasn't heavily technical. The focus was more on assessing culture fit and enthusiasm rather than just technical skills. While technical abilities were evaluated and deemed important, they seemed secondary to finding someone who aligned well with the company's culture, which I thought was a positive approach.
Confirmed questions1 question
- What's your approach when you have a disagreement with a colleague?
Prefect Software Engineer Interview Questions
Quoted word for word from Prefect interview reports.
“Can you explain the difference between a set and a list?”
Read reports →“Can you design a RESTful API that includes specific endpoints to function as a cache?”
Read reports →“Can you describe how you added a filter for the messages in exercise 1?”
Read reports →“Could you explain the steps you took to fix the CSS bugs?”
Read reports →“What's your approach when you have a disagreement with a colleague?”
Read report →“Can you share an instance where you expected disagreement on a topic and explain how you managed it?”
Read report →“Can you share your previous experience?”
Read report →Formats, difficulty and experience
Across all 7 Prefect interview reports.