I’m Michael. I was a principal engineer at Facebook from 2009 to 2017, where I was the top code contributor of all time and also conducted hundreds of interviews. I recently co-founded Formation.dev, an engineering fellowship that trains and refers engineers directly into big tech. Ask me Anything!

Hi, so in my experience each type of interview is hyper focused on specific things, so I can give those things for each type: * Data structures and algorithms: the "technical" (j.k.) term is "clean code". If someone naturally writes well organized code, minimal logic on the first try (no extra if statements or loops... even if they clean them up afterwards), that's always really impressive. Pro-tip: if an interviewer tells you your code looks "really clean" you probably passed that interview ;) * System design: if it feels like an exciting back and forth conversation more than interview that's fantastic. Like I'm talking to a peer casually about the problem. * Technical behavioral: this is a wider bucket, but strong career trajectory at your current company is very impressive, like being promoted every 6 months, or receiving really high (like top 5% at your company) performance reviews.