Full-Time

Member of Technical Staff

Offensive Security Engineer

Updated on 9/4/2026

Perplexity AI

Perplexity AI

1,001-5,000 employees

Advanced answer engine delivering source-backed replies

Compensation Overview

$220k - $405k/yr

Remote in USA + 3 more

More locations: London, UK | San Francisco, CA, USA | New York, NY, USA

Hybrid

Hybrid work is indicated for the listed on-site locations.

Category
Cybersecurity (1)
Required Skills
Kubernetes
Python
Threat modeling
Machine Learning
Vulnerability Analysis
AWS
Go
REST APIs
Penetration Testing
DevOps

Get referred to Perplexity AI

See people who can refer or advise you

Requirements
  • The candidate must have 5+ years of hands-on experience in offensive security, red teaming, or penetration testing.
  • The candidate must have deep technical expertise in at least two of cloud security (AWS, GCP, or Azure), web/API application security, Kubernetes and container security, macOS/Linux endpoint security, network penetration testing, or CI/CD pipeline security.
  • The candidate must have a track record of discovering impactful vulnerabilities or developing novel attack techniques in production environments.
  • The candidate must have strong programming and scripting skills in Python, Go, or similar languages and be comfortable writing custom tooling and exploits.
  • The candidate must have experience with industry-standard offensive tools such as Burp Suite, Cobalt Strike, Sliver, Mythic, Metasploit, BloodHound, and nuclei, and be able to operate beyond them.
  • The candidate must have excellent written and verbal communication and be able to translate complex technical findings into clear risk narratives.
  • The candidate must have experience assessing artificial intelligence and machine learning systems, large language model applications, or agentic workflows for security vulnerabilities.
Responsibilities
  • Plan and execute red team and purple team engagements simulating advanced threat actors across cloud infrastructure, including AWS and Kubernetes, endpoints, and application surfaces.
  • Conduct continuous penetration testing of web applications, application programming interfaces, mobile clients, browser extensions, cloud infrastructure, and internal services.
  • Assess artificial intelligence and machine learning-specific attack surfaces, including prompt injection, model exfiltration, agent abuse, tool-use exploitation, and MCP security boundaries.
  • Develop and maintain custom offensive tooling, exploits, and automation to improve the efficiency and coverage of security testing.
  • Perform open-scope adversary simulations that test detection and response capabilities end to end, collaborating closely with the defensive security team.
  • Drive threat modeling sessions with engineering teams to identify and prioritize attack vectors in new features and architectures.
  • Deliver clear, actionable findings to technical and executive audiences and partner with engineering to validate remediations.
  • Contribute to the security of continuous integration and continuous delivery pipelines, supply chain integrity, and secrets management through offensive assessment.
  • Stay current on emerging attack techniques, vulnerability research, and adversary tradecraft and bring external perspective into the security strategy.
Desired Qualifications
  • Published security research, conference talks (DEF CON, Black Hat, BSides), CVE credits, or meaningful bug bounty contributions.

Perplexity AI provides an answer engine that delivers precise, reliable responses to user questions by using up-to-date sources. It serves individuals who want quick answers and businesses that need detailed information, drawing on current data and source links to back its results. The product works by retrieving information from reputable sources, compiling concise answers, and presenting citations to ensure trustworthiness. It differentiates itself from competitors by prioritizing current, source-backed information and offering access that spans personal and enterprise use, potentially supported by subscriptions, advertising, and partnerships. The company's goal is to be a dependable tool for immediate, accurate information across a wide range of queries.

Company Size

1,001-5,000

Company Stage

Private

Total Funding

$1.8B

Headquarters

San Francisco, California

Founded

2022

Get referred to Perplexity AI

See people who can refer or advise you

Simplify Jobs

Simplify's Take

What believers are saying

  • Reuters reported Aug. 23, 2026: Nvidia discussed investing at over $30 billion.
  • Intuit launched QuickBooks and Mailchimp connectors on Aug. 31, 2026.
  • Perplexity released PII-Tracer and PII-TRACE on Sept. 1, 2026.

What critics are saying

  • CNN sued Perplexity on May 28, 2026, alleging copying 17,000 works.
  • Perplexity faces multiple publisher lawsuits in New York, risking injunctions and licensing costs.
  • If courts restrict scraping, Perplexity's answer engine loses core retrieval data and differentiation.

What makes Perplexity AI unique

  • Hybrid Compute splits tasks between Apple Silicon Macs and frontier cloud models.
  • Enterprise Spaces unifies Slack, Drive, Notion, GitHub, Jira, and PostgreSQL with citations.
  • Intuit, OpenSea, and other connectors embed Perplexity Computer inside real workflows.

