Meta Tech Screen & Coding in 2023

Coding round format (45 min): - 5/35/5 - 5 minutes intros, 35 minutes coding to solve 2 LC problems, 5 minutes questions Coding portion (35 min): - Problem by interviewer - Solution suggestion: data structure, algorithm, time/space complexity - "Ready to write code" - Write code - Think out loud as you write code ✅ - Trade-off's ✅ - Edge cases ✅ - Verification: hotspots in code - Can you improve time/space? - Find, implement optimization ✅ - New time/space. Explain why - Verification: Test case and Walk through example input Time/LC: ~15 min LC/round: 2 Red flags: - Receiving hints 🚩 - Handholding 🚩 - Interviewer repeats themselves 🚩 - Bugs 🚩 ----------------- Coding round tips: - "VERIFICATION" is a very specific term, and that's what it is specifically called. There are 3 types: test cases, hotspots in code, walk-through with example input/output - "Trade-off's" and "Edge cases" are both really important - 📝 REAL LIFE STICKY NOTES 📝. I know this sounds dumb. It's not. You need an obvious and not subtle reminder of the steps. I'd write this down using a sharpie and clearly visible: - Trade-off's - Edge cases - VERIFICATION: hotspots, test case, walk-thru - Interruptions. Depending on whether the interviewer likes you, he or she may interrupt often. Don't take it personally, it's just a test. However, be very mindful of time. Make sure to mention "I would like to do a Trade-off analysis", "These are the edge cases", "This is a hotspot in the code". And "I can also walk-through the code". You need to absolutely say this, do not expect to be prompted (s/he may or may not). If you DON'T cover these areas, you will be marked down for not providing signal. ----------------- System Design, Product Architecture: Design Facebook Newsfeed. Design Facebook Messenger. Design Instagram. Design WhatsApp. Design Live Commenting. Design Typeahead Suggestions. Design Google Docs. Design a distributed Botnet. Design Resource Downloader Library. Design a video-sharing platform.