Perplexity Software Engineer Phone Screen Questions
3+ questions from real Perplexity Software Engineer Phone Screen rounds, reported by candidates who interviewed there.
What does the Perplexity Phone Screen round test?
The Perplexity phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.
Top Topics in This Round
Perplexity Software Engineer Phone Screen Questions
## Problem You have `n` servers and a list of request assignments `(server_id, request_weight)`. A distribution is considered "balanced" if the maximum total weight on any server minus the minimum total weight is at most `threshold`. Write a function that checks whether a given assignment is balanced and, if not, returns the servers causing the imbalance. ```python def check_distribution( n: int, assignments: list[tuple[int, float]], threshold: float ) -> tuple[bool, list[int]]: """Return (is_balanced, list_of_imbalanced_server_ids).""" pass ``` ``` Input: n=3, threshold=5.0 assignments = [(0,10),(1,8),(2,20),(0,5),(1,7)] # Server totals: 0->15, 1->15, 2->20 # max-min = 20-15 = 5 <= 5 -> balanced Output: (True, []) assignments = [(0,10),(1,3),(2,20)] # Totals: 0->10, 1->3, 2->20. max-min=17 > 5 Output: (False, [1, 2]) ``` ## Follow-ups 1. Define "imbalanced server" clearly — is it servers above average, below average, or at both extremes? 2. How would you rebalance by moving the minimum number of requests? 3. Extend to a real-time streaming version where `check_distribution` is called after each new assignment. 4. How would you write a SQL query to find imbalanced servers if assignments are stored in a table?
## Problem Validate a dependency graph for cycles or ordering conflicts, using topological sort. ## Likely LeetCode equivalent Similar to LC 207 Course Schedule. ## Tags coding, graph, topological_sort, phone
## Problem Given a list of text documents and a stopword list, remove all stopword occurrences from each document. Matching is case-insensitive. Preserve original word casing for non-stopwords. Return the filtered documents. ```python def remove_stopwords( documents: list[str], stopwords: list[str] ) -> list[str]: pass ``` ``` Input: documents = ["The quick brown fox", "A dog and a cat"] stopwords = ["the", "a", "and"] Output: ["quick brown fox", "dog cat"] # Extra spaces collapsed, original case preserved for kept words. Input: documents = ["IS THIS WORKING"] stopwords = ["is", "this"] Output: ["WORKING"] ``` ## Follow-ups 1. What data structure do you use for stopword lookup, and why? 2. How do you handle punctuation attached to words (e.g., `"fox,"` where `"fox"` is a stopword)? 3. For a corpus of 10 million documents, how would you parallelize this pipeline? 4. Extend to support language-specific stopword lists that are selected based on detected document language.
What to Expect in the Perplexity Phone Screen Round
The Perplexity Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 3+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Phone Screen round at Perplexity show recurring patterns in difficulty and topic distribution. The Phone Screen round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Phone Screen Round Timing and Format
The Phone Screen round at Perplexity typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Perplexity Software Engineer Phone Screen commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 3 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access