How Perplexity Interviews in 2026: Process, Questions & What They Score
The complete process, reported questions, and what interviewers score.
Perplexity / Interview snapshot
11
stages from
application to offer
38
reported questions
35
public sources
Independent: SupaCV is not affiliated with or endorsed by Perplexity. This is one well-documented shape of Perplexity's interviews, not a script: processes change and vary by role, team, level, and region, so confirm specifics with your recruiter.
On this page
01 / For every Perplexity candidate
The process, start to finish.
Perplexity hires across many functions. This playbook covers the engineering track (the portal refers to its Members of Technical Staff, and prep sites call the role Software Engineer). Perplexity publishes a lot about its own process: a technical interviewing portal (interviewresources.perplexity.ai) with a page for each round format, plus an interview guide on its careers hub.
The official sequence is online application, recruiter phone screen, technical assessment, an onsite of 4 to 5 interviews including a deep dive with a hiring manager, then a final interview with a founder or leader. Team matching happens during the onsite. The two official pages word the decision timing differently: the interview guide says a decision comes within a week of the onsite, and the careers page says candidates hear back within a week of their final interview.
Each role draws a different subset of six formats: Practical Assessment (online), Hands-on Coding (live), Spike Round (a self-steered async project of up to 9 hours), Agentic Coding (frontier coding agents required), System Design, and Core Expertise. The portal says each loop is curated by engineering leadership and that the recruiter explains the loop for your role. Most technical loops also include at least one non-technical round.
Counting the recruiter screen, the technical screen, 4 to 5 onsite interviews and the founder round, an engineering loop is roughly 7 to 8 conversations (this is a count from the official stage list, not a published figure). Third-party guides put the whole process anywhere from about 1 to 5 weeks (TechPrep 1 to 3 weeks, Designgurus about 23 days on average, Codemia 3 to 5 weeks).
Perplexity says its coding exercises are written in-house by its Members of Technical Staff and that it does not use question banks from LeetCode, HackerRank or similar platforms. Python is strongly recommended. No official page lists questions from real loops; the one official example is a practice exercise, a dependency-aware todo list for AI agents. Candidate-tagged reports keep naming the same problems: that todo list, an in-memory file system, a time-versioned key-value store and a credit tracker with expirations.
Many other coding and design items on prep sites (Codemia, TechPrep) are presented as sample or common examples, not as reports from named candidates. Perplexity publishes an interviewing philosophy listing five abilities that strong technical candidates show, and it is used as the framework below. Candidate reports here are thin, and none come from Glassdoor or 1point3acres. A product manager track exists and is covered by one coaching guide (three stages, seven conversations), but it is not the focus here.
Stage 1: Application review
up to 2 weeks
Perplexity says candidates should hear back within two weeks if it thinks they would be a good fit. The interview guide asks candidates to apply even without a perfect fit and to choose the closest role, since all roles are broad and precise team matching happens during the onsite.
Stage 2: Recruiter phone screen
20-45 min
The official guide says only that a recruiter schedules an initial phone screen, with no length or content. TechPrep says 20-30 min, Codemia 30-45 min and Designgurus 45 min. Third-party guides say it covers background, motivation for Perplexity and familiarity with the product. A Blind commenter describes the first step as an HR call.
Stage 3: Technical assessment: Practical Assessment (online) or Hands-on Coding (live)
Practical Assessment: designed for 45-90 min within a 2 or 4 hour window; Hands-on Coding: 30-60 min
The interview guide says only that for engineers this step is usually a standard technical programming interview. The portal says that for many technical roles the process begins with an at-home Practical Assessment, which is self-scheduled on CoderPad or CodeSignal. The live version runs on a shared CoderPad or CodeSignal session, over Google Meet with full-screen sharing for virtual rounds, with one or two interviewers. Exercises are structured in multiple parts and you do not need to finish every part. In the live format you and the interviewer verify each part together, and the published todo list example has a test runner for each coding part. AI help is banned except for questions about library usage and online language documentation. Third-party lengths: TechPrep 1-2 screens of 45-60 min, Codemia 60-90 min, Designgurus about 60 min. A PracHub candidate describes a 4-part todo-list screen in Python, rejected the next day after finishing two parts.
Stage 4: Onsite: Hands-on Coding rounds
30-60 min each
Practical components and abstractions for the types of systems that power Perplexity, written in-house. Dynamic programming recipes, esoteric data structures and advanced graph algorithms are not expected. Codemia reports two onsite coding rounds at 45 min each, and Designgurus reports one or two. TechPrep says the onsite covers applied coding but gives no count. The number varies by role, and the portal does not say where the coding rounds sit within the loop.
Stage 5: Onsite: System Design
45-60 min
Live, on a physical or virtual whiteboard with one or two interviewers. An open-ended exercise to design and/or refine a system in domains relevant to Perplexity, sometimes with documentation provided at the time of the interview. Codemia lists a separate 45-60 min ML / LLM Design round on top of a 60 min System Design round.
Stage 6: Role-dependent: Spike Round or Agentic Coding
Spike Round: up to 9 hours; Agentic Coding: 3 hours async or 60-120 min live
Only some loops include these, and the portal does not say where they sit in the loop. The Spike Round is an async project the candidate defines and delivers on Zoom with the screen shared, ending in a 10-20 min recap. Any resources except live human help are allowed, and up to $750 of technical costs are reimbursed. Agentic Coding requires frontier coding agents. The portal says live Agentic Coding has higher expectations for scope, depth and quality than Hands-on Coding, and the async version is scored on criteria similar to the Spike Round. TechPrep separately reports a 4-6 hour take-home for some senior and staff candidates.
Stage 7: Role-dependent: Core Expertise
30-60 min
Early-career candidates choose a discipline from at least four, typically drawn from computer science and applied mathematics (algorithms is also named), and confirm the choice with the recruiter. Experienced candidates are told a technical domain by the recruiter and may be asked in depth about past work such as papers, systems and open-source contributions. The portal says there is no strict rubric. Where it sits in the loop is not published.
Stage 8: Onsite: Hiring manager deep dive and non-technical round
45-60 min for the deep dive (third-party only)
The official guide confirms a deep dive with a hiring manager on past work and experience anecdotes, and says team matching happens during the onsite process as the manager describes possible teams. The portal says most loops include at least one non-technical round with a manager or cross-functional partner. Neither official page gives a length. Codemia lists 45 min for the hiring manager or founder round and Designgurus lists 45-60 min for the hiring manager deep dive. The length of the non-technical round is not published and likely varies by role and level.
Stage 9: Final interview with a founder or leader
30-45 min
The official guide lists a final interview with a Perplexity founder or leader after the onsite and gives no length. TechPrep reports about 30 minutes on engineering philosophy, product thinking and drive. Designgurus reports 30-45 minutes on mission, curiosity and judgment.
Stage 10: Decision and offer
within 1 week of the onsite (interview guide) or of the final interview (careers page)
The two official pages differ. The interview guide says a decision is made within a week of the onsite and an offer is sent if all goes well. The careers page says candidates hear back with an offer or next steps within a week of their final interview. Codemia says offer decisions usually come 3 to 5 days after the final round.
Stage 11: Post-offer conversations
varies
The interview guide says additional conversations are scheduled after an offer so candidates can learn more about Perplexity, meet future colleagues and refine the team match. It gives no length or number of conversations and does not say what they depend on.
02 / What Perplexity scores
Our interviewing philosophy
01
Think rigorously
02
Navigate and control complexity
03
Discriminate between plausible options and make principled tradeoffs
04
Learn with high sample efficiency
05
Communicate clearly (in words and in code)
Published on Perplexity's technical interviewing portal (https://interviewresources.perplexity.ai/) under the heading 'Our interviewing philosophy', introduced as the abilities through which strong technical candidates stand out at Perplexity, no matter which role they are interviewing for. The list has five items, given exactly as published. Individual round pages publish their own criteria. System Design lists Problem framing, Requirements, Core architecture, Scaling and bottlenecks, Identifying and navigating tradeoffs, Adaptability and Domain expertise ('including but not limited to').
The Spike Round instructions list Project scope completed, Methodology, Performance and functionality, Effective use of tools, Code quality and legibility, and Communication. Hands-on Coding names its primary signal as producing high-quality work that precisely and correctly addresses the requirements. Core Expertise says it has no strict rubric.
Read the rest of the framework notesShow less
Separately, the careers page lists five company values (Craftsmanship, Ownership, Entrepreneurship, Scholarship, Partnership), and the interview guide tells candidates to review the mission and values before applying, but the values are not presented as an interview rubric.
03 / Coach's notes
Coach's tips.
01
Practice long, multi-part practical builds in Python, not LeetCode recipes. Perplexity strongly recommends Python and strongly discourages Java. It writes its exercises in-house, and it says dynamic programming recipes, esoteric data structures and advanced graph algorithms are not expected. In Core Expertise, algorithms has the lowest pass rate by a wide margin among the early-career disciplines.
02
Make each part correct before moving on, and check behavior on large inputs. In the live format you and the interviewer verify each part together before the next one, and Perplexity says it is common to run out of time before finishing every part, so you do not need to finish all parts to pass. One candidate's DFS cascade passed every test except a large one that timed out, and they were rejected the next day. The report does not say the timeout was the reason.
03
Learn the AI rules for each round. The Practical Assessment and Hands-on Coding ban AI and outside help, except for online language documentation and questions to AI or search tools about library usage. Agentic Coding requires coding agents. The Spike Round allows any resources except live human help. For a Spike Round, set up your IDE, agents and cloud accounts in advance, commit often, and save time for a solid README and the 10-20 minute recap.
04
In System Design, fit the architecture to the problem rather than a memorized template. The portal's criteria ask how well you reason quantitatively about scale and what starts breaking with successive orders of magnitude. Be selective and go deep on the few areas that matter, since you do not need to cover the full scope. Perplexity says that if you feel you covered everything worth covering, you probably missed crucial aspects.
05
For the hiring manager deep dive and the founder round, state your personal contribution and ownership precisely. Use Perplexity beforehand and think about where your work could improve its quality. The official guide says all skills listed on your application are fair game, so avoid buzzwords. It also says knowing how to use AI is required, even though building AI products is not.
06
Take the integrity rules literally. For virtual rounds share your full screen on Google Meet and test it beforehand, because Perplexity says it cannot give extra time for screen-share problems. The portal lists AI overlay apps, cheating tools on extra monitors, off-screen help and substitute interviewees as forms of cheating its interviewers say they have seen, and warns that cheating will almost certainly be caught.
04 / The research
Where this page comes from.
Compiled from public sources across 14 sites. Perplexity's own page is among them: interviewresources.perplexity.ai.
- sites
- 14
- coaching and prep guides
- 23
- Perplexity's own pages
- 11
- candidate reports and forums
- 1
Source composition
Where the research comes from
Grouped by the kind of site that published each source: Perplexity's own domain, candidate forums, and everything else.
- Coaching and prep guides23
- Perplexity's own pages11
- Candidate reports and forums1
05 / The questions
Reported questions, by category.
Showing questions for
Roles are grouped by the category each question fits, not by the source.
Practical coding
12 questions
Build a simplified todo list for AI agents: create tasks with increasing IDs, look them up, and move status forward only. Then add task dependencies, where blocked tasks become ready when their prerequisites succeed and fail when any prerequisite fails, directly or indirectly. Then render the list in an LLM-readable format.
Tests a forward-only state machine and dependency graph propagation that must stay efficient on large inputs.
Implement Task Dependencies and Failure.
Tests dependency graph traversal and cascading failure propagation, with attention to efficiency.
In-Memory File System: Strict mkdir, touch, ls, rm, rmdir and a Command Runner.
Tests path parsing and tree or hashmap modeling with strict error handling for mkdir, touch, ls, rm and rmdir.
In-Memory File System: Add cd and Relative Path Support.
Tests relative path resolution and current-directory state layered on an existing tree model.
Implement an in-memory (Unix) file system.
Tests trie or hashmap path modeling, OOP class design and edge cases on paths for mkdir, ls and file content methods.
Implement a time-versioned (timestamped) key-value store with restore.
Tests timestamp-versioned storage design and restoring an earlier state while keeping reads efficient.
Design a CreditTracker with expirations.
Tests stateful class design with time-based expiry, balance accounting and efficient removal of expired credits.
Implement a stream filter that processes text with stop words.
Tests streaming data structure design: filtering stop words in a token stream with deque, heap and hashmap.
Build a byte tokenizer.
Tests byte-level text encoding and tokenizer implementation, a core component of LLM input pipelines.
Implement an LRU cache with TTL expiration.
Tests doubly-linked list plus hashmap design with per-key expiry, and heap-based expiration management.
Implement beam search decoding.
Tests beam search over log-probabilities with pruning and heap operations, core LLM decoding knowledge.
Implement a resilient LLM provider pool.
Tests fault-tolerant design for LLM calls: provider failover, retries and health tracking.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
System design
17 questions
Design a real-time search answer engine.
Tests freshness versus quality tradeoffs across real-time crawling, event detection, caching and LLM integration.
Design an end-to-end RAG (retrieval-augmented generation) pipeline, including citations and hallucination mitigation.
Tests end-to-end retrieval design: hybrid retrieval, reranking, citations and hallucination mitigation.
Design an LLM serving system at low latency.
Tests low-latency inference serving: batching, KV-cache management, model sharding and streaming token delivery.
Architect a streaming response handler for LLM output.
Tests streaming architecture for token-by-token LLM output, including delivery latency and failure handling.
Build a batching and inference optimization layer for embedding models.
Tests request batching and throughput versus latency tradeoffs when serving embedding model inference.
Design a ranking pipeline for a search engine.
Tests multi-stage ranking design for search: retrieval, scoring, reranking and latency budgets.
Design a trending queries ranking system.
Tests streaming aggregation and time-decayed counting to rank trending queries at scale.
Design personalized discovery recommendations.
Tests recommendation pipeline design: candidate generation, ranking and personalization signals.
Design a search system that adapts to constantly changing user interests.
Tests handling interest drift in search relevance with fresh signals and ranking updates.
Design a large-scale web crawler.
Tests crawl scheduling, politeness and rate limiting, duplicate detection and freshness policy at billions of pages.
Design a search autocomplete system.
Tests prefix matching with trie-style indexes, trending query detection and P99 latency constraints.
Design a Long-Running Query Service.
Tests asynchronous job design for slow queries: queues, status reporting, retries and result storage.
Diagnose an overloaded Kubernetes cluster.
Tests systematic debugging of an overloaded cluster using metrics, resource limits, scheduling and scaling.
Design a personal finance aggregator.
Tests integration design for third-party financial data: ingestion, sync, consistency and security.
Design a real-time knowledge graph platform.
Tests graph data modeling, real-time ingestion and query design at scale.
When designing a chat application, how would you decide between using SQL and NoSQL databases?
Tests data model and access pattern reasoning: consistency, scale and query needs for a chat workload.
What techniques can be used to optimize write performance from memory to disk?
Tests storage write-path techniques such as buffering, batching, sequential writes and write-ahead logging.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
ML and LLM depth
4 questions
What metrics would you track to evaluate the performance of your ML pipeline?
Tests choosing offline and online evaluation metrics for an ML pipeline.
How would you determine the right criteria for when to forget outdated data, update the model, and evaluate performance?
Tests model retraining and data freshness policy, including drift detection and evaluation criteria.
What testing methodologies are commonly used to ensure reliability and performance of AI models in production environments?
Tests production ML reliability practices such as shadow testing, canaries, monitoring and regression suites.
How do you design systems around LLM unreliability?
Tests fault-tolerant LLM system design: output validation, retries, fallbacks and evaluation.
Reported problems, listed so you know what to expect. Practice them in your own editor or on the platform you prefer; SupaCV's practice mode coaches how you talk through them.
Every role
Behavioral and hiring manager
5 questions
Tell me about a feature you shipped where you had to make a hard tradeoff between latency and accuracy.
Where does Perplexity lose to traditional search, and how would you fix it?
Tell me about a time you identified a problem no one asked you to fix.
What interests you about AI search?
Why do you want to work at Perplexity?
Your next step
Interviewing at Perplexity?
Make sure your resume gets you to the first round.
Practicing for Perplexity against your resume is in Interview Prep on Career.
Common questions
Quick answers.
How many stages are in Perplexity's interview process?
Perplexity has 11 stages, set out in The process.
What framework does Perplexity use to evaluate candidates?
Perplexity evaluates candidates against Our interviewing philosophy, set out in What Perplexity scores.
What kinds of questions does Perplexity ask?
Perplexity's questions fall into 4 categories, grouped in The questions.
How reliable is this Perplexity interview playbook?
It is compiled from public sources, and the evidence is in The research.
Sources (35)
Every public source this page was compiled from. Links open in a new tab.
14 sites, by sources
- interviewresources.perplexity.ai9
- aced.io9
- prachub.com4
- perplexity.ai2
- techprep.app2
- codemia.io1
- designgurus.io1
- teamblind.com1
- scoutify.com1
- lodely.com1
- orbytlabs.ai1
- jobs.accel.com1
- getbridged.co1
- jointaro.com1
- 01interviewresources.perplexity.ai
- 02interviewresources.perplexity.ai/practical-assessment
- 03interviewresources.perplexity.ai/hands-on-coding
- 04interviewresources.perplexity.ai/hands-on-coding/examples/todo-list
- 05interviewresources.perplexity.ai/spike-round
- 06interviewresources.perplexity.ai/spike-round/instructions
- 07interviewresources.perplexity.ai/agentic-coding
- 08interviewresources.perplexity.ai/system-design
- 09interviewresources.perplexity.ai/core-expertise
- 10perplexity.ai/hub/careers/interview-guide
- 11perplexity.ai/careers
- 12techprep.app/blog/perplexity-interview-process
- 13techprep.app/companies/perplexity
- 14codemia.io/guides/perplexity-software-engineer
- 15designgurus.io/answers/detail/what-is-the-perplexity-interview-proces…
- 16prachub.com/companies/perplexity
- 17prachub.com/companies/perplexity/positions/software-engineer
- 18prachub.com/interview-experiences/perplexity-software-engineer-int…
- 19prachub.com/interview-questions/implement-dependency-aware-to-do-l…
- 20teamblind.com/post/perplexity-interview-zns2oibc
- 21scoutify.com/companies/perplexity/interview
- 22aced.io/questions/5615/design-search-system-adapting-to-user-i…
- 23aced.io/questions/5616/determine-criteria-to-update-model
- 24aced.io/questions/5617/chat-app-sql-vs-nosql
- 25aced.io/questions/5618/write-performance-memory-disk
- 26aced.io/questions/5619/testing-ai-models-in-production
- 27aced.io/questions/5620/evaluate-ml-pipeline-performance
- 28lodely.com/companies/perplexity-ai/interview-questions
- 29orbytlabs.ai/orbyt-jobs/interview-prep/perplexity
- 30aced.io/guides/perplexity-ai-product-manager-interview
- 31aced.io/questions/5845
- 32aced.io/questions/5851
- 33jobs.accel.com/companies/perplexity-2/jobs/85911983-member-of-technic…
- 34getbridged.co/company-reviews/perplexity
- 35jointaro.com/interviews/companies/perplexity
Related reading
- Jake's Resume: Why One LaTeX Template Took Over Tech HiringThe history behind the internet's most-copied resume template, why its formatting choices actually work, and how to get the same layout without touching LaTeX.
- Where the "75% of Resumes Are Rejected by ATS" Stat Came FromThe paper trail behind the most-repeated statistic in job search advice, what applicant tracking software actually does, and what really causes instant rejection.
How similar companies interview
Compare Perplexity's process with other High-Growth Tech & AI companies in this playbook: