• Coding 1:
  • Q1: Tagged list top 50
  • Q2: Tagged list low-frequency hard, never saw it beforehand but is an "easier" hard in my opinion

Solved both optimally on first attempt. Noticed a mistake in Q2 after the interview relating to an edge case (no solution case), not sure if the interviewer noticed, and if they check after the interview?

• Coding 2:
  • Q1: Tagged list top 50
  • Q2: Tagged list top 50 variation

Solved both optimally on first attempt.

• Behavioral:
  • I'm not really sure how to measure how good I did on a behavioral interview. They asked 4 main questions, plus followups that relate to the scenario to get a better picture. They seemed to have a good mood the whole time, but I don't know how else to tell. All 4 questions were very standard (didn't ask stuff like "what's your biggest weakness")

Don't want to share questions due to NDA but if you do the 3 month tagged list you'll cover them all. The variations/followups are not different enough for it to be difficult if you understand the standard question well.

Preparation: I've done about 800 questions lifetime, but about 50-100 questions to specifically prepare Meta.

Tips: Keep the 4 signals for Meta coding interviews at the back of your mind when interviewing and structuring your thoughts. These are

• Communication (Clarifying edge cases, inputs, thinking out loud)
• Problem Solving (Comparing approaches/data structures, time and space complexity discussions)
• Coding (No code duplication, good practices)
• Verification (Dry run, testing, debugging)
  Even if you are perfect in one category, you can fail due to lacking in other places. Self evaluating my performance, I think I did not score perfectly in two categories (communication, verification).

Try to do mock interviews with someone. If you can't, you can also try and record yourself on video talking out loud while solving a question under time constraints. This lets you critique yourself better after the fact.

Good luck!