Help us improve and share your feedback! Did you find this helpful?

Benefits

Health Insurance

Dental Insurance

Vision Insurance

401(k) Retirement Plan

Company Equity

Company News

AIDeveloper44
Sep 3rd, 2026
Perplexity releases Lily for local Qwen 35B inference on Apple Silicon.

Perplexity releases Lily for local Qwen 35B inference on Apple Silicon. Perplexity has introduced Lily, a Metal inference server optimized for running Qwen 35B models on Apple hardware with advanced session caching. AIDeveloper44 Team Perplexity's Lily project brings high-performance Qwen 35B inference to future Apple Silicon hardware. * Lily is an open-source Metal inference server designed specifically for Qwen3.6-35B-A3B models using MLX 4-bit weights. * The software requires Apple GPU family 10 (M5 chips) and macOS 26 to utilize specific Metal tensor operations. * It features a two-entry LRU session prefix cache and runtime-compiled Metal kernels to optimize token decoding. Overview of the Lily inference server. Perplexity has shared new developments in its open-source inference technology through the release of Lily, a specialized inference server hosted in the pplx-garden repository. Lily is a minimal Metal-based server built in Rust, designed to facilitate local execution of a specific large language model (LLM) checkpoint: the Qwen3.6-35B-A3B. The tool is tailored for Apple Silicon and focuses on efficient, on-device inference by utilizing the MLX framework's quantization standards. Unlike general-purpose inference engines that support a wide variety of models and quantization formats, Lily is intentionally restricted. It is designed to work exclusively with MLX affine 4-bit weights with a group size of 64. The server validates the architecture and quantization layout at the time of loading, rejecting unsupported formats such as GGUF, AWQ, GPTQ, or standard floating-point weights (BF16, fp8). This strict adherence to a specific architecture allows for deep optimization within the Metal environment. Hardware and software prerequisites. According to the technical documentation provided in the Lily repository, the server has specific hardware and software requirements that point toward future-facing Apple technologies. The project specifies the need for Apple GPU family 10 or later, which corresponds to M5 series chips and newer. Additionally, the software requires macOS 26 or later to support necessary Metal tensor operations. The build process is managed via Rust 1.92, as pinned by the project's toolchain configuration. For model compatibility, users must provide a local Qwen3.6-35B-A3B MLX checkpoint. Perplexity specifically recommends the mlx-community revision `38740b847e4cb78f352aba30aa41c76e08e6eb46` for benchmarking and testing, ensuring that the quantization remains immutable for performance tracking. Technical architecture and kernel design. The core of Lily lies in its Metal kernels, which are responsible for the computational heavy lifting on the GPU. These kernels are not pre-built; they compile from source at runtime, eliminating the need for an offline shader build step. The source layout of the project indicates a highly modular approach to these components: * src/kernels/: Contains the Rust dispatch logic and the raw Metal shader source files. * src/model.rs: Defines the prefill and single-token greedy model graph. * src/weights.rs: Handles the loading of MLX affine Q4 weights into memory. * src/config.rs: Performs strict validation of the 35B-A3B checkpoint parameters. By focusing on greedy decoding - where the model always selects the most likely next token - Lily simplifies the generation loop. This design choice is reflected in src/generate.rs, which manages the tokenizer-backed decode sequence without the overhead of complex sampling parameters like temperature or top-p. The session prefix cache. One of the distinctive features of Lily is its implementation of a fixed two-entry Least Recently Used (LRU) session prefix cache, located in src/serve/session.rs. This cache is designed to improve efficiency during interactive conversations. When a new prompt is received, the server checks if the token sequence matches a sequence already stored in the cache. A state is only reused if the new prompt's token sequence is a strict prefix of the existing entry. Users can manage this behavior through an optional prompt_cache_key. While providing a key allows the server to prefer a specific cache entry, the system still mandates token equality to ensure accuracy. The server reports the number of reused tokens in the response metadata under usage.prompt_tokens_details.cached_tokens, providing transparency regarding the efficiency gains of the cache during multi-turn interactions. API surface and implementation limits. Lily exposes a minimal subset of the OpenAI chat completions API. It supports standard endpoints such as POST /v1/chat/completions, GET /v1/models, and GET /health. However, the request surface is deliberately constrained to maintain stability and performance. The server only accepts text-only system, user, and assistant messages. Furthermore, it enforces that the final message in a request must have the "user" role. Many standard API features are explicitly rejected by Lily to maintain its minimal footprint. These include streaming responses, tool calling (function calling), multimodal content, and speculative decoding. The server also disables "thinking" templates for the checkpoint, focusing purely on direct text generation. The -max-seq flag controls the total token capacity for the prompt and completion, which is capped at 262,144 tokens by the kernel, though it is often further restricted by the checkpoint's own max_position_embeddings. Open source contributions and licensing. As part of the pplx-garden initiative, Lily is released under the Apache-2.0 license. This allows developers to inspect, modify, and integrate the inference server into their own workflows on Apple Silicon. The repository includes comprehensive testing suites, covering CPU-reference kernel tests, API surface validation, and tokenizer accuracy. For developers with the 35B checkpoint available, the repository provides golden tests to verify output consistency against known benchmarks. References & Sources

