Internal AI Job Board

Senior AI Automation Engineer

BetterUp - Multiple cities

This role is part of the Internal AI Job Board, a curated list of jobs for teams building or operating internal AI systems. Follow the original role page for the employer description, requirements, and application flow.

Compensation: salary range for this role is as follows: $165,000 – $230,000 Hybrid Work Policy & Hub Locations BetterUp is a hybrid company that values in-

Responsibilities

• This is applied agent engineering: tool-using AI systems built on real business data, embedded in the workflows people live in every day, trusted enough to be part of how the work actually gets done. This is foundational work. It shapes how BetterUp wins in the AI era, and how many more people grow through what we build.
• You'll embed with HR, Sales, Customer Success, Coach Operations, Legal, and Finance to do three things:
• Understand how people actually work, with sufficient detail to build the right solutions
• Apply AI to fit the workflow as it is, not as a redesign would have it
• Reimagine what comes next, once you've earned the team's trust

Qualifications

• You experiment with new models, agent frameworks, and orchestration patterns on your own time because you can't help it. Claude, the Anthropic SDK, and MCP are already in your toolkit. You've replaced parts of your own work or life with agents you built yourself, you read model release notes the day they drop, you pay for the tools out of pocket, and you have a strong opinion about why one agent framework beats another for a given problem.
• You publish your work where you can: open-source, write-ups, demos, or conference talks.
• 7+ years of engineering experience, with a track record of shipping real systems at scale
• The ability to sit with a non-technical operator, understand their actual workflow rather than what they think the solution is, and translate it into a working agent or automation
• A founder's bias for action and a senior engineer's obsession with quality
• Full-lifecycle ownership, from the first discovery call to the tenth production bug
• Comfort when the problem isn't fully scoped, and a preference for finding the right work over waiting for it

Apply on the original posting