
FareHarbor Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 11 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at FareHarbor.
Software Developer
The whole thing was okay, they were helpful. It all wrapped up in about 2 weeks. Here's how it went: A quick 15-minute first call, then a 1-hour live coding session. After that, two 1-hour sessions back-to-back: one for System Design and another with the Manager. No word back after all that though.
- Typical first call questions about getting to know each other and expectations.
- An average data structures question for the live coding portion.
- System design question related to frameworks, requiring demonstration of computer engineering skills (e.g., solid fundamentals).
Senior Software Engineer
The overall process was pretty standard for a tech company. I got a referral from an employee. CV screening was super fast, got a response the same day. Then there were a few interview stages: a 1hr online coding session with an engineer, a 1hr video chat with an engineering manager, a 1hr algorithms coding session, a 1hr systems design session, a 30min chat with a VP of product, and a 30min chat with an engineering manager. Everything was online because of COVID, but I think the first two are usually online and the rest are in-person, back-to-back in one day (about 3hrs). All the interviewers were really friendly and professional, felt more like a chill chat between colleagues than a stressful interview.
- Tell me about a simple, everyday coding problem that starts with a small scope and then expands.
- Can you solve a LeetCode medium problem that's a bit trickier than the last one?
- How would you design a system for a real feature used at our company?
Lead Software Engineer
The interview process involved an initial conversation with the CEO followed by a coding assessment. Although further stages might have existed, they weren't communicated upfront, and my participation concluded after the coding challenge. The overall human interaction was positive; the staff were amiable, and discussions felt relaxed. From a technical standpoint, the interview content didn't quite align with the role I applied for. During the CEO discussion, areas for improvement, such as architectural points and organizational issues, were brought up. For the coding portion, they asked questions like how to flatten a dictionary. This felt like a bit of a concern, suggesting a potential disconnect between their problem-solving needs and their hiring approach, which could create undue pressure in daily tasks. It's worth noting that the company appears to have substantial potential but is currently in a transitional phase regarding process professionalization. This could present an interesting opportunity for individuals keen on contributing to organizational development during its formative stages.
- What management-related questions were asked during the first interview?
- For the coding interview, were Leetcode-style questions presented?
- Was Big O analysis part of the coding interview?
FareHarbor Software Engineer Interview Questions
Quoted word for word from FareHarbor interview reports.
“Given two joined tables, write an SQL query to group the results.”
Read reports →“Can you write code to flatten a JSON object recursively, ensuring type checks?”
Read reports →“Could you implement a group by method for a specific key in the given JSON input?”
Read reports →“How would you implement a rate limiter for a web application?”
Read reports →“Was the question solvable using either BFS or DFS?”
Read report →“How would you implement a dynamic table using Javascript?”
Read report →“Were there questions about flattening a dictionary?”
Read report →“Was Big O analysis part of the coding interview?”
Read report →“Can you solve a LeetCode medium problem that's a bit trickier than the last one?”
Read report →Formats, difficulty and experience
Across all 11 FareHarbor interview reports.