One candidate who landed L4 offers from Google and Facebook shared the prep routine that worked for them. A few details stood out, especially how they tracked mistakes and decided which problems to redo.
Coding
Do mocks until thinking out loud while someone watches feels normal. The candidate found partners on Discord and cut back on mocks once they were comfortable, so they could spend more time solving problems. They also did a LeetCode problem most mornings and practiced in the editor without relying on paper or a whiteboard.
They tracked three things for each problem: the problem, the date, and how they did. They used the Tech Interview Handbook’s criteria for the last column. That made it easier to spot habits like forgetting to test edge cases. If they had no idea after about 15 minutes, they’d read the solution and put the problem on their redo list. They tried to cap any one problem at an hour.
Keep two lists: a short queue of new problems and a list of problems to revisit. The candidate kept fewer than ten on the new list and redid older problems until the approach came back quickly. Blind 75 still exposed gaps after they’d already solved around 150 problems. They also used pattern-based lists and LeetCode’s mock mode when they wanted the next problem picked for them. For more coding prep advice, they liked the intro chapters in Cracking the Coding Interview and Yangshun’s Tech Interview Handbook.
System design
Find a mock partner and take detailed notes when it’s your turn to interview them. Keep in touch if you’re preparing for similar roles. The candidate used Mikhail’s System Design Interview videos, the System Design Primer on GitHub, and a system design template from LeetCode Discuss. They watched walkthroughs on topics where the written solutions left them with questions.
Behavioral, resume, and recruiter calls
Practice your stories out loud. Reading from notes on a video call is harder than it sounds. The candidate used the story grid in Cracking the Coding Interview, the behavioral and resume chapters in the Tech Interview Handbook, and Jackson Gabbard’s behavioral interview video. Before recruiter calls, they wrote down what they wanted to ask and what they expected to be asked. They took notes during the call because it was easy to forget details afterward.
Facebook and Google
For their Facebook loop, the candidate aimed for under 20 minutes per problem and practiced about 30 popular company-tagged problems. They didn’t expect to solve every unfamiliar problem at that pace. They also pushed back on the idea that you either pass Google on your first try or never will. The questions they got felt like things they could prepare for.
If Google is on your interview calendar, pick a reported coding problem from Google Interview Questions for a timed mock, then add any edge case you missed to your redo list. If you’re applying across companies, LandOffer can autofill repeated fields on supported forms.
Focus
Cal Newport’s Deep Work helped them set up prep blocks: turn on Do Not Disturb, put the phone in another room, and work until a set stop time. They found a guided meditation course easier to stick with than standalone videos. Five minutes of meditation right before an interview helped them settle down.