Backend Engineer

Role overview This is a backend engineering seat focused on owning the service layer, the data model, and the contracts other systems depend on. Languages are chosen per workload rather than per resume, with TypeScript carrying most of the API and integration surface, Python running the data and agent work, and Go handling paths that must stay fast under sustained load. Many engagements touch all three.

Responsibilities - Build and own production services in TypeScript, Python, and Go, choosing between them based on workload characteristics - Design REST, GraphQL, or gRPC API contracts that stay stable as consumers multiply, and version them properly when they cannot - Model data in Postgres with attention to indexes, query plans, and migrations that run safely against live tables - Build the integration layer between commerce platforms, ERPs, and internal services, where idempotency and retries are most of the work - Design event-driven flows on queues and message buses, including dead letter handling and replay that has been exercised - Write reconciliation logic that keeps two systems of record in agreement, and the alerting that fires when they stop - Instrument services with structured logging, metrics, and tracing before they reach production, and deploy to Cloud Run, Fargate, or Kubernetes

Requirements - Five or more years building backend services in production, with real depth in at least two of TypeScript, Python, and Go - Strong relational data modeling and SQL, including the ability to read a query plan and act on it - Experience with asynchronous and concurrent work, including queues, background jobs, and their failure modes - A track record of integrating poorly documented or unreliable third-party APIs and making the result dependable - Comfort deploying and operating your own services on AWS or GCP

Nice to have - Experience with agentic AI systems or LLM-backed services in production - Commerce or ERP integration background, including Shopify, Salesforce Commerce Cloud, NetSuite, or QuickBooks - Infrastructure as code with Terraform, and ownership of a deployment pipeline end to end