PermitFlow logo

PermitFlow Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 13 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
30.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at PermitFlow.

Showing 3 of 13
PermitFlow logo
PermitFlow

Software Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Take home Technical screen Phone screen
Interview formats
Coding System Design Behavioral

So first I had a recruiter call where they asked for permission to record. Then came the take-home assessment, which was to build a CRUD app in three hours. Didn't need to finish everything, but a working prototype was necessary. Also had to make a short video explaining my work and talk about extra features I might've added. It felt like a lot for just an initial screen, and there wasn't any feedback. The recruiter got back in a few days and said I'd move to the next round. They called it a coding interview, but it was actually a design interview. The interviewer was nice, but the pacing was off. The task was to design a system for storing their questionnaires and questions. The design interview itself was also recorded without asking for permission, which is kind of weird.

Confirmed questions2 questions
  • What motivates you to want to work for PermitFlow?
  • Describe your approach to setting up the database for storing questionnaires and questions.
PermitFlow logo
PermitFlow

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Take home Technical screen Recruiter call
Interview formats
Coding Technical Behavioral

The interview process was fine overall. The initial take home was a lot for just a screen, asking to build a full CRUD app in three hours. Then there were a few technical screening rounds. It was pretty standard, but I was surprised to not get any feedback on my submission. They didn't even go over my CRUD work in the later rounds, which was annoying since I spent so much time on it. Also, they didn't give much of a reason when they rejected me.

Confirmed questions1 question
  • Create the core functionality for a full-stack CRUD application.
PermitFlow logo
PermitFlow

Software Engineer

Engineering

Entry Average Positive experience Decline offer 4 rounds
Interview process
Take home Technical screen Background check Offer
Interview formats
Coding Behavioral

A trusted advisor referred me to PermitFlow. I met with Sam, the CTO and a co-founder, who was super nice and flexible. It was a quick and pleasant process: a take-home assignment, a live coding interview, a cultural chat, and then reference checks. I'd tell any engineers who are good with products to apply.

Confirmed questions2 questions
  • Questions about the take-home assignment, which was designed for PermitFlow's specific industry.
  • Questions related to the live coding interview, which was also customized for PermitFlow's sector.

PermitFlow Software Engineer Interview Questions

Quoted word for word from PermitFlow interview reports.

Create the core functionality for a full-stack CRUD application.

Read reports

Describe your approach to setting up the database for storing questionnaires and questions.

Read reports

Formats, difficulty and experience

Across all 13 PermitFlow interview reports.

Interview formats

Behavioral 42.3%
Coding 26.9%
Technical 26.9%
System Design 3.8%

Interview difficulty

Easy 7.7%
Average 92.3%
Difficult 0%

Candidate experience

Negative 69.2%
Positive 30.8%