← Back to Directory

Perplexity interview notes, page 1 of 5

Small

Most of these Perplexity write-ups come from Software Engineers (25), then Product Managers (12) and Machine Learning Engineers (4). The most reported rounds are the technical phone screen (17), the system design round (8), the hiring manager screen (5) and the product sense round (5).

41 interview notes · updated Jul 2026

Perplexity·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM case interview at Perplexity AI centered entirely on a market sizing and strategy problem for an autonomous vehicle service in Austin. Pretty open-ended, more like a consulting case than a typical PM screen.
  • You are launching an autonomous vehicle service in Austin. Estimate the total market size and potential demand for this service.
  • Given your demand estimates, what is the optimal fleet size for this autonomous vehicle service, and how would you adjust for peak versus off-peak periods?
  • What are the business strategy options for this service, specifically around operating the fleet directly versus licensing the technology to other operators?

“I started with population and daily commute patterns, then tried to carve out the addressable segment by income bracket and willingness to pay versus ride-sharing alternatives.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

Apr 2026
Perplexity software engineering interview focused on a practical coding problem: building a Todo List API designed for AI agent consumption. The twist was thinking about extensibility from the start, not just getting CRUD working.
  • Design and implement a Todo List system meant to be consumed by an AI agent. It should support adding, listing, updating, and removing tasks, with a clean API and in-memory data model that could later be extended with things like task dependencies and cascade failure handling.

“The CRUD part I had down fine.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

Apr 2026
Coding round at Perplexity for a Software Engineer role. The question was a meaty in-memory file system implementation and I got most of the way through it before running into a bug I couldn't squash in time. The interviewer was pretty checked out the whole session and I got a rejection the next day.
  • Implement an in-memory file system that supports creating directories and files, reading and writing content, and listing or searching within the file system.

“I'd seen this problem floating around before so I wasn't totally blindsided.”

View Post

Perplexity·Product Manager·Hiring Manager Screen

Apr 2026
Interviewed for a PM role at Perplexity AI. Just the one question I can recall, focused on cross-functional collaboration and experimentation with designers.
  • Can you walk me through how you've collaborated with designers when running A/B tests across different product iterations?

“I talked about syncing with design early so we weren't retrofitting metrics onto something already built.”

View Post

Perplexity·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Interviewed for an ML engineer role at Perplexity AI. One question on pipeline metrics, pretty focused on whether you actually know what to watch versus just listing buzzwords.
  • What metrics would you track to evaluate the performance of your ML pipeline?

“I went with the obvious stuff first, latency, throughput, model accuracy, then tried to layer in data drift and feature skew.”

View Post

Perplexity·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Interviewed for a PM role at Perplexity AI. One product strategy question about rolling out a new feature. Short post, not much context to go on.
  • How would you approach rolling out a new feature for Perplexity?

“Classic GTM meets product sense mashup.”

View Post

Perplexity·Software Engineer·Online Assessment (OA)

Apr 2026
Perplexity gave me a timed coding assessment centered on tokenization, basically asking me to reimplement a reference algorithm but fast. The problem was well-scoped but the performance bar was real, and I spent way too long second-guessing whether my output was even correct before worrying about speed.
  • Given a reference tokenization algorithm in a slow method, implement a faster version that produces identical output while tokenizing roughly 500KB of text against a 10,000+ token alphabet within a 10-second time budget.

“The 'identical output' constraint tripped me up more than the performance part.”

View Post

Perplexity·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Interviewed for a PM role at Perplexity AI and got a classic product sense question about UX design. Short post, just the one question from what I can tell.
  • What product do you think has good UX design, and why?

“Picked a product I actually use daily which helped, but I rambled a bit trying to cover too many angles at once.”

View Post

Perplexity·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design question at Perplexity AI for a software engineering role. Just the one question from what I can tell, focused on database selection for a chat app.
  • You're building a chat application. How do you choose between a SQL and a NoSQL database?

“I went straight to the access patterns, which felt right.”

View Post

Perplexity·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Perplexity system design round for a software engineer role. Just one question but it took up the whole session, which I wasn't fully expecting.
  • Design a personal finance management app similar to Mint.

“I started with data ingestion from bank feeds and got pretty deep into the plumbing before realizing I hadn't touched the user-facing side at all.”

View Post