You are the day-to-day engine of delivery, working directly with our Head of AI Solutions and with a direct line to the founder. No middle layers. What you own: • The client request queue across active accounts — triage, fix, ship, verify, against a response SLA. The lane we most need covered, and the one we most want to shrink. • Full-stack feature work on live client apps — Next.js and React on the front, Node and Supabase behind it. Real users, real data, shipped weekly. • The LLM surface — agent loops with tool calling, structured output that has to be reliable, and model swaps measured against quality rather than guessed at. • The verification layer — the code that checks the model's output before a client ever sees it. Deterministic, boring, and the most important thing we ship. • The interface — you'll get a hand-drawn wireframe and a few references, not a Figma file. Mid-level UI craft is enough; the bar is that a client can use what you build without a training call. • Deploys and the boxes they run on, plus automating your own lane: triage flows, runbooks, self-serve fixes. We want the queue to shrink, not to be lived in. • Internal systems — our own operations platform (client events, portals, payouts, call intelligence) alongside client work. How we work: • Async by default: short Looms, clear written updates, one weekly sync. • Nothing is "done" until it's verified. You count what you expect. • We set goals together each week and track the goals, not hours. • Tooling provided — Claude Code and the AI stack we use daily. What we expect from you: someone obsessed with automation who reports before anyone asks. Not someone waiting for instructions.

AI Automation Engineer

Emma

Responsibilities

Skills wanted:

Language(s) required:

Ruben Davoli

Ruben Davoli

About Beavermind:

mission:

beavermind.ai/

Admin access needed