Coursera

“Pretty straightforward once you realize you only look at the first element of each ballot.” The rest of the author's notes on Software Engineer interview at Coursera, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to mutate the ballots as candidates got eliminated and I wasted a few minutes going down that path before realizing it was a mess.” The rest of the author's notes on Software Engineer interview at Coursera, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty mechanical once you see it.” The rest of the author's notes on Backend Engineer interview at Coursera, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The counting part was fine, just a frequency map and a scan.” The rest of the author's notes on Software Engineer interview at Coursera, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Walked through the usual stuff: target audience, positioning, pricing, channels, success metrics.” The rest of the author's notes on Product Manager interview at Coursera, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The redistribution logic is where I got a bit tangled.” The rest of the author's notes on Backend Engineer interview at Coursera, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to activation metrics and probably spent too long there before even touching retention properly.” The rest of the author's notes on Product Manager interview at Coursera, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Tried to frame it around the B2B value prop vs the consumer side, like why a company would pay for Coursera for Teams instead of just letting employees self-subscribe.” The rest of the author's notes on Software Engineer interview at Coursera, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is a bottom-up growth question and I fumbled the opening by going straight to tactics before establishing why consumer adoption even matters to an enterprise deal.” The rest of the author's notes on Software Engineer interview at Coursera, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The core counting part is straightforward, just a frequency map over the first element of each ballot.” The rest of the author's notes on Software Engineer interview at Coursera, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.