Kostya Serebryany
Principal Software Engineer at Tesla
Palo Alto, California, United States
Summary
🤩
RockstarKostya Serebryany is a Principal Software Engineer with 15+ years of deep systems and compiler expertise, currently driving Dojo and Autopilot Hardware efforts at Tesla from Palo Alto. He is a long-time contributor to dynamic program analysis and C++ memory-safety tooling—having led development on AddressSanitizer, ThreadSanitizer, libFuzzer and related Clang integrations at Google—bringing rare expertise at the intersection of fuzzing, sanitizers, and compiler code generation. Kostya’s work on OSS-Fuzz and Google’s fuzzer-test-suite demonstrates strong automation and build-engineering skills that materially improve open-source quality and security at scale. Previously he shaped compiler technology at Intel and MCST, giving him a pragmatic, low-level view of performance and reliability tradeoffs. He combines research-quality instrumentation with production-grade engineering, and is known for squeezing both performance and debugging clarity out of complex toolchains.
15 years of coding experience
24 years of employment as a software developer
Stackoverflow
51reputation
2kreached
1answer
6questions
Github Skills (38)
c-language10
libfuzzer10
scripting10
compiler-development10
llvm10
bash10
addresssanitizer10
script10
performance-optimization10
build-automation10
asa10
sh10
fuzzing10
shell10
cprogramming-language10
Programming languages (12)
Github contributions (5)
google/fuzzer-test-suite
Oct 2016 - Aug 2021
Set of tests for fuzzing engines
Role in this project:
QA Engineer / Test Automation Engineer
QA Engineer / Test Automation EngineerContributions:234 commits, 28 PRs, 214 pushes in 4 years 11 months
Contributions summary:Kostya's primary contributions involve writing and modifying test scripts for a variety of fuzzing targets within the `google/fuzzer-test-suite` repository. They wrote test scripts to verify the functionality and identify potential vulnerabilities in multiple software components and libraries. Commits focus on improving test coverage and ensuring the reliability of the fuzzing process by incorporating diverse test cases. The user also used the `test-libfuzzer.sh` scripts to analyze the fuzzing results.
fuzz-testingtestingfuzzingfuzzerstability
google/oss-fuzz
Oct 2016 - Dec 2019
OSS-Fuzz - continuous fuzzing for open source software.
Role in this project:Automation Engineer / Build & Release Engineer
Automation Engineer / Build & Release EngineerContributions:244 commits, 158 PRs, 354 pushes in 3 years 2 months
Contributions summary:Kostya primarily contributed to build scripts and configurations within the OSS-Fuzz project. Their work involved modifying build processes for various projects, including pcre2, freetype2, llvm, and ffmpeg. They also added and updated seed corpora, made changes to compiler flags, and addressed build-related issues, demonstrating a focus on automating builds and integrations for fuzzing.
oss-fuzzfuzz-testingossvulnerabilitiessecurity
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.