ByteDance interview notes, page 1 of 29

“This wasn't a casual 'tell me about yourself' opener.” The rest of the author's notes on Machine Learning Engineer interview at ByteDance, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This question is deceptively wide.” The rest of the author's notes on Software Engineer interview at ByteDance, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The O(n) trick here is to keep a running length counter and add it to your total at each position.” The rest of the author's notes on Software Engineer interview at ByteDance, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The setup sounds easy and then you realize you have to compute two separate rates for each of five matrices without making arithmetic mistakes while someone is watching you.” The rest of the author's notes on Software Engineer interview at ByteDance, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The high-level part felt fine but I wasn't ready for how fast they'd pivot to the weeds.” The rest of the author's notes on Software Engineer interview at ByteDance, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This was the whole interview, not just one part of it.” The rest of the author's notes on Backend Engineer interview at ByteDance, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went DFS first because it felt more natural to code quickly, just mark visited cells as '0' and recurse in four directions.” The rest of the author's notes on Software Engineer interview at ByteDance, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This felt like one question but it's really four.” The rest of the author's notes on Software Engineer interview at ByteDance, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew the punchline (all 5s with var, 0 through 4 with let) but fumbled explaining why the console.log after the loop fires before any of the timeouts.” The rest of the author's notes on Frontend Engineer interview at ByteDance, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“It's labeled Hard but anyone who's done a few rounds of prep has seen this one.” The rest of the author's notes on Software Engineer interview at ByteDance, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.