Zapier - Sr. Engineer, Backend
Upload My Resume
Drop here or click to browse · PDF, DOCX, DOC, RTF, TXT
Requirements
• I sometimes support more junior engineers (or candidates) through pairing, answering questions, or explaining context, even if I’m not the official mentor. • support more junior engineers • I experiment with tools (including AI) that help me work more efficiently, while staying responsible for the quality of the output. • work more efficiently • If most of these feel true most weeks, you’re likely operating at L3.If many feel aspirational or “only when things are perfect,” you’re probably still growing toward L3. • L4 Senior Backend Engineer – Enterprise Integrations • 1. Technical leadership & architecture • I am an expert in my team’s services and at least one major backend technology, and I can handle most unknowns and edge cases myself. • expert in my team’s services • I regularly lead the technical design for features or projects, especially those involving complex integrations, auth models, or cross‑team dependencies. • technical design • I create or evolve integration patterns and best practices (e.g., how we structure integration adapters, rate limiting, retries, observability) and help others adopt them. • integration patterns and best practices • I am fluent in AI-assisted, agentic development: I can break work into agent-friendly tasks, compose the right tools/skills, and use agents to generate, refactor, and migrate code — while I remain accountable for correctness, security, and long-term maintainability. • fluent in AI-assisted, agentic development • 2. Scope, ambiguity & outcomes • I work on problems where the outcome is clear but the path is not, and I break the work down into a plan that the rest of the team can execute. • outcome is clear but the path is not • I take responsibility not just for my own tasks, but for helping the team deliver its commitments, especially on critical enterprise integrations.
Responsibilities
• 3. Problem solving & debugging • When something breaks in an integration (timeouts, auth errors, upstream API changes), I can triage, debug, and fix many issues myself by using logs, traces, and metrics. • triage, debug, and fix • For problems I can’t solve alone, I know which experts or teams to pull in and how to clearly summarize the problem, impact, and options. • which experts or teams to pull in • I contribute to incremental improvements (small refactors, better error messages, test coverage) while working on my regular tasks. • incremental improvements • 4. Customer & enterprise mindset • I understand which integrations are most important for enterprise customers and factor that into how I prioritize bugs and improvements. • integrations are most important for enterprise customers • I’m aware of SLAs, incident processes, and on‑call expectations, and I follow them reliably when working on production issues. • SLAs, incident processes, and on‑call expectations • I’m able to translate customer problems (often reported via Support or Success) into clear technical tickets and solutions. • clear technical tickets • 5. Collaboration & communication • I communicate early and often about my progress, risks, and blockers so my team can plan around me. • early and often • I ask for help when I’m stuck, and I accept feedback on my code and approach without getting defensive. • I can participate in design discussions by asking good questions and giving thoughtful input on proposals others lead. • giving thoughtful input • 6. Growth & impact beyond self • I actively seek feedback from my manager and peers and use it to improve my skills and habits. • team deliver its commitments • When delivery is at risk, I propose options and trade‑offs (scope, sequencing, technical approaches) instead of just flagging the problem. • propose options and trade‑offs • 3. Reliability, operations & incidents • I proactively look for systemic reliability risks in our integrations (e.g., dependency fragility, poor backoff, missing alerts) and drive fixes before they cause incidents. • systemic reliability risks • In incidents, I can quickly evaluate impact, coordinate technical response, and make pragmatic decisions that balance risk and customer needs. • quickly evaluate impact, coordinate technical response • After incidents, I help drive root cause analysis and long‑term improvements, not just the immediate patch. • root cause analysis and long‑term improvements • 4. Enterprise & cross‑functional impact • I understand how our integrations affect major deals and enterprise customers and use that understanding to shape priorities and designs. • affect major deals and enterprise customers • I work closely with Customer Success, Support, and Sales when needed to clarify technical feasibility, risks, and timelines for enterprise‑critical integration work. • Customer Success, Support, and Sales • I influence roadmap and scoping discussions by bringing a strong engineering perspective on complexity, trade‑offs, and long‑term maintainability. • roadmap and scoping discussions • 5. Leading others & multiplying the team • I regularly mentor and unblock other engineers, helping them grow their debugging, design, and ownership skills. • mentor and unblock other engineers • I provide clear, actionable feedback on design docs and PRs, improving not just the code but the author’s thinking. • clear, actionable feedback • I often act as technical lead or feature lead for projects, coordinating work across multiple engineers or teams when needed. • technical lead or feature lead • 6. Strategic thinking & continuous improvement • I spot patterns in bugs, incidents, or customer requests and turn them into roadmap‑level improvements (e.g., common integration libraries, platform capabilities). • roadmap‑level improvements • I advocate for and help implement process or tooling improvements (CI, testing strategies, runbooks, observability) that make the team more effective. • process or tooling improvements • I stay current on emerging technologies and industry patterns relevant to integrations (API standards, auth flows, observability, AI tooling) and bring back practical ideas for the team. • emerging technologies and industry patterns • If most of these are already how you operate today – and your peers and manager would independently agree – you’re likely performing at or near L4.If you only do these occasionally or when asked, you’re probably still solidly at L3, growing toward L4. • Application Deadline: • The anticipated application window is 30 days from the date job is posted, unless the number of applicants requires it to close sooner or later, or if the position is filled. • Even though we’re an all-remote company, we still need to be thoughtful about where we have Zapiens working. Check out this resource for a list of countries where we currently cannot have Zapiens permanently working.
Benefits
• IndiaIC 3 - Base Salary ₹52,97,600 – ₹79,46,400 • IndiaIC 4 - Base Salary ₹64,10,100 – ₹96,15,100 • We believe all Zapiens should be rewarded competitively and equitably, using practices that are simple and transparent. This philosophy ensures we’re able to find, grow, and retain exceptional people from a broad range of backgrounds. Here’s how we define our compensation principles: • Competitive: Zapier pays well among the technology sector. • Equitable: Consistent pay practices; Pay for impact • Simple: Pay is well understood, and pay practices are built for scale. • Transparent: Zapiens know how pay works, including how their pay is determined. • A Candidate's compensation package is finalized once the interview process is concluded and accounts for demonstrated experience, job knowledge, skills, abilities, and internal equity. We use a business impact approach to base pay, which means we set pay for all Zapiens based on their demonstrated impact on Zapier’s success. In alignment with that philosophy, the upper half of a pay range is typically reserved for individuals who have consistently demonstrated a high impact in their current role and level while at Zapier.For more information on Zapier’s Total Rewards please click here. • Upload your resume here to autofill key application fields. • Drop your resume here! • Parsing your resume. Autofilling key fields... • Please Note: We cannot accept more than one application per candidate per job. If you have applied to this job already, you will be unable to apply again for 90 days. • Please enter your legal first name as it appears on your government-issued ID. This is only used for official documentation and onboarding if hired. Otherwise, we’ll refer to you by your preferred name. • Please enter your legal last name as it appears on your government-issued ID. This is only used for official documentation and onboarding if hired. Otherwise, we’ll refer to you by your preferred name. • Please only enter your preferred first name • preferred first name • or drag and drop here • Due to regulatory and security reasons, there’s a small number of countries where we cannot have Zapier teammates based. Additionally, because Zapier is an all-remote company and people can join our workforce from almost any country, we do not sponsor visas or transfers. Zapier teammates need to be authorized to work from their home location. • we do not sponsor visas or transfers • I am authorized to work in the country due to my nationality. • I am authorized to work in the country based on a valid work permit. I do not need a company to sponsor my visa. • I am authorized to work in the country based on a valid work permit. I will need to be sponsored by the company I work for. • I am not authorized to work in the country and will need visa support. • Online Job Ad or Job Board • Zapier's Talent Acquisition Team Outreach • That said, while Al can be a helpful assistant, your application should still reflect you. You have the opportunity to stand out by being specific, reflective and thoughtful about your own real experiences. • We value transparency and trust — and that starts from day one. We expect you to complete live interviews on your own. In our skills assessments, Al tools may be encouraged — we'll be interested in how you use them. • If we find that you have misrepresented yourself at any stage of the process, we'll remove you from consideration for this and future roles at Zapier. • Please select "Yes" to confirm your understanding and agreement. • Tell us about the most complex REST API integration you built or maintained in production. What made it complex, and how did you handle that complexity? • Describe a time you debugged a complex issue that spanned multiple services or third-party APIs (e.g., auth failures, upstream API changes, webhook delivery issues). Walk us through: what broke, how you triaged it, what tools/logs/traces you used, and how you resolved it. Be specific about the technical details. • https://zapier.com/jobs/culture-and-values-at-zapier • American Indian or Alaska Native • Black or African American • Hispanic or Latino • Native Hawaiian or Other Pacific Islander • Two or More Races • Non-Binary/Gender Non-Conforming • Prefer not to disclose • Straight or Heterosexual • Active Duty Wartime or Campaign Badge Veteran • Armed Forces Service Medal Veteran • Disabled Veteran • Recently Separated Veteran • I do not identify as a veteran • I do not identify as a person with a disability • Zapier may use Artificial Intelligence with this application. Learn more.
No credit card. Takes 10 seconds.