Chris Smith
Principal Software Engineer at Zocdoc
New York, New York, United States
Summary
🤩
Rockstar🎓
Top SchoolChris Smith is a Principal Software Engineer in New York with 11 years of experience building distributed systems, developer platforms, and production ML pipelines. At Zocdoc he progressed from hands-on service development to leading platform initiatives that improve developer productivity, CI/CD, observability, and infrastructure reliability. He contributes actively to open-source projects—most notably OpenTelemetry—where his backend work improved trace ingestion and sampling across diverse formats, and to tooling like Pants and NUnit to harden builds and test automation. Comfortable across JVM/Python ecosystems, Spark/LightGBM ranking, and cloud migrations, he combines pragmatic engineering with a focus on observability and operational excellence. Colleagues rely on him to translate tricky, system-level problems into robust, maintainable solutions that scale.
11 years of coding experience
12 years of employment as a software developer
Bachelor of Science (B.S.) Computer Science, Bachelor of Science (B.S.) Computer Science at The College of New Jersey
Github Skills (47)
apache-spark10
docker10
test-driven-design10
teamcity10
data-science10
testing10
nunit10
machine-learning10
test-framework10
pyspark10
build-system10
dockers10
zipkin10
ml10
scala10
Programming languages (13)
Github contributions (5)
nunit/nunit
Apr 2015 - Sep 2016
NUnit Framework
Role in this project:
QA Engineer / Test Automation Engineer
QA Engineer / Test Automation EngineerContributions:17 commits, 9 PRs, 8 pushes in 1 year 5 months
Contributions summary:Chris primarily contributed to improving the test automation framework of the NUnit project. Their work involved fixing issues related to XML escaping in test output, adding new test cases for specific scenarios, and enhancing the integration with TeamCity by modifying the output format. They also updated test configurations and refactored existing tests to use test IDs for more robust parallel execution. This demonstrates a focus on test quality, reporting, and maintainability within the framework.
dotnettestingtest-frameworkc-sharpnunit-framework
open-telemetry/opentelemetry-collector
Jun 2020 - Oct 2020
OpenTelemetry Collector
Role in this project:Back-end Developer
Back-end DeveloperContributions:13 reviews, 7 commits, 11 PRs in 5 months
Contributions summary:Chris primarily contributed to the OpenTelemetry Collector's trace component, focusing on integrating and translating different trace formats. Their work involved modifying the Zipkin receiver to correctly handle timestamps, addressing issues in OC to internal and OC span type conversions, and unifying the parsing logic for Zipkin v1 and v2 annotations and tags. They also implemented changes to the tail sampling processor to ensure proper trace handling, including combining batches and allowing parsing of string tags. Their contributions enhanced the collector's ability to process and manage trace data from various sources.
opentelemetry-collectortracingtempoobservabilitytelemetry
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.