← Back to Directory

Perplexity interview notes, page 3 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·Software Engineer·Technical Phone Screen

May 2026
Perplexity SWE interview that went deep on a timestamped key-value store design, specifically around adding a restore operation and hashing out the semantics and tradeoffs live with the interviewer. More open-ended than I expected, less about coding and more about thinking through data structure choices under pressure.
  • You have a timestamped key-value store with set, delete, and get operations. Design a restore(timestamp) operation that rolls the entire store back to its state at the given time. Discuss the semantics, data structure changes, and time/space complexity tradeoffs.

“This one took me a minute to even figure out what they were actually asking.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

May 2026
Standard SWE coding round at Perplexity. One question, trie-based design problem, test cases were given so no need to write your own.
  • Design an in-memory file system that supports creating files and directories, listing directory contents, and reading/writing file content.

“Go with a trie from the start, don't second-guess it.”

View Post

Perplexity·Software Engineer·Online Assessment (OA)

May 2026
Perplexity coding assessment, one problem the whole way through. The task was deceptively practical, less about clever algorithms and more about knowing when to stop and extrapolate.
  • On a ByteTokenizer class with a working tokenize method, implement estimate_token_count(text, sample_size, rng) that estimates the full token count without tokenizing the entire input. You can call tokenize as many times as you want, but the total bytes passed across all calls must stay within sample_size. If sample_size is at least as large as the input, return the exact count. Any randomness must use the provided rng object.

“The edge case tripped me up first.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a software engineering role at Perplexity and got a pretty meaty coding problem centered on an in-memory task management system. The core challenge was extending it with dependency tracking and a cascade-failure mechanism, which sounds manageable until you're actually tracing through a DAG under pressure.
  • You're given an in-memory Todo List system with basic CRUD operations. Extend it to support dependency tracking between tasks (parent/child relationships), then implement a cascade-failure function: when a task is marked failed, all tasks that transitively depend on it must also be marked failed. Handle performance for large, deeply interconnected graphs.

“I started with the dependency modeling, which felt fine, just adding parent and child sets to each task node.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineering role at Perplexity and got a coding question about building an in-memory Unix file system. Had a bug I couldn't track down in time and got rejected two days later.
  • Design and implement an in-memory Unix file system supporting commands like touch, mkdir, ls, rm, and rmdir.

“Went with a tree structure which felt like the obvious call.”

View Post

Perplexity·Product Manager·Hiring Manager Screen

Jun 2026
PM interview at Perplexity AI with a question about how you engage with users. Short and focused, nothing too wild, but the kind of question that sounds easy until you're actually answering it.
  • As a PM, how do you approach working with users?

“I rambled a bit.”

View Post

Perplexity·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Perplexity AI for a software engineering role. The whole question was basically one giant design problem about building a multi-provider LLM routing library, and they wanted you to go deep on basically every subsystem you could think of.
  • Design a resilient client library that routes requests across multiple external LLM providers. Your design should cover provider registration, capability mapping, rate limiting and quotas per provider, health checks, timeouts, circuit breakers, cost and latency aware load balancing, retry and fallback logic, observability, secure key management, and thread-safe concurrency. Walk through your interfaces, data structures, and how you handle failures.

“This question is basically a full distributed systems design crammed into one prompt.”

View Post

Perplexity·Product Manager·Recruiter / HR Screen

Jun 2026
Short PM screen at Perplexity AI, basically just one question about motivation for joining the company.
  • Why do you want to work at Perplexity?

“Pretty standard opener but I fumbled it a bit.”

View Post

Perplexity·Product Manager·Recruiter / HR Screen

Jun 2026
Screened for a PM role at Perplexity AI, one question about AI project experience and that was pretty much it.
  • What experience do you have working on AI projects or automations?

“Pretty expected for an AI company but I still fumbled it a bit.”

View Post

Perplexity·Product Manager·Hiring Manager Screen

Jun 2026
Interviewed for a PM role at Perplexity AI. Just one question worth noting, a conflict resolution scenario that felt deceptively simple until I was actually in it.
  • If you disagreed with an engineer on a product decision, how would you reconcile your data-driven perspective with their technical constraints without damaging the working relationship?

“I went straight to 'bring data to the table' and could tell that wasn't landing as a complete answer.”

View Post