Software Engineer, Enterprise Zone (Backend & Full Stack) — Multiple Levels

• Lead responses to critical incidents and customer-impacting events • Work directly with enterprise customers • Collaborate across engineering, product, and support to solve urgent problems • Build internal tools and improve core product features based on real-world, customer feedback • Build a new extensible platform for account and organization-level settings, applying declarative controls, VPC connections to on-prem data, and instrumenting account-wide AI guardrail controls • The Asset Management team is responsible for building and scaling the systems that make every Zapier asset, across products and workspaces, discoverable, governable, and portable. You will be responsible for architecting and deepening enterprise-grade Platform APIs to manage assets across multiple products, ensuring consistency, reliability, and performance at scale for all of our customers. • The Asset Management team • Design and implement scalable backend architecture and APIs for asset cataloguing, ownership, and security • Build intuitive, unified interfaces for organizing, transferring, and governing assets across accounts and products • Embed AI technology into core product experiences to proactively monitor and suggest optimizations to account management • Drive technical alignment with senior leaders and stakeholders across the organization • Deliver fast-paced solutions and POCs, prioritizing impact over deep polish, while balancing short-term execution with long-term technical vision • Tackle challenges in data standards, compliance automation, and cross-product integrations • This team is central to Zapier's multi-product strategy, unlocking faster product onboarding, reducing manual support burden, and delivering key enterprise capabilities. • The Enterprise Insights team builds and maintains the core systems that support our customers. We're not following an existing playbook, we're writing it. Here, you will help build a strong account oversight platform that connects and supports Zapier's products. • The Enterprise Insights team • You'll work on: • Building scalable platforms like User Notifications, Unified Smart Inboxes, Audit Logs, Public APIs to give customers better visibility, control, and access across Zapier. • Supporting key use cases such as compliance, error tracking, and transactional alerts through reliable communication systems. • Creating and improving observability features like SLOs, alerts, and dashboards to help Zapier grow. • Strengthening core systems as we expand to serve larger and more complex customers. • Leading important projects from start to finish — using AI to speed up development and improve the customer experience, while working closely with your team. • All of these roles are instrumental in ensuring Zapier can deliver on their upmarket strategy and mission. They have a direct impact in driving higher company ARR. These are high impact, high reward roles that will include far reaching features, new challenges, and close connection to customers each day. • Our Commitment to Applicants • Culture and Values at Zapier • Zapier Guide to Remote Work • Zapier Code of Conduct • Diversity and Inclusivity at Zapier • High Visibility, High Impact • If you're someone who thrives on ambitious goals and meaningful work, this is the team for you: • Work on high-impact features that directly influence premium plan sales and help close strategic enterprise deals. • Collaborate cross-functionally with Product, Design, Revenue, Support, and GTM teams. • Work in a high-visibility area with strong leadership support and a clear growth path for engineers. • Play a key role in Zapier's growth trajectory—you're not a cog in a machine, you're part of the engine. • Openings • Openings • We're hiring multiple openings across two levels — Engineer (L3) and Senior Engineer (L4) — across these teams. We run a shared pipeline and map candidates to the right level based on what we observe throughout the process. You don't need to decide upfront. • The difference between levels comes down to scope: • L3 engineers own outcomes end-to-end within their team — they break down complex problems, ship iteratively, and drive strong technical execution in their domain. • L4 engineers do all of that and extend it beyond their team — they coordinate across ownership boundaries, shape technical direction for adjacent systems, and bring other engineers along with them. • Our level definitions may look different from what you've seen elsewhere, so we map based on what we observe in the process, not your current title. We'll be transparent about leveling before you reach the final stages. • These qualities apply across both levels — scope and context will vary based on where you land. We know great engineers come from a range of backgrounds and career paths. You'll be successful in these roles if: • You're a proven SaaS engineering builder. You have deep experience designing, developing, and maintaining complex mission-critical systems, whether that's measured in years or in the breadth and impact of what you've shipped. You're comfortable writing backend services (Python or Node.js ideal), and you're not afraid to go deep into API design, database modeling, or CI/CD pipelines. • You're a proven SaaS engineering builder. • You work through AI agents, not alongside them. Your daily development workflow is built around directing and reviewing agent-written code, not writing it by hand. You have opinions about which models to use for which tasks, you've hit real failure modes and built mitigations, and your workflow is actively evolving. Bonus: you use multi-agent patterns, enable others on your team to build faster with AI, or have scaled AI impact beyond yourself. • You work through AI agents, not alongside them. • You know event-driven systems and have strong platform thinking. You've built scalable tools that help other teams move faster and simpler. You're familiar with systems like Kafka, SQS, and Fastify, and you've worked with observability tools like Datadog, Grafana, and Graylog. • You know event-driven systems and have strong platform thinking. • You work close to the customer. You don't wait for product specs or UX research to tell you what to build. You pull customer tickets, talk to CSMs, review feedback, and use that context to drive what you ship. You think in milestone slices: what's the smallest thing I can get into production that moves us forward and teaches us something? • You work close to the customer. • You ship through ambiguity. When there's no spec, no designs, and no clear path forward, your first instinct is to gather customer evidence, break the problem into a narrow first slice, and get rough working software into production within days, not weeks. You use working prototypes to drive alignment with stakeholders rather than waiting for consensus before building. You're comfortable throwing work away when direction changes and you treat discarded work as a fast learning loop, not a loss. • You ship through ambiguity. • You own your work and yourself. You take initiative without waiting for permission and you ship fast and share early. But you also own your mistakes, your gaps, and your role in friction, openly. You say "I don't know" and "I was wrong" out loud, early, and without shame. You hold yourself to a high standard and can articulate where you've fallen short, not just where you've succeeded. • You own your work and yourself. • You communicate proactively in an async-first culture. You manage up and across, flagging risks, surfacing decisions, and keeping stakeholders informed without being asked. You use written artifacts, working demos, and rough prototypes as your primary communication tools, not meetings. • You communicate proactively in an async-first culture. • You believe enterprise can move fast. You've seen (or are excited to prove) that shipping to enterprise customers doesn't have to mean slow, waterfall-style cycles. You know how to balance compliance, security, and rollout considerations with tight iteration loops and rapid customer feedback. You see enterprise constraints as interesting design problems, not reasons to slow down. • You believe enterprise can move fast.