Listing unavailableEngineeringHybrid

Member of Technical Staff (Software Engineer, Connector Platform)

This listing is no longer verified as available.

MeritLog keeps this source-backed description for reference. Availability is not verified, and there is no application link here.

Last seen by MeritLog September 12, 2026Source: AshbySource version: ashby-public-job-posting-v1

Source: the employer's Ashby job board. Open the original listing for current details. Availability is not verified for this retained page.

Job details

Work model: Hybrid
Salary: Not listed by source
Location: San Francisco

What the role asks for

What you'd do

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.

What they're asking for

Experience designing and building backend systems that run in production (typically 4+ years for mid-level, more for senior and staff).Experience
Strong system design skills, with a track record of building efficient, reliable, and scalable architectures, ideally including API integration, gateway, or platform-style systems with many heterogeneous downstreams.SkillPreferred
Strong proficiency in at least one backend language such as Python, Go, or Rust, and the ability to work effectively in a multi-language environment.Skill
Hands-on experience with modern infrastructure (for example AWS, Kubernetes, and related cloud technologies).Skill
Depth in at least one of: OAuth and authorization protocols, API/connector or MCP-server development, schema and semantic modeling, or building tooling and evaluation for LLM-based agents.Skill
Comfort working in security-sensitive areas (auth, authorization, credential isolation) and making pragmatic trade-offs between safety, simplicity, and velocity.Skill
Collaborative mindset and eagerness to solve hard, ambiguous problems alongside other experienced engineers.Skill

Parsed by MeritLog from the employer’s own posting. The full description follows below.

Job description

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. QUALIFICATIONS - Experience designing and building backend systems that run in production (typically 4+ years for mid-level, more for senior and staff). - Strong system design skills, with a track record of building efficient, reliable, and scalable architectures, ideally including API integration, gateway, or platform-style systems with many heterogeneous downstreams. - Strong proficiency in at least one backend language such as Python, Go, or Rust, and the ability to work effectively in a multi-language environment. - Hands-on experience with modern infrastructure (for example AWS, Kubernetes, and related cloud technologies). - Depth in at least one of: OAuth and authorization protocols, API/connector or MCP-server development, schema and semantic modeling, or building tooling and evaluation for LLM-based agents. - Comfort working in security-sensitive areas (auth, authorization, credential isolation) and making pragmatic trade-offs between safety, simplicity, and velocity. - Collaborative mindset and eagerness to solve hard, ambiguous problems alongside other experienced engineers. If you’re excited about this role, we encourage you to apply even if your experience doesn’t match every qualification listed above.

Keep exploring

Available Engineering roles

These current listings are available to explore now.

Search all jobs