Perplexity interview notes, page 2 of 5

“My first mistake was only tracking which tasks a given task depended on, not which tasks depended on it.” The rest of the author's notes on Software Engineer interview at Perplexity, Onsite - Coding / Algorithms 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 Perplexity, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This question is basically five system design questions duct-taped together.” The rest of the author's notes on Software Engineer interview at Perplexity, Onsite - System Design / Architecture 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 just use a dict and I had to stop myself.” The rest of the author's notes on Software Engineer interview at Perplexity, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This tripped me up more than I expected.” The rest of the author's notes on Software Engineer interview at Perplexity, Take-home Assignment round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Spent the first minute just trying to pick a direction and probably looked a bit lost.” The rest of the author's notes on Product Manager interview at Perplexity, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to staleness thresholds and drift detection, which felt right, but I didn't connect it back to business impact fast enough.” The rest of the author's notes on Machine Learning Engineer interview at Perplexity, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Got through the main logic fine, dedup first then figure out the order from the paragraphs.” The rest of the author's notes on Software Engineer interview at Perplexity, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is one of those questions that feels easy until you realize they want all of it: the plain English explanation, the complexity analysis, and bug spotting, all in one go.” The rest of the author's notes on Software Engineer interview at Perplexity, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This one has a lot of surface area and I probably tried to cover too much.” The rest of the author's notes on Machine Learning Engineer interview at Perplexity, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.