Current YOE: 4yrs

Fareharbor is a part of Booking holdings, so the interview process/ slary/perks are similar to Booking.com

For senior roles, Recruiter has in-depth discussion in a 30-40min call regarding your experiences and the relevance. For senior roles, you are expected to lead every aspect of the interview.

Round 1: Telephonic Interview to assess coding ability. Medium/Easy level, structured coding problem.(40min)
You also have to have a running code.

Theres a file having many log lines containing :
timestamp, eventid, event state description

1, id1, event started
2, id1, files uploaded
3,id2, process is running
4, id1, event complete

find all events that are complete ( event must have started, and must have completed)
find all open events ( events started but not completed)
find all invalid events (no event start history)
find top N longest running events where N is variable
Was able to solve this successfully and run it.

Round 2:(1hr) Hiring Manager round and Cultural Fit.
Various questions around your experience, What is expected etc. Some knoweldge about FH's product would be nice

Round3: Coding round 2(1hr) Leetcode Medium problem, more algorithmic problem. I received a variationof BFS problem where was asked to find hops between point 2 from point 1. Solved and ran it successfully. It was followed up with what happens if we have a graph with uneven distances betwen points, negative distances etc. Talked about djikstra's Algorithm, Time complexity, when to choose BFS vsDFS

Round 4: System Design. (1hr)
Design Zapier.

• A system where A user can integrate apps in a platform and based on certain events happening in app1, you can trigger events in app2.
• A USER can create TRIGGERS for certain EVENTS and have RULES, and based on this perfom certain automated ACTIONs on another APP.
• Activities are looged for every event (like event triggered, action performed, etc and made visible in a user-facing client application ) User can check the activities of that day. maybe this has an acces of once /day. ACtivity tracking may be eventually consistent

Scale: 100M DAU, each user having 5 events/sec. so 500M RPS !!!!
based on how the interview discussions went, I would say the final design was pretty complicated and many tradeoffs had to be considered.

Verdict: I enjoyed all the rounds, and performed well to my knowledge. some scope of improvements in Sytem Deign maybe. Interviewrs seemed happy as well.

I received a rejection email in 2 days stating it was a hard decision: "In the end, it really came down to the fact that we had a number of talented applicants that had qualifications and specific experiences that are very uniquely well suited to what we are looking for in the role."

Not sure if this is a generic rejection but quite disappointed wih the outcome.