Automation Engineer

We’re looking for an Automation Engineer who diagnoses before they build. You’ll take a mapped process (from our Redprint) and turn it into a live, resilient automated system — then keep tightening it as the client’s business evolves. This spans agentic workflow orchestration, RAG over operational data, RPA for systems with no API, and the operator-facing dashboards that make it all visible. This is not a “connect the APIs and ship it” role. We care more about why an automation is built a certain way — and whether it holds up under real-world failure — than how fast it went out the door. What You’ll Do • Take a mapped process and design the automated system behind it — identifying where a person is currently acting as “the API” between two systems • Build multi-step, agentic workflows in n8n with conditional branching, retries, human-in-the-loop checkpoints, and full audit trails • Build RAG pipelines over operational data (CRM records, email threads, call transcripts, internal docs) with source-cited, auditable retrieval • Build resilient browser automations (RPA) for legacy systems with no API — vendor portals, county systems, etc. — designed to survive UI changes • Build operator-facing dashboards so teams can see what’s automated, what’s pending, and where human judgment is still needed • Design for failure from day one: retries, dead-letter handling, alerting, reconciliation, explicit failure routing, human-override paths • Phase rollouts deliberately — ship one workflow at a time, stabilize, then expand, without breaking the client’s operation How to Apply Send us samples or a portfolio of your work — specifically the most complicated automation you’ve built. Walk us through what it replaced, where it was hardest to get right, and what happens when it fails. We’re more interested in your thinking than a list of tools.