MezoSoftDotNet
Sep 2nd, 2026
Perplexity launches Hybrid Compute to split tasks between cloud and local AI.

Perplexity launches Hybrid Compute to split tasks between cloud and local AI. Moaataz Anwar September 02, 2026 0 Comments AI search company Perplexity has announced the launch of Hybrid Compute, a privacy-focused framework integrated directly into its native Mac platform. Following the initial release of its agentic Perplexity Computer ecosystem, the new feature allows users to split complex computational workflows between powerful cloud-hosted frontier models and isolated local large language models (LLMs) running natively on their own hardware. The system is engineered to secure highly sensitive user data on-device while simultaneously reducing cloud computing costs. Data confidentiality and the privacy gate architecture. The primary objective behind Hybrid Compute is providing a secure environment for enterprise professionals handling proprietary information. For instance, legal professionals can utilize the platform to draft case briefs, allowing an on-device model to process private client files locally while offloading public case law research to cloud infrastructure. To automate this workflow, Perplexity developed a specialized privacy classifier model. Whenever a user initiates a task or uploads documentation, this classifier scans the content for sensitive strings. It then presents an interactive "privacy gate" UI, letting the author review exactly which data slices will be isolated locally and which unclassified elements will be sent to cloud endpoints like Opus 5 or GPT-5.6 Sol. Local model selection and terminal-free installation. Before launching an analytical task, users can explicitly choose which local model configurations they want to run on their personal machine. At launch, the pre-configured local options include: To keep the platform accessible to non-technical professionals, the installation pipeline is fully abstracted. Users do not need to open the macOS terminal or configure code environments; the native Perplexity application handles the model downloads and storage indexing automatically behind the scenes. System monitoring, costs, and cross-device queuing. While an active task is running, the interface displays a real-time system visualization dashboard. This console tracks localized CPU, GPU, and unified memory usage alongside a sidebar counter displaying token consumption. Crucially, enterprise clients and retail subscribers are not charged for any tokens processed or generated by the local hardware, providing an avenue for thrifty teams to lower their monthly API inference costs. Once Hybrid Compute compiles the primary output, users can continue refining the data using standard natural language follow-up prompts. Additionally, users can leverage an iPhone app link to remotely queue up heavy tasks to their Mac from a mobile device while away from the workstation. Performance trade-offs and hardware prerequisites. Perplexity openly acknowledges that a hybrid output represents a slight compromise compared to a 100% frontier cloud pipeline, noting that fully cloud-based architectures will almost always deliver superior results in raw asset generation. However, the company emphasizes that local splitting represents a necessary sliding scale for users who value data sovereignty and operating costs over raw model capability. During the initial rollout, Hybrid Compute is restricted exclusively to Apple Silicon Macs running macOS 15. Due to the high hardware demands of local model execution, Perplexity recommends host machines be equipped with at least 32GB of unified memory. The feature is available immediately to Pro, Max, and Enterprise tier subscribers. Upgrade Laptop Hardware #PerplexityAI #HybridCompute #DataPrivacy #MacApp #LocalAI Posted bymoaataz Anwar.

ZenTech Academy
Sep 2nd, 2026
Perplexity introduces PII-TRACE benchmark and PII-Tracer on-device detector - unite.ai.

