Senior Engineer, Partner Integration
a2z-sync · Denver, Colorado, United States · Full time · $160,000–$180,000 a year
Posted 2026-11-18
What this role cares about
- Microservices
- Moblie App Development
- Code Maintaining
- Full Stack Development
- API Programming
- CI/CD Pipelines
- Troubleshooting/Debugging
- Data Pipelines
- Cyber Security
- Testing
- Front-end Development
- Database Management
- Software Development
- Cloud Infrastructure
Tools: APIs, AWS, AWS Lambda, CloudWatch, MySQL, Python, CircleCI, API, S3
Job description
# Senior Engineer, Partner Integration
> A2Z Sync · Denver, United States (Remote) · Full-time · Posted 2026-11-18
**Salary:** USD 160,000–180,000
**Workplace:** remote
**Department:** Engineering
## Description
### Why This Role Exists
We operate a multi-tenant automotive SaaS platform serving thousands of dealer groups across the United States, running on a native AWS backend: Lambda, EventBridge, DynamoDB, S3, Step Functions.
That platform doesn't operate alone. It sits between dealer groups and the systems they already run: DMS platforms (CDK, Reynolds & Reynolds, Tekion, DealerTrack, Procede), CRMs, digital retail tools, F&I providers, and lenders. Over 40 partner platforms feed or consume our data today, and every one of them has its own auth model, its own schema, its own idea of what a "deal" is, and its own opinion about how much traffic you're allowed to send.
That integration surface is the product. If a dealer's data doesn't land clean and on time, nothing downstream works: not the desking tool, not the reporting, not the AI. This role owns that surface end to end. You are the engineer who reads the partner's spec, gets on the call with their team when the spec is wrong, builds the ingestion in Python on AWS, and keeps it healthy in production.
The engineering is only half of it. The other half is the partner's integration team: reading between the lines of their documentation, getting a straight answer about undocumented behavior, and pushing back on a bad contract before it becomes our problem. We want an engineer who does that work well and understands what dealer workflow the data serves, not one who moves JSON from A to B and calls it done.
### Scope & Scale
- Over 40 integrated partner platforms across DMS, CRM, Digital Retail, F&I, and lending, each with distinct auth, rate limits, and data models.
- 5,000+ dealer tenants, each with isolated data and per-tenant partner configuration.
- Tens of thousands of API requests daily across REST, SOAP, webhook, and file-based integration surfaces.
- Partner outages, silent schema changes, and rate-limit shifts are routine, not exceptional. The integrations you own have to survive them without a human in the loop.
### What You'll Own
- **End-to-end partner integrations.** From spec review and sandbox access through production cutover. You write the Python, define the mapping, and own the result.
- **The partner-facing technical relationship.** You're the engineer on the call with their integration team: clarifying undocumented behavior, negotiating payload changes, driving certification, and escalating when their sandbox is down.
- **Ingestion and normalization pipelines.** Webhook receivers, polling clients, and file-based feeds landing into S3 and promoting through the medallion layers into the normalized model.
- **Resilience under someone else's SLA.** Idempotency and deduplication, exponential backoff, rate-limit handling, replay of missed events, and graceful degradation when a partner goes dark.
- **Integration security.** Webhook signature verification, OAuth2/JWT credential lifecycles, KMS encryption, and credential storage in SSM/Secrets Manager. No secrets in code, ever.
- **Contract testing and validation.** JSON Schema validation at the boundary, contract tests against partner sandboxes, and CI gates that catch a partner's breaking change before a dealer does.
- **Observability and integration health.** CloudWatch dashboards, alarms, and structured logging per partner, so a 2 AM failure is diagnosable without guessing.
- **Documentation that survives you.** Mapping specs, runbooks, and onboarding guides per partner. The next engineer should not have to re-derive what you learned on a call.
### First 90 Days / First Year
**First 90 Days:** Ramp on the partner catalog, the normalized data model, and the dealer workflows the data feeds, so you know what the fields are for. Ship your first partner-facing change to production in the first few weeks. By day 90, own one full partner integration end to end: client, mapping, validation, tests, dashboards, runbook.
**First Year:** Running independently across a portfolio of partners, and the primary technical contact for several of them. New partner onboarding is measurably faster and less bespoke because of the patterns and tooling you built.
### Hands-On Expectations
This is a building role, and the balance shifts with the calendar. Between onboardings you're heads-down in code: clients, transformations, tests, instrumentation. During an active partner onboarding, expect several calls a week with their engineering team and real time spent in their documentation. Both modes are the job.
### Tech & Tools
- **Integration core:** Python (AWS Lambda Powertools), API Gateway, EventBridge, Step Functions, SQS; REST, SOAP/XML, webhook, and SFTP surfaces.
- **Cloud services (native AWS stack):** Lambda, S3, DynamoDB, EventBridge, Step Functions, ECS Fargate, Aurora, API Gateway, CloudWatch, Secrets Manager, KMS, CDK.
- **Languages:** Modern Python.
- **Data platform:** S3 data lake with medallion layering (landing, bronze, silver, gold), DynamoDB single-table design, MySQL/Aurora.
- **Infrastructure and security:** CDK, IAM, Auth0, OpenTelemetry, CircleCI.
### How You'll Use AI
This is not a "we are AI-curious" company. We use Claude every day, and we expect you to as well. Concrete examples for this role:
- Turning vendor API docs, WSDLs, and sample payloads into typed Python client skeletons and mapping code.
- Using Claude Code to scaffold Lambda handlers, JSON Schemas, and unit tests from a partner spec.
- Diffing a partner's new spec version against the old one to find the breaking change fast.
- Drafting integration runbooks and mapping documentation from the code you just wrote.
- Reasoning over production logs to isolate whether a failure is ours or theirs.
**You will not be replaced by AI. You will be the engineer who onboards partners at a pace the rest of the industry can't match.**
### Role Specifics
- **Department:** Engineering (Data Platform Engineering)
- **Reports To:** Head of Data Platform
- **Location:** Remote (US). Denver HQ nice to have.
- **Employment Type:** Full-Time
## Requirements
### Must Have
- 10+ years of software engineering experience with strong, current Python.
- Judgment about scope: you start from what the integration is worth to the dealer, not from the most interesting way to build it, and you've shipped the boring version when the boring version was right.
- Hands-on production experience integrating third-party APIs you don't control, including at least one integration you owned through spec, build, certification, and production support.
- **Comfort across integration styles, not just modern REST: SOAP/XML, webhooks, and file-based feeds are all in scope here.**
- **Hands-on AWS experience (Lambda, S3, EventBridge, DynamoDB, Step Functions, Secrets Manager/SSM).**
- **Real experience mapping and normalizing inconsistent external schemas into a canonical model, and the judgment to know when the partner's data is simply wrong.**
- **Ability to debug distributed, event-driven systems from logs and traces and be able to put observability in place.**
- Willingness to be the person on the partner call. Direct, clear, and unbothered by pushing back on someone else's engineering team.
### Strongly Preferred
- Idempotency and deduplication patterns for at-least-once delivery (e.g., DynamoDB-backed dedup).
- Webhook security: HMAC signature verification, mTLS, replay protection.
- OAuth2 / JWT credential flows and rotation for machine-to-machine integrations.
- JSON Schema or comparable contract validation at system boundaries.
- Infrastructure as code (CDK) and CI/CD (CircleCI).
### Nice to Have
- Automotive retail, DMS/CRM, fintech, or multi-tenant marketplace platform experience.
- Experience standing up a partner integration program from scratch (templates, scorecards, onboarding runbooks).
## Benefits
We pride ourselves on cultivating a fun, casual, and collaborative workplace culture where your hard work is recognized, your contributions drive real results, and your impact is felt every day. At A2Z Sync, we're deeply committed to our employees' well-being, starting with comprehensive benefits designed to help you care for yourself and your family.
**Here's what we offer:**
- **Base Salary:** $160,000 – $180,000, depending on experience and qualifications, plus an equity grant.
- **Employer-Paid Health, Dental, and Vision Insurance:** Comprehensive coverage for you and your family starting on day one.
- **Flexible Work:** Remote (US). Denver HQ nice to have.
- **401(k) Retirement Plan with Company Match:** Build your future with our competitive matching program.
- **Generous Paid Time Off (PTO):** Unlimited PTO and 10 paid holidays.
- **Short-Term and Long-Term Disability Coverage:** Fully employer-paid.
- **Life and AD&D Insurance:** Employer-paid coverage for peace of mind.
- **Free Mental Health Support:** Access to confidential therapy sessions through BetterHelp.
- **Pet Insurance Options:** Affordable plans for your furry family members.
- **Identity Theft Protection:** Voluntary services to safeguard your personal information.
- **Other Cool Stuff:** On-site gym in Denver, great co-workers, and a stocked kitchen with snacks and beverages to keep you fueled.
## Apply
[Apply at A2Z Sync](https://apply.workable.com/a2z-sync/j/74BC877E3A/apply)
---
Powered by [Workable](https://www.workable.com)