
Fieldwire 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
Candidate interview experiences
First-hand accounts from people who interviewed at Fieldwire.
Software Engineer
I got contacted on LinkedIn and had a phone chat with a technical recruiter. Then, I went through an hour-long live coding test, kind of like LeetCode. I felt pretty good about it. After that, I did a take-home assessment and then a 3-hour "on-site" interview. The 3-hour on-site was a bit much, honestly. It was like 3 interviews back-to-back, and I had to take time off work for it. Felt like a waste of my time since I didn't get an offer and clearly messed something up. It would have been better if they spaced them out so the later ones could be canceled if I didn't do well early on, saving me time off my current job for a job I won't get. The technical deep dive was confusing; they didn't give much direction on what they were looking for, so I think that's where I messed up. The system design question was for just one user, which also threw me off since I prepared for more typical questions. They rejected me saying the role was filled, which felt impersonal after I spent over 10 hours interviewing and prepping. The company culture seemed really good though, I just wish the interview process was more manageable for someone working full-time.
- Could you design Dropbox for a single user with multiple devices?
Software Engineer
The recruiter was super responsive after each interview. It kicked off with a quick recruiter chat about my background and what I'm looking for salary-wise. Then, I had a 1-hour session with the hiring manager where I had to solve a LeetCode-style problem. After that, there were two paths: either a take-home project followed by a 3-hour virtual onsite that included a 1-hour extension of the take-home, a 1-hour deep dive into a past project, and a 1-hour systems design problem, OR a 3.5-hour virtual onsite with a 1.5-hour live coding session, a 1-hour project deep dive, and a 1-hour systems design question. Finally, I met with the VP of Engineering.
- Build an app to consume an API payload and display it appropriately as a take-home challenge.
Software Engineer
After an initial phone screen, I had a 45-minute coding interview with a senior engineer or lead. I didn't pass, but I gotta give them props for giving me a functioning UI and asking me to add features – it's a super realistic coding scenario and a nice change from typical coding interviews. HR did say I could choose the programming language, but that wasn't entirely true... you can't really use C++ to work with the DOM after being given CSS, HTML, and JS files. Usually, when HR says that, they mean for an algorithms/CS type of question. Still, it was the most realistic interview I've ever seen.
- Using JavaScript on a provided UI, implement new functionalities.
Fieldwire Software Engineer Interview Questions
Quoted word for word from Fieldwire interview reports.
“Solve a min cost problem using data algorithms.”
Read reports →“Did the recruiter send an automated rejection email instead of a personalized one?”
Read reports →“Could you design Dropbox for a single user with multiple devices?”
Read reports →“Can you create test automation for the ‘omninotes’ app?”
Read reports →“Can you explain how to call some API library and fetch data?”
Read report →“Build an app to consume an API payload and display it appropriately as a take-home challenge.”
Read report →“Solve data structure and algorithm problems.”
Read report →“Can you design a system like Google Drive, considering aspects like storage, retrieval, scalability, and efficiency?”
Read report →“Could you use a public REST API that you've never encountered before, and interact with it?”
Read report →Formats, difficulty and experience
Across all 13 Fieldwire interview reports.