Perplexity introduces PII-TRACE benchmark and PII-Tracer on-device detector - unite.ai. Perplexity on September 1, 2026, introduced PII-TRACE, a benchmark for evaluating detectors of personally identifiable information, and PII-Tracer, a compact 0.6B-parameter model built to flag PII on a user's device before text is sent to cloud models. The announcement frames both releases as privacy infrastructure for the company's hybrid compute architecture, in which cloud agents handle research, reasoning, and planning while a local model works with private files. Under that architecture, a local privacy gate keeps sensitive content on the Mac, redacts detected private information, or requests approval before sending it to the cloud. Perplexity said the boundary only protects privacy if the device can recognize PII before text is sent to a remote model, and that detection becomes harder across long, multilingual conversations where the same identifier may appear several times across different turns. One missed mention can expose the information the system is meant to protect. PII-Tracer supplies one local control signal for model routing by flagging spans predicted to contain PII. The application then enforces the routing policy: it keeps the relevant input local, redacts detected spans, or requests explicit approval before escalating to a cloud model. The PII-TRACE benchmark. PII-TRACE, short for Tracing Recurring PII Across Conversational Exchanges, contains 13,148 synthetic user-assistant conversations across 13 languages and 10 writing systems, with 37,431 identifier mentions labeled at the character level across nine PII types. A total of 41% of the conversations contain structured content. Among the 5,645 conversations with labeled PII, 63.8% include an identifier that appears more than once, and 28.7% include an identifier that appears across multiple turns. Perplexity said it designed the benchmark around three behaviors that matter when a detector screens assistant conversations. The first is consistent coverage: when an identifier appears several times or crosses user and assistant turns, the detector needs to find every mention. The second is robustness to long context, with conversations ranging from fewer than 1,000 to more than 100,000 characters. The third is handling multiple languages and mixed-format content, since a conversation may switch languages and combine prose with code, tables, or structured records. The benchmark measures performance at two levels. At the identifier level, a consistent detection score asks whether the detector covered every character in every mention of the same identifier, reported separately for identifiers with multiple mentions and for identifiers that repeat across turns. At the character level, precision measures how much of the text marked by a detector is labeled PII, recall measures how much labeled PII it finds, and F1 balances the two. The dataset is synthetic but derived from production conversations. According to the company, multiple language models first mark nine types of PII in production user-assistant conversations, and a rule-based pass groups repeated identifiers of the same type under one entity ID. Each marked value is replaced by a typed placeholder, each turn is paraphrased with placeholders intact, and synthetic values matching each identifier's type and format are inserted. Three automated gates check that replacements match the stored spans, that repeated mentions use the same value, and that marked source values are absent under a Presidio and regular-expression rescan. A second language model audits a sample, and humans review anything it flags as PII. A compact detector for local use. PII-Tracer is a 0.6B bidirectional encoder adapted from a Qwen3 backbone. Perplexity said privacy screening differs from text generation because it requires finding relevant PII spans and returning their boundaries, so the model replaces Qwen3's causal mask with padding-aware bidirectional attention, letting every token draw on both earlier and later turns within a 4,096-token window. For each token, the encoder produces a 1,024-dimensional representation, and a linear tagging head scores 37 possible labels under the BIOES scheme for named entity recognition: one label for text outside a PII span, plus four span-position labels for each of the nine PII types. An auxiliary head predicts whether the conversation contains sensitive material, such as health or religious information. The company said it trained the model for three epochs on roughly 714,000 training samples combining multilingual assistant conversations with single-record examples. At inference time, a constrained Viterbi decoder searches for the highest-scoring valid label sequence and maps the result back to exact character spans for redaction or local routing. Evaluation results. Perplexity reported that PII-Tracer achieved the highest character F1 (0.629) among the 12 systems evaluated, along with the second-highest span-overlap F1 and span-containment F1. The company said frontier models, namely GPT-5.6-sol and Claude Sonnet 5, achieved comparable overall performance, with GPT-5.6-sol scoring higher on both span-level metrics but lower on character F1. It noted that those frontier models have hundreds of billions or even trillions of parameters and are closed-source models hosted in the cloud, making them unsuitable for screening text that must remain local, while other open-source PII detectors performed substantially worse than PII-Tracer. On the consistency test, the evaluation set contains 899 identifiers that appear once and 959 that appear more than once, 790 of them spanning multiple turns. Perplexity reported that PII-Tracer finds every mention of 79.4% of recurring identifiers and 77.6% of cross-turn identifiers, while GPT-5.6-sol reaches 57.0% and 55.1% on the same two measures. PII-Tracer's score moves from 0.917 for single-mention identifiers to 0.691 for identifiers appearing six to ten times. Length remains a limitation. Single-window recall is 0.975 for conversations below 1,000 characters and 0.955 from 1,000 to 10,000, but drops to 0.687 at or above 10,000 characters. The company said decoding the same checkpoint with 50%-overlap sliding windows raises overall character recall from 0.830 to 0.965 and multi-mention consistent detection from 0.794 to 0.954, without retraining. Across a six-language slice spanning Latin, Cyrillic, and Hangul scripts, PII-Tracer leads character F1 in German (0.735), French (0.633), Italian (0.676), and Russian (0.651), and sits within 0.016 and 0.036 of the best results in English and Korean, the company reported. On five external single-record benchmarks, Perplexity said PII-Tracer posted higher character F1 than the OpenAI Privacy Filter on every dataset, including 0.950 versus 0.907 on ai4privacy, 0.847 versus 0.709 on Nemotron-PII, and 0.594 versus 0.350 on TAB, the only benchmark in the group built from real, human-labeled text. The research paper cautions that the conversations are synthetic reconstructions derived from the structure of production assistant traffic, so results should be read as measurements of conversational PII detection rather than estimates for any particular production workload. The paper also notes that tool calls, inter-agent messages, and multimodal inputs fall outside the benchmark's scope, and that each baseline was evaluated under a single inference configuration. Perplexity said it plans to release both PII-TRACE and PII-Tracer soon; the paper states both will be released under the MIT license.

