Member of Technical Staff (Software Engineer, Connector Platform)

About

the Role The Connector Platform team builds the data layer that lets Perplexity's agents reach into the world's software. This team owns the systems that turn hundreds of heterogeneous integrations (native, MCP, CLI, first-party, and third-party APIs) into one unified, reliable, well-typed surface that agents can call with confidence. The connector platform is the core layer that forms the knowledge layer for Computer: it is how the agent discovers what tools exist, understands what each one means, decides which to call, and grounds its reasoning in real, permissioned, up-to-date enterprise data. We maintain a knowledge layer above connectors that pushes and pulls context into them, rather than letting each connector hoard org knowledge on its own, making Computer the source of truth for institutional knowledge. Models are commoditizing; grounded, actionable, permissioned access to a customer's real systems is not. When this layer is fast, accurate, and semantically rich, every agent built on top of it gets smarter; when it is weak, no amount of model quality compensates. Key

Responsibilities Own the design and implementation of the connector runtime, the system that registers, hosts, and executes built-in connectors, hosted MCP servers, and CLI-backed tools behind a single agent-facing interface. Build and extend the semantic layer: tool and entity schemas, capability metadata, relationship modeling, and the mechanisms for capturing and applying organization- and account-specific corrections and knowledge. Design the tool-discovery and tool-selection surfaces that agents use to find the right connector and call it correctly, optimizing for both model accuracy and context efficiency. Make agent loops robust: structured results, partial-failure and retry semantics, idempotency, pagination, rate-limit handling, and observability into every tool call an agent makes. Define authentication, authorization, and credential-isolation patterns for connectors (OAuth flows, BYOK, per-org credential boundaries), partnering with Security and Backend Platform on defense-in-depth. Build the connector onboarding path (schemas, fixtures, and evaluation suites) so new connectors ship with measurable quality rather than hope, and drive the eval metrics that tell us a connector actually works inside agent loops. Set the technical bar for connector reliability and operability: SLAs, observability, error-rate monitoring, and incident response for an always-on, high-fan-out integration surface. Partner with product and AI teams to define clear connector interfaces and integration patterns so new agent capabilities can reliably build on the shared platform.