Software Engineer, Enterprise Knowledge Platform

About this role

ABOUT THE ROLE The Enterprise Knowledge Platform team builds the data and action layer that connects Perplexity's agents to the systems where enterprise work happens.

• Function: Infrastructure
• Seniority: mid

Location & pay

On-site · San Francisco · California · United States Listed pay on Jobrow: $220k–$405k.

Source

Jobrow reads the public Ashby board for Perplexity. First seen 11 days ago; last seen 11 days ago; closed 11 days ago. We are not the employer — apply only on the company ATS.

Posting

ABOUT THE ROLE The Enterprise Knowledge Platform team builds the data and action layer that connects Perplexity's agents to the systems where enterprise work happens. Useful agents need more than access to APIs: they need to discover the right tools, understand an organization's data and terminology, and act reliably within its permissions. This team brings native connectors, MCP servers, and CLI-backed tools into a consistent platform, and builds the marketplace through which customers adopt integrations and partners extend the ecosystem. This is a product and platform engineering role with end-to-end ownership, from designing connector infrastructure and semantic models to shipping the experiences customers use to discover, connect, and activate integrations. You'll build the runtime that executes tool calls, the knowledge layer that makes enterprise context reusable across connectors, and the developer and marketplace foundations that help the ecosystem grow. Working with AI Research and Enterprise teams, you'll turn fragmented systems into reliable, permission-aware capabilities that agents can use to complete real work. The impact is direct: every improvement helps customers put their existing software and knowledge to work through Perplexity. KEY RESPONSIBILITIES - Own the connector runtime that registers, hosts, and executes native connectors, hosted MCP servers, and CLI-backed tools through a consistent agent-facing interface. - Build the semantic and knowledge layer, including tool and entity schemas, capability metadata, relationships, organization-specific terminology, and reusable corrections, while preserving provenance and source-system permissions. - Design discovery, search, and recommendation systems that help agents find relevant tools and context and help users and organizations choose integrations that fit their work. - Build the marketplace and activation experience end to end, from browsing and recommendations to installation, configuration, admin enablement, and ongoing adoption. - Make connector execution reliable and observable, with structured results, retries, idempotency, pagination, rate-limit handling, and recovery from partial failures. Own reliability targets, production monitoring, and incident response. - Implement connector authentication, credential isolation, and permission enforcement, partnering with Trust & Governance, Security, and Backend Platform on shared policies and tenant boundaries. - Bu