Sr. Software Engineer, Fullstack or Backend (Workflow Zone)

About Zapier

We're humans who simply think computers should do more work. At Zapier, we’re not just making software—we’re building a platform to help millions of businesses globally scale with automation and AI. Our mission is to make automation work for everyone by delivering products that delight our customers. You’ll collaborate with brilliant people, use the latest tools, and leverage the flexibility of remote work. Your work will directly fuel our customers’ success, and as they grow, so will you.

Job Details

• Salary: $170.8K - $224.1K
• Location Type: Remote
• Employment Type: FullTime
• Job Posted: 8/19/25
• Location: Americas

About the Workflow Zone

Zapier’s Workflow Zone is responsible for the core engine that powers our automation platform. As more teams and organizations depend on Zapier to automate critical workflows, we’re investing in scaling the capabilities, reliability, and intelligence of our core product experience. We’re hiring Sr. Backend Engineers and Sr. Fullstack Engineers (backend-leaning) to join several high-impact teams in the Workflow Zone. If you’re passionate about building robust systems, enabling advanced user workflows, and shaping the future of automation, we’d love to hear from you.

The Workflow Zone is where Zapier’s automation magic happens. This zone owns the product experience and execution engine behind creating, running, and debugging workflows (Zaps). We’re focused on building powerful, flexible tools that help individuals and teams automate their work with speed and confidence.

As automation use cases grow more complex—especially for Enterprise users—we’re evolving the platform to support more sophisticated logic, scalable execution, and AI-native experiences. This means:

• Building intuitive and resilient workflow authoring experiences
• Expanding execution capabilities and logic primitives
• Introducing AI-powered tools for creation and troubleshooting
• Improving reliability, observability, and control across the system

We’re currently hiring for several teams across the zone, including:

• Editor Creation
• Troubleshooting
• Runner
• Workflow Capabilities

Editor Creation Team

The Editor Creation team is reinventing how users build automations—laying the groundwork for a faster, smarter, and more intuitive workflow authoring experience. Rather than iterating on legacy patterns, this team is redesigning the editor's foundations to support new paradigms like AI-assisted creation and more advanced configuration options.

In this role, you’ll:

• Redesign and modernize the Zap creation experience with performance, clarity, and scale in mind
• Build flexible UI components and configuration flows that support both no-code and AI-assisted automation
• Contribute to foundational infrastructure that enables new editor paradigms and future UX modularity
• Collaborate across Product and Design to streamline the journey from idea to working automation

Troubleshooting Team

The Troubleshooting team ensures automations run smoothly—and when they don’t, users have the tools to understand why. This team is focused on preventing, detecting, and resolving workflow errors with clarity and speed.

In this role, you’ll:

• Build systems that proactively detect, surface, and explain errors in user workflows
• Design clear, actionable debugging experiences to help users fix issues faster
• Collaborate with Support to turn customer pain points into product improvements
• Strengthen the zone’s culture of reliability, observability, and resilience

If you enjoy solving messy problems, closing feedback loops, and turning complexity into clarity for users, this is a team where you’ll thrive.

Runner Team

The Runner team is responsible for reliably executing Zaps—fast. We’re focused on the core infrastructure that powers Zapier’s workflows, including scaling for high volume and reducing latency across millions of executions daily.

In this role, you’ll:

• Develop and maintain Zapier’s execution engine, scaling it to handle millions of daily runs
• Improve system performance, reduce latency, and strengthen failure handling
• Design and implement execution primitives that power