Apple World Today
Sep 1st, 2026
Perplexity introduces hybrid computing on the Mac.

Perplexity introduces hybrid computing on the Mac. posted on Sep. 01, 2026 at 11:05 am Perplexity is launching what is says is the first-ever hybrid inference orchestrator, debuting on Apple silicon. A Mac can now become the local half of one continuous Perplexity Computer task, working alongside frontier cloud models without the user switching modes, restarting the work, or managing the handoff. Here's how it works: the Mac's computing starts in the cloud for its hardest reasoning, search, and planning, then calls on a local model running on Apple silicon when a step involves sensitive information. An on-device Privacy Gate checks prompts, tool outputs, memory, and logs before anything reaches the cloud. Users can even start a task from an iPhone and send its local steps to their Mac. "For Mac users, the computer already on their desk is no longer just a window into cloud AI," says Perplexity spokesperson Beejoli Shah. "Its Apple silicon becomes active compute inside the workflow, handling private steps locally while frontier models take on the rest. Apple mentioned Perplexity in its second quarter earnings call, and hybrid compute shows why the Mac is becoming a serious AI machine." Here are details from a Perplexity fact sheet: ° Truly hybrid inference requires a harness that can orchestrate models, files, and tools, as well as compute across the cloud and local device. ° Hybrid compute on computer begins in the cloud, using the most capable frontier models available. When a step involves sensitive data, Computer orchestrates down from the cloud to the device without restarting the task or losing context. This differs from local compute, which Perplexity launched on NVIDIA DGX Spark last week. Local compute starts on the user's hardware and orchestrates up to frontier cloud models only with permission. ° The cloud will handle frontier reasoning, web search, and long-horizon planning, while the local subagent handles private files, local data, and actions on the device. ° A Perplexity-trained Privacy Gate runs on the device and identifies sensitive information such as names, addresses, account numbers, and secrets. Computer flags that information before anything is sent to the cloud, and the user decides where that portion of the task runs. ° Users can start a task from any Apple device, including an iPhone, and send local steps to their Mac without restarting. Computer completes the cloud and local work seamlessly within one task, returning a single result. That opens up work most people would never hand to a cloud-only agent: privileged legal documents, confidential client data, and patient records. ° At launch, users can choose from three local models: Gemma E4B, Qwen3.6 35B-A3B, a Perplexity post-trained version of Qwen3.6 35B, with more to follow. Setup takes one click inside the desktop app, with no terminal required. ° Users are not charged for any tasks that run locally. Charges only apply for frontier model usage. ° No new hardware is required to run hybrid compute. It works on any Apple silicon Mac running macOS 15 and higher. ° Due to the size of more advanced local models, it runs the best on devices with at least 32GB of unified memory. ° Enterprise admins can set one organization-wide sensitivity policy for the company and see a full record of what leaves each device. Hybrid compute will be available through the Perplexity desktop app on Apple devices with Apple silicon. I hope you'll help support Apple World Today by becoming a patron. Almost all our income is from Patreon support and sponsored posts. Patreon pricing ranges from $2 to $10 a month. Thanks in advance for your support. Dennis Sellers is the editor/publisher of Apple World Today. He's been an "Apple journalist" since 1995 (starting with the first big Apple news site, MacCentral). He loves to read, run, play sports, and watch movies.

MaChaSh
Sep 1st, 2026
Perplexity launches privacy-minded 'hybrid compute' AI feature for Mac.

Perplexity launches privacy-minded 'hybrid compute' AI feature for Mac. * 9to5Mac By Zac HallSep 1, 2026, 11:20 am95 pts Aside from being featured by Apple in the M6 Mac mini launch, Perplexity has been relatively quiet on the Mac front this summer. That changes today with hybrid compute for Mac. more... Read Article Share Article * email * x.com * facebook * pocket * reddit * tumblr * linkedin * pinterest