Thomas Orozco
Software Engineer at Facebook
London, England, France
Summary
🤩
Rockstar🎓
Top SchoolThomas Orozco is a versatile software engineer with 13 years’ experience building robust back-end systems, currently at Facebook in London. He has strong systems and DevOps instincts demonstrated by work on high-profile open-source projects like Buck2, Watchman and Supercronic, where he improved build/action execution, artifact handling, and reliability in container cron and file-watching tools. Previously a VP of Technology at Aptible and product/solutions lead at Scalr, he has hands-on experience scaling deployments, CI/CD and reducing release time and failure rates dramatically. He blends deep Rust, C++ and systems knowledge with pragmatic product sensibilities from roles in product management and as a startup CTO. Colleagues rely on him to refactor tricky subsystems and add observability and fault-tolerance—often surfacing subtle race conditions and recovery paths others miss. Fluent in both engineering and operational concerns, he repeatedly turns complex distributed problems into dependable, well-tested solutions.
13 years of coding experience
4 years of employment as a software developer
Master of Science (M.Sc.), Management, 3.66/4, Master of Science (M.Sc.), Management, 3.66/4 at HECLycée Saint Louis
English, French
Stackoverflow
54,202reputation
6.0mreached
663answers
9questions
mysql
top-5%
django-models
top-5%
ubuntu
top-1%
dictionary
top-5%
recursion
top-5%
django
top-1%
Github Skills (80)
python10
testing10
http10
c1110
ubuntu10
c1710
low-level-programming10
code-generation10
pip10
flask10
async10
django10
init10
linux10
dockers10
Programming languages (19)
Github contributions (5)
aptible/supercronic
Jul 2017 - Nov 2020
Cron for containers
Role in this project:
Back-end & DevOps Engineer
Back-end & DevOps EngineerContributions:1 release, 3 reviews, 96 commits in 3 years 5 months
Contributions summary:Thomas focused on developing core functionality and testing for the `supercronic` project, a cron for containers. They implemented initial features and added tests for the `runJob` functionality, demonstrating a focus on ensuring the reliability of the project's core features. The user also refactored code, handled signal interruptions, and addressed potential race conditions. They implemented flag handling and added support for CRON_TZ.
containerssupercronicdockercroncontainer
krallin/tini
Feb 2015 - Jul 2021
A tiny but valid `init` for containers
Role in this project:Backend Developer
Backend DeveloperContributions:36 releases, 229 commits, 113 PRs in 6 years 5 months
Contributions summary:Thomas primarily contributed to the development of `tini`, a minimal init system for containers. Their work focused on adding argument handling capabilities, refactoring code for clarity, and implementing features like configurable verbosity levels. The user also added a basic test harness and improved the quality of the logging messages.
containersseccomptinyinit-systemlinux
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.