Software Engineer applicants have rated the interview process at PermitFlow with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 40% positive. To compare, the company-average is 32.2% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 9 days to get hired, when considering 10 user submitted interviews for this role. To compare, the hiring process at PermitFlow overall takes an average of 25 days.
Common stages of the interview process at PermitFlow as a Software Engineer according to 10 Glassdoor interviews include:
Phone interview: 38%
One on one interview: 38%
Skills test: 13%
Background check: 13%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. I interviewed at PermitFlow
Interview
The overall interview process was fine. The initial take home is basically to build a full CRUD application in three hours, which is quite a bit of work for just an initial screen. Then you have a few rounds of technical screening.
Pretty standard overall, but it was surprising to not get feedback on anything I submitted. We didn't go over my CRUD submission at all during the subsequent rounds, which was annoying for having to spend so long on it. Then on rejection they didn't give much of a rationale either.
Interview questions [1]
Question 1
Build the basic functionality for a fullstack CRUD application.
Pros: The initial outreach was prompt, and individuals on the team seemed knowledgeable.
Cons: Avoid this company at all costs. They will undermine your talents. The entire hiring process is a disorganized gauntlet that feels more like a hostile environment than a professional evaluation. I was bounced between multiple recruiters and shuffled across various roles simultaneously, which made for an incredibly frustrating experience.
The company forces candidates through a repetitive cycle of technical tasks. My experience:
- Take-home assessment
- Live coding interview
- SQL assessment
Demanding three separate technical evaluations for multiple roles at once shows a complete lack of internal alignment. I received conflicting information from different staff members throughout the process, making it impossible to pin down the actual requirements for any specific position.
The worst part was the SQL assessment. There was zero room for a collaborative technical discussion or even basic clarifying questions about the requirements. Instead of a peer-to-peer conversation, it felt like a rigid, one-sided test where the interviewers were clearly just looking for you to fail.
Advice to Management: Consolidate your interview loops. Making candidates complete a take-home, live coding, and SQL assessment without a unified strategy is a massive waste of time. Train your technical team on how to actually talk to people. A "gotcha" culture is a major red flag for top talent.
I applied through a recruiter. I interviewed at PermitFlow
Interview
Similar to others, a standard recruiter screen followed by a very direct question about being okay with working 50 hours a week. This seems like the only question they care about. If you say anything other than yes, you're immediately rejected.
I applied through a recruiter. I interviewed at PermitFlow in Aug 2024
Interview
After the recruiter screen the first step is a take-home assessment where you're expected to build a CRUD app in three hours. You don't have to finish all the DB and API endpoints within that time, but you still need a working prototype. Additionally you're expected to make a short video explaining your work and write more information about additional features you might have done.
This is a lot for an initial screen. There's also no feedback on your submission.
Recruiter got back to me in a few days that I'd move onto the next round that was described as coding interview, but it's actually a design interview. The interviewer was nice but the pacing of the interview was bad. You're asked to design a system for storing their questionnaires and questions.
In the recruiter call you're asked for permission to have the conversation recorded. The design interview didn't ask for permission and was recorded. This isn't standard practice.