Martin Churchill
Software Engineer at Google
England, United Kingdom
Summary
🤩
Rockstar🎓
Top SchoolMartin Churchill is a software engineer with 10 years' experience at Google Play and a PhD-trained background in programming language semantics. He combines deep research experience from a postdoc at Swansea with practical expertise in backend systems, security, and scalable cryptographic logs, having contributed to high-profile open-source projects like Certificate Transparency and Trillian. At Google he has worked across teams including Play, Ads, Geo and Cardboard, translating formal methods thinking into robust, production-grade code. Colleagues rely on him for debugging complex race conditions, improving SCT handling and storage APIs, and pragmatic refactors that reduce memory leaks. Based in England, he brings a rare mix of academic rigor and hands-on security engineering to large-scale distributed systems.
10 years of coding experience
9 years of employment as a software developer
Bachelor of Arts (BA), Mathematics and Computer Science, First, Bachelor of Arts (BA), Mathematics and Computer Science, First at University of OxfordDoctor of Philosophy (PhD), Computer Science, Doctor of Philosophy (PhD), Computer Science at University of Bath
Github Skills (22)
c-language10
back-end-development10
code-review10
security10
go10
x50910
openssl10
cryptography10
cprogramming-language10
grpc10
mysql9
api-design9
testing9
tls129
tls139
Programming languages (7)
Github contributions (5)
google/trillian
May 2016 - Aug 2020
A transparent, highly scalable and cryptographically verifiable data store.
Role in this project:
Back-end Developer
Back-end DeveloperContributions:28 releases, 83 reviews, 285 commits in 4 years 3 months
Contributions summary:Martin primarily contributed to the Trillian project by addressing issues related to log operations and storage. They worked on implementing and debugging the get-leaves-by-index and get-leaves-by-hash handlers within the RPC server. Furthermore, they were involved in the core logic for the integration and sequencing of leaves, the handling of unsequenced data, and the management of the signed log root, all core back-end features. Code changes include adjustments to the storage API and database schema.
verifiablecryptographyscalabletransparentcertificate-transparency
google/certificate-transparency-go
Apr 2016 - Jul 2020
Auditing for TLS certificates (Go code)
Role in this project:Back-end Developer & Security Engineer
Back-end Developer & Security EngineerContributions:30 releases, 11 reviews, 87 commits in 4 years 3 months
Contributions summary:Martin primarily focused on enhancing the security and functionality of the CT log auditing code. Their contributions involved the addition of issuer common name matching to the scanner, enabling the printing of full certificate chains, and implementing features related to SCT (Signed Certificate Timestamp) handling within the Trillian project. Further work included addressing issues with SCT signing and improving the verification process, showcasing a strong understanding of cryptographic protocols and backend infrastructure. The user also worked on adding various checks to ensure compliance with RFC standards.
golangssltlscertificatescsr
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.