Zach Hauser Email & Phone Number

Toronto, Ontario, CA

San Francisco, California, US

San Francisco, California, US

• While at Twilio, I worked in the Platform organization, which provides the tools and services that enable every Product Engineering team to develop and operate their systems at scale. Over 4.5 years, I worked on nearly.
• Observability: logs, metrics, events, and traces — and insights from them all! We owned a mix of in-house systems and SAAS solutions, working primarily to ensure their value for incident response and prevention, and.
• Compute: VMs, containers, and Kubernetes clusters. We kept one foot in the past and one in the future, actively developing both the battle-tested systems that orchestrated tens of thousands of VMs and the modern.
• Service Mesh: building a custom service mesh based on Envoy Proxy. My full-time stint on this team ended in late 2018, but I remained a subject matter expert on our highly-available, performance-critical service.
• Application Bootstrapping: automating the creation process of new microservices, promoting best practices and eliminating tedious work. Our system created scaffold codebases and automatically integrated them with.
• Platform Access: developing self-service systems for managing firewalls, IAM policies, secrets, AWS accounts, VPCs, and network primitives.-----[𝘤𝘰𝘯𝘵𝘪𝘯𝘶𝘦𝘥 𝘣𝘦𝘭𝘰𝘸]

San Francisco, California, US

• [𝘤𝘰𝘯𝘵𝘪𝘯𝘶𝘦𝘥 𝘧𝘳𝘰𝘮 𝘢𝘣𝘰𝘷𝘦]Some projects I'm especially proud of:
• Redesigning our log aggregation system (~1 PB logs/month) to meet the GDPR compliance deadline and avoid a regulatory fine of $10M+. I worked with stakeholders across the company (from Legal, Security, Architecture.
• Delivering foundational components of our Envoy service mesh, which was a key requirement for Twilio's effort to attain HIPAA compliance and unlock the enormous healthcare market. I built a bidirectional GRPC streaming.
• Contributing significantly to the multi-year effort to decommission our monolithic AWS accounts and move to a multi-account model (for scalability, security, and developer productivity). Highlights: (1) I rewrote key.

San Francisco, California, US

• [𝘤𝘰𝘯𝘵𝘪𝘯𝘶𝘦𝘥 𝘧𝘳𝘰𝘮 𝘢𝘣𝘰𝘷𝘦]
• Developing a tech talk that introduced early-in-career engineers to the concept of "service-to-service communication" and its fundamental importance in microservice architecture. We discussed concepts such as service.
• Launching and stewarding a working group for the common API infrastructure via which most Platform services are accessed by internal customers, which previously had no real owner. The working group drove improvements.
• lots of Java and Python; a little bit of a bunch of other languages
• some Javascript, Typescript, React
• cgroups, Docker, Kubernetes

Claremont, California, CA, US

Mentored students one-on-one and in small groups, covering core classes (introductory object-oriented programming, introductory functional programming, and upper-level programming languages theory).I certainly helped with a lot of coursework, but best of all was when I was able to get a tricky core concept to really click for someone. I enjoy teaching and.

San Francisco, California, US

Developed a Slack chatbot that aided in incident response by automatically providing insight on customer impact for on-call engineers (often before they even got to their laptops!). I worked with the Platform Observability team, which I later returned to full-time, as they developed a new log aggregation system for Twilio. The chatbot I built served a.

New York, NY, US

Designed and built a reverse proxy server that cached, tweaked, and replayed backend responses in an extremely unreliable staging environment, helping make automated UI testing of the mobile app viable and eliminating 30% of build failures.I learned a ton from a talented group of developers that Amex had acqui-hired as the core of an "internal innovation".

Computer Science (Major) & Classics (Minor)

Education record

Education record