We run a multi-tenant automotive SaaS platform used every day by dealership staff and consumers across the United States. We're now in the middle of a significant platform evolution: breaking the legacy monolith into domain-owned microservices, standing up a modern event-driven backbone on AWS, and building production AI agents that take real action inside dealer workflows.
That work runs on Tech Leads. A Tech Lead at A2Z Sync is the engineering anchor of a product or platform area: the most senior IC on the team, the person who turns architecture decisions into shipped product, runs design reviews, holds the bar on what gets merged, and owns the outcome when services hit production at 2 AM. You are not a manager. You are the technical leader of a small team of engineers (a mix of US-based and offshore), and the patterns you set become the patterns the team inherits.
What you will own:
Your areas, end to end: multiple product or platform areas with a team of roughly 3-5 engineers per product across onshore and offshore, covering both the legacy scope still in production and the new services being built or extracted.
Service design and delivery: from design doc through dual-write rollout, traffic-splitting, per-tenant feature flags, and clean cutover. You decide where the monolith seams are: which domain comes out next, what its service boundary is, and how the data comes with it.
Full-stack application delivery: vertical slices, not layers. Micro-frontend delivery (independently deployable React/Next.js modules, API/BFF contracts, shared design system), microservices (domain-owned, event-driven over EventBridge, independent pipelines), and performance/monitoring (Core Web Vitals, API latency budgets, OpenTelemetry tracing browser to database, CloudWatch dashboards, load baselines before every cutover).
AI agent co-delivery: when the AI platform team builds an agent that touches your domain, you own the tool contract on your side: schema, SLA, idempotency, eval fixtures, and guardrails.
Team velocity: responsible for the velocity, productivity and quality of engineers working across our agentic harness through loop engineering practices.
The patterns the team inherits, cross-team contracts, code and design review cadence, on-call and incident ownership, and mentoring your engineers.
Tech environment: Python, Java (Spring Boot), PHP (Laravel), TypeScript/React (Next.js); AWS (Lambda, EventBridge, DynamoDB, ECS Fargate, Aurora, API Gateway, S3, SQS/SNS, Step Functions, CloudWatch); Strands Agents SDK on AWS Bedrock AgentCore, MCP servers, Bedrock Guardrails, Anthropic models; AWS CDK, CloudFormation, CircleCI, OpenTelemetry, Auth0.
Requirements
Must have:
7+ years of professional software engineering experience, with at least 2 years operating as a tech lead or staff engineer.
Strong proficiency in at least 3 of: Python, Java/Spring Boot, PHP/Laravel, TypeScript/React. You can ship production code in your primary stack and review PRs in the others.
Hands-on production experience with AWS: Lambda, EventBridge, DynamoDB, ECS or Fargate, RDS/Aurora, API Gateway, SQS/SNS, CloudWatch.
A battle-tested understanding of breaking a monolith into microservices: carving domain-driven service boundaries, applying strangler fig and anti-corruption layers, splitting shared databases, and leading at least one non-trivial extraction in production with dual-write validation, traffic-splitting, and canary or per-tenant rollout. You can describe what broke and how you caught it before customers did.
Full-stack delivery experience: you have shipped frontend (React or similar) and backend services in the same product area and owned the performance and monitoring of both.
Experience integrating with third-party APIs at scale: REST, SOAP, webhook patterns, idempotency, retry/backoff, vendor-specific quirks.
Comfort with both relational (MySQL/Aurora) and NoSQL (DynamoDB) data models.
Strong written communication: your design docs are clear enough that another engineer can implement from them without a meeting.
The instinct to build reusable abstractions without over-engineering.
Strongly preferred:
Experience shipping production AI/agentic workflows: code-first agent frameworks (Strands Agents, LangGraph, or equivalent) deployed on AWS Bedrock AgentCore, MCP servers, prompt engineering, eval harnesses, guardrails, cost and latency budgets. Or a clear track record of picking up new platforms fast.
Micro-frontend architecture experience: module federation or equivalent, independently deployable frontend units, shared design systems.
Event-driven architecture experience including event schema versioning and consumer-driven contracts.
Multi-tenant SaaS experience: tenant isolation, per-tenant configuration, feature flags as a rollout primitive.
Experience working with both onshore and offshore engineers in a single delivery cadence.
Nice to have:
Automotive, fintech, or marketplace platform experience.
OpenTelemetry, CircleCI, AWS CDK, Auth0.
Browser automation in production integration flows (e.g., Playwright).
Data pipeline experience: Glue, Athena, S3 data lake patterns.
Benefits
Here's what we offer:
Comprehensive medical, dental, and vision benefits.
Employer provided STD/LTD and life insurance.
Matching 401k plan.
Unlimited paid time off, including 10 paid holidays.
Free mental health support through BetterHelp, pet insurance options, and identity theft protection.
Flexible work: Denver hybrid (2 days/week in office) or fully remote anywhere in the US.
Real ownership of a product area: your patterns, your roadmap, your cutovers, your AI agents shipping to production.
