Dmitry Vyukov
Principal Software Engineer at Google
Bavaria, Germany
Summary
🤩
Rockstar🎓
Top SchoolDmitry Vyukov is a Principal Software Engineer with 15+ years focused on multicore, multithreading, lock-free algorithms, and high-performance distributed systems, currently driving core tooling and runtime correctness work at Google from Bavaria. He is a prolific open-source contributor across LLVM/Clang, Google sanitizers, Go, syzkaller and Abseil—best known for deep ThreadSanitizer and fuzzing infrastructure improvements that harden compilers, runtimes, and kernels. His work blends low-level instrumentation, build/test infrastructure, and synchronization primitives, delivering tangible performance and correctness gains (for example, coverage-guided fuzzing and TSAN build fixes). Dmitry’s background in high-performance computing (MSIT, Bauman MSTU) and early VoIP/P2P production experience give him a rare combination of research-grade concurrency expertise and pragmatic systems engineering. He frequently tackles efficiency and correctness trade-offs that are invisible to end users but critical for large-scale software reliability.
15 years of coding experience
12 years of employment as a software developer
1038MSIT High-Performance Computing Systems, MSIT High-Performance Computing Systems at Bauman Moscow State Technical University
English, Russian
Stackoverflow
86reputation
2kreached
2answers
0questions
Github Skills (58)
code-optimization10
benchmark10
c-language10
back-end-development10
scripting10
mutex10
barrier10
testing10
memory-model10
benchmarking10
c1110
data-structure10
gcc10
c1710
kernel10
Programming languages (11)
Github contributions (5)
dvyukov/go-fuzz
Apr 2015 - Mar 2020
Randomized testing for Go
Role in this project:
Back-end Developer
Back-end DeveloperContributions:8 reviews, 712 commits, 150 PRs in 4 years 11 months
Contributions summary:Dmitry's commits primarily focus on adding coverage instrumentation to the `go-fuzz` project, a tool for randomized testing of Go code. They implemented a `go-fuzz-build` tool to instrument Go source files, enabling code coverage tracking during fuzzing. The user made several changes to the core `cover.go` file, including adding import statements, modifying the `Visit` method to instrument blocks and control flow statements, and adding functionality for printing the instrumented code.
golangrandomizedtestingfuzzingtesting-tools
google/syzkaller
Oct 2015 - Jan 2023
syzkaller is an unsupervised coverage-guided kernel fuzzer
Role in this project:Back-end Developer
Back-end DeveloperContributions:3041 reviews, 4398 commits, 2858 PRs in 7 years 4 months
Contributions summary:Dmitry focused on refactoring the coverage backend for syzkaller by improving the handling of data structures used to represent the coverage. They made several changes to the code that improved efficiency by implementing changes to the way coverage points are stored and managed, and refactored code to remove duplication, and improve code readability. This improved the overall performance of the code, optimized memory usage, and potentially addressed related bugs in the system.
kernelsecurity-toolscoverage-guidedfuzz-testingsecurity
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.