About the role
Phyto Nex AI promises customers a 15-minute setup and a read-only footprint. Behind that promise sits a connector platform that has to survive rate limits, partial webhooks, paginated APIs that change shape without notice and month-end spikes where a single customer submits 41,000 receipts in 36 hours. When a connector stalls, AP teams notice before we do, and trust erodes fast.
As a Staff engineer you will set the technical direction for that platform. You will design how we model expense objects across vendors, how we guarantee exactly-once processing for duplicate detection, and how we roll out new connectors without bespoke code for every vendor. You will work closely with partner engineering contacts at our platform partners and represent Phyto Nex AI in their technical reviews.
You will join a platform team of six engineers in Coimbatore and work directly with Karthik, who built the first Concur and Ramp connectors himself. The problems are concrete: a Brex webhook that arrives before the transaction it references, a Navan folio that changes after the trip closes, an Expensify report split across two policies. Each one affects whether a duplicate is caught or a controller sees a false alarm. We value engineers who read vendor changelogs for fun, write migration plans before code and leave every connector easier to operate than they found it.
What you will do
- Define the architecture for connector ingestion, backfill, webhook handling and idempotent replay across 12 integrations.
- Build a vendor-neutral expense object model that preserves line items, card authorizations and approval chains without lossy mapping.
- Design the ERP write-back path so approved deductions and tax classifications land in NetSuite, QBO and Workday with full audit trails.
- Raise the bar on reliability: SLOs per connector, synthetic checks, automated circuit breakers and public status reporting.
- Lead security reviews of every OAuth scope we request and keep our footprint strictly read-only where the vendor allows it.
- Coach senior engineers through design reviews and own the integrations roadmap with the product lead.
What you bring
- 10+ years building backend systems, with deep experience in third-party API integrations at scale.
- Expert in Go, Java or Kotlin, plus strong SQL and event-driven design (queues, outbox patterns, exactly-once semantics).
- Experience designing multi-tenant SaaS systems with strict data isolation.
- Shipped OAuth 2.0 integrations with enterprise vendors and handled scope reviews and app marketplace certification.
- Able to lead through influence across teams and write design docs that settle debates.
Nice to have
- Prior work on SAP Concur, NetSuite SuiteTalk or Workday Web Services APIs.
- Experience in fintech, payments or accounting systems where reconciliation correctness matters.
- Familiarity with SOC 2 evidence collection for change management and access control.
Your first 90 days
First 30 days
Ship a production fix in the Navan connector and write an assessment of our ingestion failure modes.
By day 60
Publish the design for the unified connector SDK and get sign-off from platform and audit engine leads.
By day 90
Land the first two connectors on the new SDK with per-connector SLOs visible on our status page.