Meta E6 Loop experience
- Experience
- 9.5 years
- Posted
- 2 May 2025
Summary
I had an E6 loop at Meta, comprising two coding rounds, two system design rounds (Ticketmaster and Ad impressions aggregator), and a behavioral round. I performed well in coding and behavioral, but felt time management in system design could be improved. I am currently awaiting the results and feeling nervous.
How it went
I just had a loop at meta for e6 role. YOE - 9.5 1st coding round: optimally completed the 1st Q. Completed the 2nd Q as well but not optimal 2nd coding round: both questions done optimally though 2nd Q after some brainstorming. System design round 1 (Ticketmaster): Gave the HLD and the deep dive to handle locking via redis and hold period. Basic strategies for handling scale in last 2 mins as time went by quickly. Interviewer asked couple of questions only at the end which I answered. But i think time management was not perfect. I missed some points which i wanted to make. Behavioural: Gave perfect anecdotes at senior and staff level with great impact and scale. I think this went great. System design round 2 (Ad impressions aggregator): Gave the HLD with 2 deep dives into fault tolerance, low latency and scaling using Kafka.
Awaiting for the result. I am really nervous.
Questions asked (2)
- 01
Design Ticketmaster
System Design
Design a system like Ticketmaster. I provided a High-Level Design (HLD) and deep dived into handling locking via Redis and managing a hold period. I also discussed basic strategies for handling scale.
- 02
Design Ad Impressions Aggregator
System Design
Design an Ad Impressions Aggregator system. I provided a High-Level Design (HLD) with two deep dives focusing on fault tolerance, low latency, and scaling using Kafka.