Connector Platform Engineer

  • Location: Remote
  • Department: Platform
  • Employment Type: Full-time

What’s in it for you?

Every service a customer connects becomes a tool Pax can use. Gmail and LinkedIn came first [Live]. Calendar, Slack, meetings, storage, finance, and signature tools follow. Each one is a surface where Pax stops being a chat window and starts doing the work.

You would own the pattern that makes each new connector fast to add and boring to maintain. Get that right and the product’s reach stops being limited by engineering time.

About the team and the opportunity

Paciva does not use the MCP protocol for its own reasoning path. The platform speaks to services directly and keeps the model focused on judgment. That is a deliberate architectural bet, and it is part of why the product feels quick.

The connector pattern is already designed. Dozens are planned. The gap is a person who owns the whole surface, from authentication and rate limits through sync behavior and failure recovery.

A day in the life

You ship a connector for a service a beta customer asked for on Friday. You find its rate limits are stricter than documented, so you rework the sync schedule and add backoff that degrades without dropping work. Later you review a partner’s API changes and update three connectors before anyone notices a break.

What you will work on

  • Own the connector framework, including authentication, sync, retries, and recovery
  • Ship new connectors on a predictable cadence, with tests and documentation
  • Handle multiple accounts of the same service per user, including personal and work separation
  • Build the health signals that tell a customer when a connection needs attention
  • Work with the enterprise motion on customers who point Pax at their own internal servers
  • Keep raw customer content inside Paciva unless the customer opts in per source
  • Reduce the time to add connector number fifty below the time it took to add number five

What we need from you

  • 4+ years in backend engineering with heavy third party API work
  • Scars from OAuth, token refresh, webhook delivery, and partner rate limits
  • Strong judgment about what to sync, what to cache, and what to leave alone
  • Care for data handling, permissions, and least privilege by default
  • Ability to write a connector spec another engineer can follow
  • Preference for one good pattern applied twenty times over twenty clever exceptions

Remote work, compensation, and benefits

This is a remote role. Paciva is based in Miami, Florida & Austin Texas and the team works across time zones. We value clear written communication, ownership, practical collaboration, and dependable follow-through. Compensation is based on experience, skills, location, market data, role scope, and internal equity. For sales roles, compensation may include base salary and variable incentive compensation. Final details will be shared during the hiring process. Most roles include occasional travel for team meetings, customer sessions, company events, or off-sites.

Equal opportunity statement

Paciva is an equal opportunity employer. We make employment decisions based on qualifications, merit, business needs, and role fit. We do not discriminate based on race, color, religion, sex, sexual orientation, gender identity or expression, national origin, age, disability, veteran status, genetic information, marital status, pregnancy, caregiver status, or any other status protected by applicable law. If you need a reasonable accommodation during the application or interview process, please let us know. We will work with you to support your participation.