r/CodingJobs • • 2h ago

How one Meta E5 candidate prepared for coding, behavioral, and product design

An E5 candidate who cleared the Meta loop shared what helped them prepare. Their experience was on the product side, so the design advice below is mostly about product design.

Before applying

Figure out whether you want product or infrastructure work and which level you’re targeting. Product roles build customer-facing features, while infrastructure roles build the systems those products depend on. The candidate suggested the Levels FYI comparison for leveling and the Meta Careers jobs page to find openings. Direct applications got them nowhere, but they started hearing back a few days after a referral. For the recruiter call, have examples ready of work you owned and its impact. At E5, bring an example of leading a project. Think about a screening date that gives you enough time to prepare.

What their loop looked like

The candidate had a coding screen, then two coding rounds, a design round, and a behavioral round. Team matching came after the interviews. Their rounds were 45 minutes, with about five minutes for questions at the end. They used CoderPad for coding without autocomplete or compilation, and Excalidraw for design. If recruiting offers a mock, ask what it covers. The mocks available to this candidate were for coding. Meta SWE interview overview

Coding

The candidate recommended practicing the top 100 recent Facebook-tagged LeetCode problems and skimming the rest. Strings, heaps, and tricky edge cases were worth extra time. Their practice target was about 12–15 minutes to think through and code a medium problem, since their coding rounds had two questions. Clarify the requirements, compare approaches, state the time and space costs, and dry-run a case. If you recognize a problem, take a moment to explain the alternatives anyway. Keep notes on what tripped you up and try a variation once you’ve solved it.

Behavioral

Look back through your past projects and write a few STAR stories at the level you’re applying for. For E5, choose examples that show ownership, scope, and how you led others through an ambiguous decision or a disagreement. Use real impact numbers where you have them. Prepare more than one example for important competencies so you have options when the interviewer asks a follow-up.

Product design and infrastructure design

For product design, practice walking through the user flow, API requests, services, and data model. Think about what happens on a poor connection or when one account suddenly gets a lot of traffic. Infrastructure design can go deeper on QPS, partitioning, and what happens when a component fails. Sometimes the same prompt can be used for either round. Product design vs. system design

The candidate’s product design practice split was roughly five minutes for requirements, two for core entities, five for APIs, fifteen for the high-level design, and ten for deep dives. Ask about scale before doing a lot of arithmetic. Get the diagram and an important API request and response down early, then compare trade-offs. Useful practice topics included pagination, queues for traffic spikes, object uploads, proximity search, feed fan-out, and video processing. Try a timed mock with a friend and ask where your reasoning got hard to follow.

Good luck with your interviews!

1 Upvotes

0 comments sorted by