
FloQast Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 61 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at FloQast.
Software Engineer
My experience was mostly negative. I had two technical interviews. The first was a straightforward JavaScript DSA problem. The second interview lasted two hours, split into one hour for backend and one hour for frontend, both conducted on Replit. The backend part involved a basic Node server where I had to provide pseudocode as the given code was not runnable. The frontend challenge, which was to design and build an app checkout page, was clearer, but I struggled with running their React code, limiting my time. I was not hired, and I suspect the competition was high. They couldn't provide feedback due to policy. Notably, the same job was reposted on LinkedIn shortly after, appearing to be a copy-paste with an old application deadline. This, coupled with the lack of feedback and the job posting being up for three months, makes me question their hiring process and intent.
- Can you design and build a checkout page for apps?
Software Engineer
I started with a 20-minute behavioral interview that covered my past work experience. Then, it moved to a technical interview where I was given a simple data structures and algorithms problem. I mostly solved it, but the problem statement was a bit unclear about what was needed. I spent some time clarifying the prompt with the interviewer, and then I understood it better. I asked if I could code the remaining part, but they told me to skip it and just explain my approach. Afterwards, I asked some questions about the company, and the interviewer's responses about work-life balance and job security seemed disingenuous. I just went along with it, feeling like it might be a trap.
- Find user actions recorded in a specific sequence from provided logs.
Software Engineer
The whole process was pretty good and the team was super encouraging. Started with a phone screen that had a pretty easy coding challenge. Then I had a 4-5 hour onsite interview, which also included lunch with the team. Everyone was great and the questions were mostly fair, though there were a couple of topics about cloud services and specific details that I felt were a bit much, as not many engineers would deal with them unless they're cloud infrastructure focused. They also asked a good amount of database questions and how to design a database, which might be more DBA territory. But if you've worked in a startup where you had to do everything, you'll be fine with those.
- Can you answer some algorithm questions?
- Can you explain data structures (simple ones)?
- Can you design an API?
FloQast Software Engineer Interview Questions
Quoted word for word from FloQast interview reports.
“Write a function that prints numbers 0 to 5, with a one second delay between each number.”
Read reports →“Given a list of error codes for user IDs, identify all errors associated with a user.”
Read reports →“Could you count the number of characters that appear more than once in a given list?”
Read reports →“Can you use a hashmap to determine if there are repeated user keypresses that are causing an error?”
Read reports →“How would you find a specific sequence of letters from an array of objects containing single letter strings?”
Read report →“Design the data schema for a document collaboration app like Google Docs, including documents and user comments.”
Read report →“Can you explain how a site like Twitter or Facebook is structured?”
Read report →“Create a wireframe for the staff-facing frontend of the property management app, showing how they mark tasks complete using React.”
Read report →“Design a secure system for requesting documents, focusing on API and data storage aspects.”
Read report →Formats, difficulty and experience
Across all 61 FloQast interview reports.