Andrew Wilkins is a seasoned tech lead and principal engineer with 17 years’ experience building and operating observability and ingestion systems, currently leading Elastic’s Observability Ingest efforts from Perth, Australia. He blends deep systems and performance engineering—evidenced by contributions to Elastic APM agents, APM Server, the Elasticsearch Go client, and the OpenTelemetry Collector—with hands-on DevOps and CI/CD improvements that speed testing and deployments. Andrew has led cross-team architectural work such as adding OTLP support, designing multi-tenant managed ingest services, and introducing dynamic metrics indexing into Elasticsearch, while also paying down technical debt and modernising build and test infrastructure. A pragmatic mentor and organiser, he routinely translates product needs into reliable, performant backend implementations and has a track record of subtle but impactful fixes (e.g., retry-safe transport handling and Lambda/ioredis bug fixes) across major open-source projects. He combines a generalist’s breadth with focused expertise in high-throughput, low-latency telemetry pipelines and a taste for optimising real-world systems.
17 years of coding experience
19 years of employment as a software developer
Bachelor of Computer Science (Hons) Computer Science Information Technology Systems, Bachelor of Computer Science (Hons) Computer Science Information Technology Systems at The University of Western Australia
Contributions:26 releases, 513 reviews, 1044 commits in 5 years 2 months
Contributions summary:Andrew contributed to the Go Agent for Elastic APM, primarily focusing on supporting new Go versions by fixing compatibility issues and upgrading dependencies. They addressed build-related problems for Go 1.8 by refactoring code to avoid deprecated methods, implemented a new feature to allow the specification of an agent's transaction name, and also fixed tests that involved the use of HTTPS/2. The user's efforts included fixing error handling and ensuring consistent code across the project by applying improvements to error reporting and code quality standards.
Orchestration engine that enables the deployment, integration and lifecycle management of applications at any scale, on any infrastructure (Kubernetes or otherwise).
Role in this project:
Back-end Developer
Contributions:1856 commits, 812 PRs, 2 pushes in 3 years 8 months
Contributions summary:Andrew appears to be primarily focused on back-end development, contributing to the core functionality of the "juju/juju" orchestration engine. Their work involved modifying and refactoring the bridge script and adding features to support container management (LXD) and Cinder volumes, as well as fixing issues in the existing code. These changes suggest a focus on networking, cloud infrastructure integration, and the core engine logic.
operatormicroserviceyamljujuk8s
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.