Backend Engineer | Zenskar
JP Morgan Chase | SDE 3 | YOE 3.4
Microsoft SDE - 2 | Interview Experience | Status Pending
eBay || SWE3 Interview Experience || Bangalore
Bloomberg | Interview Experience | Senior Software Engineer | NYC | Nov 2025
Facebook | E4 | London
Summary
I recently completed my onsite interview for an iOS Engineer role at Facebook in London. The interview included coding, behavioral, and a system design round where I had to design a messenger app. I believe my performance was strong and I'm currently awaiting the outcome, hoping for an E5 offer.
Full Experience
I recently completed my onsite interview for an iOS Engineer position at Facebook in London. I have 5 years of experience (YOE).
In the first coding round, I tackled two standard questions, though not from LeetCode. I performed well, successfully running tests for the first question, and even though I couldn't run tests for the second due to time constraints, the interviewer seemed fine with it.
The second coding round presented one medium and one hard question, both of which I was able to solve in O(n) time complexity. This round also went smoothly.
The behavioral round involved standard questions about challenging work and my motivation for joining Facebook. I effectively answered these by sharing past examples from my career.
The fourth round, iOS System Design, was particularly engaging. My task was to design a messenger app. I felt this round went great, as I was able to discuss multiple architectural approaches for each component, along with their respective tradeoffs and scalability considerations.
My pre-screening took place in March, but the onsite interview was scheduled for October due to a hiring freeze for E4 positions. Overall, I feel my rounds went well, and I'm optimistic about potentially receiving an E5 offer. I'm now waiting for an update regarding the hiring freeze and my candidacy.
Interview Questions (1)
My task was to design a messenger application. During the discussion, I explored and discussed multiple architectural approaches for various components, emphasizing their tradeoffs and scalability implications.