We're looking for an Architect with backend expertise to join the Architecture team at Zapier. Over 3 million professionals already use Zapier to save more time, but there are millions more to reach. Do you want to help shape a sustainable backend architecture across a growing set of product teams so that we can support our mission to make everyone more productive at work? Then keep reading...
We know applying for and taking on a new job at any company requires a leap of faith. We want you to feel comfortable and excited to apply at Zapier. To help share a bit more about life at Zapier, here are a few resources in addition to the job description that can give you an inside look at what life is like at Zapier. Hopefully, you'll take the leap of faith and apply.
Zapier is proud to be an equal opportunity workplace dedicated to pursuing and hiring a diverse workforce.
Even though our job description may seem like we're looking for a specific candidate, the role inevitably ends up tailored to the person who applies and joins. Regardless of how well you feel you fit our description, we encourage you to apply if you meet these criteria:
You’re a force multiplier for engineering. Everything you do is in the service of making the engineering team more efficient at delivering higher quality, more secure and reliable products for our customers. This might be code, documentation, lightning talks, mentoring, research, or whatever it takes.
You’ve scaled large systems with many services. You’ve worked with small 3 tier systems, in a cloud/SaaS environment, and you’ve scaled systems up to support millions of customers with polyglot microservices and event-driven architectures. You have preferences on particular technologies and patterns, but you know there are always tradeoffs and carefully consider teams and use cases before making recommendations. You’ve built systems that have failed, and now you know how to design systems that are resilient to failure.
You balance long and short term. You’re careful to resist taking shortcuts that lead to excessive technical debt, but you’re also not an “architecture astronaut.” You make pragmatic architecture designs and decisions based on real-world experience and the input of the engineering team, and you help experiment with new technology and patterns in a sustainable way. You don’t build excessive abstractions or unnecessarily risk the business on unproven technology.
You help teams build understandable systems. You know that architecture is often about telling a story so that engineers have a shared understanding, and we can simplify complex models through high-level diagrams. You always start projects with specs so that everyone is on the same page. You may be familiar with models like C4, but you’re not overly dogmatic to the point of slowing things down. You know that code is an important part of the story, so you’re also interested in automated ways of keeping documentation up-to-date.You're a mentor. You’re not only interested in growing systems but also people. You want to help other engineers learn new technologies and techniques, and you’re equally ready to learn from other engineers.
Finally, you’re an engineer. Although you’re primarily concerned with improving how other engineers ship code, you’re also more than capable of shipping code yourself. Your code is often a tool, service, or pattern that other engineers will build on, but if the need arises, you can ship a feature as well.
Things You'll Do
- Help scale a fast-growing and unique system. Our workflow engine connects with thousands of APIs across thousands of servers.
- Document and diagram systems to help engineers better visualize our architecture and ultimately improve it.
- Help refactor large services into multiple smaller services, including splitting databases, while considering the impact on the organization and our products.
- Help improve the quality of our releases by encouraging better patterns of system design, API design, testing, security, and data encapsulation.
- Help improve deployment systems to reduce bottlenecks while making deployments more reliable.
- Embed on product teams, helping to design systems and ship code for critical projects.
- Give back to the community via open source or blog posts.
- As a part of our All Hands Support initiative, help customers have the best possible experience with Zapier.