Perplexity Interview Question Bank
Perplexity interviews lean toward long, product-flavored engineering simulations rather than generic LeetCode. Candidates should expect Python-first coding, incremental multi-part specs, careful edge-case preservation across parts, and system-design conversations tied closely to search, discovery, retrieval, inference, and operational reliability.
17
questions
Last updated
Before you start
Showing 17 of 17
Design an In-Memory File System with Non-Recursive mkdirAnalyze Daily CTR and Data Quality in a Large JSONL DatasetSort Topic Names by Prefix and Numeric SuffixChange Directory with Relative Path SupportImplement an In-Memory File SystemIncremental Per-Context Entry Numbering and Late-Data BackfillDesign an In-Memory Unix File SystemDesign an In-Memory File System with Shell CommandsCommand-Line In-Memory File SystemDesign In-Memory File SystemDesign an In-Memory Unix File System and Implement Basic CommandsImplement an OOP ToDo List with Task CRUD, Status, and Dependencies (Cascade Updates)Design an In-Memory File System (Trie-based)Debug Failures (Identify Root Cause from Symptoms)Log Processing (Parsing & Aggregation)DFS with Memoization (Top-Down DP)Fix Existing Code (Bug Fixing)Parse citation numbers from paragraphs and reorder/deduplicate sources by first appearanceBuild a Discover-like News Feed Page with Infinite Scroll and Repeating LayoutImplement a Dependency-Aware Todo List with Cascade FailureEstimate Token CountImplement Tokenize FunctionUnderstand Code FunctionalityOptimize Byte Tokenization and Estimate Token CountImplement ToDo list for AIDepth-First Search ProblemBinary Classification using scikit-learnImplement ToDo List for AI