Cloud engineers who understand the cost of running at scale

Infrastructure experience across digital payments, creative software, virtualisation, mobility and connected television. The strongest public example is a production cost programme at an Indian payments infrastructure company.

• Named alongside a colleague in the payments company's account of moving workloads onto spot capacity. The reported EC2 savings were 40 to 50% for the programme.
• The engineering problem connects capacity economics with production operations: lower priced compute is useful only when the workload can tolerate interruptions and changing capacity.
• His career provides relevant operating context across several product businesses; the published cost case provides a specific piece of work to examine.

A Pune based SRE with a public record that combines enterprise infrastructure experience with practical cloud native education. His professional GitHub identifies a global endpoint and cloud security company.

• Publishes cloud native learning material and maintains public repositories that make his technical interests inspectable.
• His community work includes CNCF and Docker participation, providing evidence of sustained engagement with container infrastructure and practitioner education.
• The relevant career pattern is a substantial infrastructure tenure followed by another production focused environment, rather than a sequence of unrelated short assignments.

A Bengaluru based Linux engineer at a global cloud provider, with earlier experience at a cloud native infrastructure company. His public record centres on Flatcar Container Linux.

• Publicly identified as a Flatcar maintainer, with work at the operating system layer rather than only application deployment.
• Maintains an inspectable connection to the project's issue tracking and documentation through his professional GitHub profile.
• His public technical activity addresses the maintenance and release lifecycle of container infrastructure: a different responsibility from configuring a single application's cloud account.

Reliability experience at a global accommodation marketplace and a global video streaming platform. His public work connects distributed system failures with the practical decisions engineering teams make during incidents.

• Coauthored "Automating chaos experiments in production," describing a platform that generated and executed experiments against production systems.
• The work examined whether systems continued to behave acceptably when components slowed down or failed, moving resilience testing beyond assumptions made during design.
• His long running technical writing covers incident analysis, complex system failures and the interaction between people, software and operational work.

A London based infrastructure engineer whose career spans a semiconductor company, a distributed simulation platform, an enterprise open source provider and a global cloud platform.

• Cocreated Thanos with another engineer in 2017, addressing the challenge of scaling Prometheus based monitoring.
• Became a Prometheus maintainer and later worked on the managed Prometheus offering of a global cloud provider.
• Authored a book on efficient Go programming and contributes to profiling, instrumentation and observability work across company and open source environments.

A Montreal based software developer with earlier infrastructure experience at a global payments platform. Her public work makes the implementation and failure modes of production infrastructure unusually visible.

• Authored the payments company's account of introducing Kubernetes for a distributed cron scheduling system.
• The account covers reading controller code, load testing and prioritising etcd reliability before depending on the platform in production.
• Her wider body of work examines Linux, networking, DNS and debugging, connecting operational decisions with the underlying systems rather than treating infrastructure as a collection of configuration files.

An observability software provider, following reliability and staff engineering at a global cloud and internet platform. Based in Sydney, with a second base in Vancouver.

• A published conference presentation examines moving production workloads to ARM infrastructure and the operational trade offs involved.
• Earlier work at a global cloud and internet platform covered load balancing and travel search.
• The public engineering record connects infrastructure choices with compute cost and latency, which is what a team weighing platform cost against performance has to reason about.