Systems and Automation Engineer
Own the schedulers, pipelines, and glue that keep client platforms and our own operations running without a human pressing the button.
- TypeScript
- Python
- GitHub Actions
- Cloud Run
- Lambda
- Postgres
Every engagement accumulates automation: nightly syncs, content pipelines, deploy jobs, reconciliation runs, alert routing, and the scripts that stitch vendors together. Most of it is written once under deadline and then quietly rots. This role owns that layer properly, for clients and for our own internal systems.
You will replace cron and copy pasted shell with workflows that have retries, idempotency, observability, and a clear owner. Where an LLM makes a step better, you use one. Where a deterministic script is the right tool, you do not dress it up as an agent.
Build the automation layer
- Design and run scheduled and event driven workflows on GitHub Actions, Cloud Run jobs, Lambda, and workflow engines such as Temporal or Inngest, with retries and idempotency designed in from the start
- Write the integration scripts between commerce platforms, CMSs, data warehouses, and messaging tools, in TypeScript or Python, with typed contracts at every boundary
- Add LLM steps where they earn their place: classification, extraction, summarization, and content generation with schema validation and human review gates
Make it observable and safe
- Instrument every job with structured logs, run history, and alerts that name the failing step and the likely fix
- Build the guardrails that stop a bad run from compounding: dry run modes, staged writes, rate limits, and kill switches
- Own secrets, credential rotation, and least privilege service accounts for everything that runs unattended
Keep it maintainable
- Consolidate the one off scripts that pile up on every engagement into shared, documented tooling
- Write the runbooks so any engineer can rerun, backfill, or pause a pipeline without reading the source
- Audit what runs where, retire what nobody needs, and keep the cost of the automation layer honest
Required
- Four or more years in systems, platform, DevOps, or backend engineering with real ownership of production automation
- Strong scripting in TypeScript or Python, enough shell to be dangerous, and the judgment to know when a script has become a service
- Hands on with GitHub Actions and at least one cloud job runtime: Cloud Run, Lambda, ECS, or Kubernetes CronJobs
- You have debugged a pipeline at 2am from logs alone and then fixed the logging so nobody has to again
- Comfort with Postgres, queues, and the failure modes of third party APIs
Helpful, not required
- Experience with LLM APIs in batch or pipeline contexts, including cost control and output validation
- Workflow engine experience: Temporal, Inngest, Airflow, or Prefect
- Commerce or content operations exposure: Shopify, Sanity, or another headless CMS
Also hiring.
Engineering Lead and Client Partner
Remote Delivery
A player coach seat that combines technical lead, delivery owner, and second seat on sales.
Forward Deployed Engineer, Agentic Commerce
Remote Applied AI
Embed with commerce clients and ship agent driven discovery, catalog, and checkout systems into production on their stack, not ours.
Forward Deployed Engineer, Enterprise AI Integrations
Remote Applied AI
Wire LLM agents into the ERPs, CRMs, and ticketing systems enterprises already run, inside the client environment, and make the integrations survive production.
Show us something you built.
Send a resume or profile with a short note about work you have shipped. Links to code, systems, or launched projects tell us more than a cover letter ever will.
careers@contracollective.com