← Back to Directory

Perplexity

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·Onsite - System Design / Architecture

Jul 2026
Perplexity system design round for a software engineering role. The core problem was building a timestamped key-value store from scratch with time-travel and rollback, which sounds manageable until you actually have to think through all the edge cases live.
  • Design and implement an in-memory key-value store where every operation carries a monotonically increasing timestamp. It must support set, get, delete, a range query over a time interval, and a full-store rollback to any past timestamp. Discuss the data structures you'd use and any assumptions about ties at the same timestamp.

“This is a meaty one.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

Jul 2026
Perplexity software engineer round that was basically one meaty coding problem about a task manager with dependency cascading. The graph traversal angle is where it gets interesting and where I think a lot of people stumble.
  • Design and implement a Python in-memory task manager for an AI workflow system. Tasks have unique IDs and statuses, and can depend on other tasks. You need to support adding tasks, adding dependencies between tasks, failing a task (which must cascade to all downstream dependents), and querying a task's status. The implementation must handle large graphs efficiently without redundant traversal.

“I started with a straightforward DFS for the cascade and it felt clean until they mentioned the efficiency constraint.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

Jun 2026
Perplexity AI coding round for a software engineer role. One meaty design question that looked manageable at first glance but had enough edge cases to keep you busy for a full session.
  • Design a CreditTracker class with methods to add credit (with a start and end time), subtract credit (at a given time, deducting from the earliest-expiring credit first), and check the current credit balance at a given time. Calls to add and subtract can arrive out of chronological order. Walk through your data structure choices, implementation, and time/space complexity.

“The greedy deduction rule (earliest expiry first) is what makes this non-trivial.”

View Post

Perplexity·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Perplexity system design round focused entirely on an AI-augmented to-do list app. The scope was massive and I definitely underestimated how deep they wanted to go on the LLM integration side specifically.
  • Design an AI-powered to-do list application that supports natural language task creation (e.g. 'remind me to call mom every Sunday at 6pm'), AI-suggested subtask decomposition, smart prioritization, scheduling, and reminders. Cover the data model, API surface, LLM integration, cross-device sync, and offline support.
  • How would you design the data model to handle recurring tasks with flexible recurrence rules?
  • How would you handle LLM integration for this product: specifically prompt design, latency, cost, and privacy concerns?
  • How would you support offline functionality and cross-device sync for this application?

“This is a single question but it's basically six questions duct-taped together.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a SWE role at Perplexity AI and got a technical question around storage I/O optimization. Pretty focused session, one meaty question that required knowing your way around low-level write performance.
  • What techniques can you use to optimize write performance when moving data from memory to disk?

“I started with buffered writes and batching, then moved to write-ahead logging and memory-mapped files.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

Jun 2026
Coding round at Perplexity for a software engineer role, basically a multi-part Python implementation problem. Not brutal, but you have to keep an eye on the clock.
  • Implement a ToDo list in Python using three provided classes: a TaskStatus enum, a Task class, and a ToDoList class. Complete four parts sequentially, each with their own test cases. Part 1 covers basic CRUD operations.

“The scaffolding was already there which helped, but four parts means four chances to fall behind on time.”

View Post

Perplexity·Product Manager·Hiring Manager Screen

Jun 2026
Interviewed for a PM role at Perplexity AI. Just one question to go off here, focused on cross-functional collaboration with UX.
  • How have you collaborated with UX designers to move quickly through iteration cycles?

“I talked through a project where we were shipping design changes weekly and I was basically the go-between for eng and design.”

View Post

Perplexity·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Interviewed for a PM role at Perplexity AI. One question on AI product metrics, pretty focused on whether you actually understand what makes AI features different from traditional ones.
  • How would you define success metrics for an AI-oriented feature or product?

“This tripped me up more than I expected.”

View Post

Perplexity·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed at Perplexity for a software engineer role. The question was about outputting citation numbers from paragraphs, which sounds trivial until you're actually in the seat trying to articulate a clean approach under pressure.
  • Given a set of paragraphs where each paragraph contains numeric citations that map to a list of sources, output all the citation numbers found in the paragraphs.

“This felt deceptively simple.”

View Post

Perplexity·Product Manager·Hiring Manager Screen

Jun 2026
Interviewed for a PM role at Perplexity AI. Just one question to go off here so hard to say much about the full loop, but the AI-first angle made it feel different from a typical PM screen.
  • Why do you want to join an AI-first company?

“Sounds easy until you actually try to answer it without sounding like you just read the homepage.”

View Post

Perplexity interview FAQ

What rounds are in the Perplexity interview?

Candidates most often report a technical phone screen (17 write-ups), a system design round (8), a hiring manager screen (5) and a product sense round (5).

What does the Perplexity technical phone screen cover?

Across 17 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (12 questions), System Design (12) and Technical Trade-offs (12).