As a learning designer at Zapier, I used to spend my days helping my teammates learn: I built and led trainings, created enablement resources, and helped folks better understand how their work contributed to company strategy. Now, I sit inside our HR team as an AI automation engineer. But the through line is the same: I still help my teammates (and now customers, too!) do their best work.
AI automation engineer sounds like a vague title, so here’s the job, plainly: I embed with a team (HR, in my case), spot opportunities to enhance the team’s work, and build AI-powered workflows that jump on those opportunities. The goal is to create measurable improvements that free my teammates up for creativity, strategy, and connection.
I think we’ll be seeing this title pop up more and more as time goes on. For example, instead of hiring a new content writer, content marketing teams might look for AI automation engineers with a strong eye for content. Instead of a new junior coder, engineering teams might look for an AI automation engineer with a technical background.
Lots of teams see AI’s potential but get stuck turning ideas into action. The gap is less about technology and more about translation: understanding how a real process works today, where it fails, what data is safe to use, and what “better” even looks like.
AI automation engineers close that gap. We prototype fast using tools like Zapier, ChatGPT, Airtable, and Cursor, then we harden those prototypes into reliable internal tools.
In HR, that looks like:
And it is not just about helping my own team. A big part of my role is building repeatable HR workflows that we can share with our customers. When I design something for Zapier’s people team, like an interview debrief summarizer or a self-serve policy bot, I’m also thinking about how it could work for other HR teams out in the world. Sometimes it even goes the other way: a customer use case inspires a workflow that we bring back inside Zapier.
AI automation engineer is a new type of role, and I’m even newer to it myself, but here’s a glimpse into how I spend my days.
I don’t come from a technical background, but I’m a tinkerer, and I think that’s what makes me suited for this role. I’m comfortable building with no-code tools and love to ship solutions.
Skills I’ve picked up along the way are prompt engineering, responsible AI practices, and understanding how to pick the right AI tools for the job.
One of the most important parts of the role, though, is something I have a lot of experience with: enablement. I need to make sure the folks I’m building for understand how to make the most of these systems.
One important thing to note: My focus is squarely on HR. That’s where I build, prototype, and enable. While I love seeing how AI automation engineers show up in marketing, IT, or engineering, my role is all about HR use cases. I help our people team work smarter, and I help our customers run stronger HR operations. But I’m also proof that you don’t need to be a software engineer to become an AI automation engineer. Here are some other folks from the Zapier community who I’d argue are AI automation engineers, each from a different background.
Moving from learning & development into this role as an AI automation engineer for HR hasn’t changed my mission. I still help people work better. If you’re AI-curious, start with the smallest annoying task you do every week. Fix that. Measure it. Then fix the next one.
By Emily Mabie