Andrew Poydence
Software Engineer at Google
Queen Creek, Arizona, United States
Summary
🤩
Rockstar🎓
Top SchoolAndrew Poydence is a software engineer with 12 years’ experience building high-performance, reliable systems at companies including Google and Lockheed Martin. He favors functional programming—working in F# and functional-style C#—and has led telemetry and data-processing designs that improved performance dramatically while shaping team paradigms. At Lockheed he led a telemetry redesign that supported missile flight tests and terabyte-scale archiving, and at Google he contributes to cloud and infrastructure projects, including notable open-source work on Google Cloud Go libraries and the GoMock testing framework. He blends backend systems, test automation, and cloud infra skills (including Windows-builder improvements for Google Cloud Build) and enjoys authoring data structures and elegant algorithms. Based in Queen Creek, Arizona, he pairs practical production impact with a continuous curiosity for new languages and surprising algorithmic solutions.
12 years of coding experience
10 years of employment as a software developer
Bachelor's of science, Electrical engineering, Bachelor's of science, Electrical engineering at University of Oklahoma
Stackoverflow
10,319reputation
3.2mreached
242answers
61questions
java
top-5%
go
top-5%
Github Skills (41)
build-time10
socket-io10
go-modules10
google-cloud-platform10
docker10
testing10
storage10
buildx10
google-cloud-datastore10
dockers10
datastore10
google-cloud-storage10
build-engine10
build210
socket10
Programming languages (12)
Github contributions (5)
cloudfoundry/loggregator-release
Sep 2014 - Oct 2018
Cloud Native Logging
Role in this project:
Backend Developer
Backend DeveloperContributions:8 releases, 305 commits, 44 PRs in 4 years 1 month
Contributions summary:Andrew's commits focus on fixing bugs and improving the stability of log aggregation within the `loggregator-release` repository. The user addressed issues related to tailing logs and scaling applications, resolving errors that occurred when sockets were closed unexpectedly. These changes involved modifying code related to handling socket connections and ensuring continuous log streaming. The fixes ensure that the DEA agent can gracefully handle closed sockets during app scaling events.
golangcloud-foundryfluentdloggingcff-wg-app-runtime-platform
golang/mock
Nov 2018 - Nov 2019
GoMock is a mocking framework for the Go programming language.
Role in this project:Back-end Developer & Test Automation Engineer
Back-end Developer & Test Automation EngineerContributions:3 releases, 20 commits, 52 PRs in 1 year
Contributions summary:Andrew primarily focused on modifying the `gomock` framework, a mocking framework for the Go programming language. Their contributions involved refactoring test artifacts and ensuring the correct callstack is pointed at the offending line in production code. The user also introduced changes to the mock generation process, including the implementation of `WantFormatter` and `GotFormatter` for better failure message formatting during testing. They also added documentation to the exported functions.
golangtestingmocksmockinggomock
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.