AI Operations Manager

Moburst is a full-service mobile-first digital marketing agency that helps companies exceed their growth goals. Leading global brands and startups (including Google Samsung and Uber) leverage our mobile and digital expertise to grow their products strengthen their market presence and maximize performance KPIs.

Were hiring someone to own the operational side of our AI teams output: keeping whats already built running and building the smaller well-defined automations that dont need a full system design pass. Where our AI builders design and ship new end-to-end systems from open client use cases this role keeps the existing estate healthy and builds from a spec thats already written.

This is a hands-on detail-first role. Youll be the person who notices an automation is about to break before anyone else does and who can turn a well-scoped request into a working build without needing it handed to you twice.

Monitor and maintain automations the AI team has already shipped: catch breakages keep credentials and integrations current and fix issues before anyone else notices them.

• Build new automations from an already-defined spec (n8n Make Zapier or equivalent) for tasks that are scoped as distinct from open-ended use case design.

• Maintain a live inventory of whats running what it depends on and who owns it so renewal dates and credential locations dont rely on any one persons memory.

• Triage day-to-day fix or small-build requests from the team escalating anything that needs full system design.

• Document every automation you touch well enough that someone else on the team could pick it up without a handoff call.

• Test like a QA engineer: before anything ships push it through edge cases (malformed or empty inputs expired tokens rate limits API changes unexpected volume) and fix what breaks before it breaks for a user.

• Be our user: use every build the way the account managers strategists and clients who depend on it would and flag anything confusing slow or fragile from their side of the screen.

• Hands-on experience building and maintaining automations in at least one low-code platform (n8n Make Zapier or equivalent); n8n experience preferred.

• Comfortable owning the less visible parts of a system: monitoring error handling documentation credential hygiene.

• A QA mindset: you instinctively ask what happens if hunt for edge cases and would rather find the failure yourself than hear about it from a user.

• User empathy: you can think like our ICP (Ideal Customer Profile) and judge a build by whether it works for the person relying on it in their real workflow.

• Enough scripting ability (Python or JavaScript) to extend an automation when a platforms native nodes run out.

• Organized enough to maintain a registry or inventory as standard practice not only when asked.

• Prior ops support engineering or QA background where the job was keeping something running rather than designing it new.

• Basic familiarity with Claude tooling (API Claude Code).