Home › Jobs › A2Z Sync

Software Technical Lead

A2Z Sync · Denver, Colorado · Posted November 19, 2026 (1 days ago)

Apply on A2Z Sync’s siteFill the application with AutoFillSee your fit for this role

Job description

Why This Role Exists 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. Scope & Scale Multiple product or platform areas, each with a team of roughly 3–5 engineers across onshore and offshore. Both the legacy scope still in production and the new services being built or extracted from the monolith. A multi-tenant platform serving thousands of dealer tenants, with per-tenant configuration and feature flags as the rollout primitive. Integration surfaces across REST, SOAP, webhook, and event-driven patterns with third-party dealer systems. AI agents from the AI platform team that touch your domain and depend on your tool contracts. What You'll 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 and 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. 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. First 90 Days / First Year First 90 Days: Learn the platform, the monolith, and the extraction plan. Take ownership of your areas and their on-call. Run design reviews and set the review bar with your team. Ship a meaningful change to production in your primary stack, and publish the design doc for the next domain extraction in your area. First Year: At least one non-trivial domain extracted from the monolith in your area, through dual-write, traffic-splitting, and clean cutover, with no customer-visible incident. Micro-frontend modules in your area shipping independently with performance budgets met. Tool contracts for every AI agent touching your domain in place with eval fixtures and guardrails. Your onshore and offshore engineers working in one delivery cadence, with velocity and quality measurably up. Hands-On Expectations This is a senior IC role, not a management role. Expect the majority of your time in code, design docs, and reviews: shipping production code in your primary stack, reviewing PRs across the others, running design reviews, and owning cutovers. The remainder is cross-team contracts, on-call and incident ownership, and mentoring your engineers. Tech & Tools Languages and frameworks: 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. AI and agents: Strands Agents SDK on AWS Bedrock AgentCore, MCP servers, Bedrock Guardrails, Anthropic models. Infrastructure and delivery: AWS CDK, CloudFormation, CircleCI, OpenTelemetry, Auth0. 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: Run your team on the agentic development harness: agent-assisted coding, review, and testing as the default way your engineers ship, with the velocity gain measured. Own the tool contracts that production AI agents call into your domain: schema, SLA, idempotency, eval fixtures, and guardrails. Draft design docs, extraction plans, and ADRs with Claude as your first-draft partner, then make them precise enough to implement from. Use AI to review PRs across the stacks you are not primary in, so your review bar holds across Python, Java, PHP, and TypeScript. Generate load baselines, dashboards, and runbooks for every cutover faster than you could by hand. You will not be replaced by AI. You will be the Tech Lead whose small team ships what used to take a department. Role Specifics Department: Engineering Reports To: SVP, Engineering Location: Denver, CO, hybrid (2 days/week in office) or Remote (US, outside the Denver market) Employment Type: Full-Time

Posting dc9DXGoe1ReH9VLVE6nKLz on workable. Source: the employer’s listing. Valid through January 3, 2027 unless closed earlier.