Provenance

Vladimir has written more than 100 pieces of content for Docker in the past year. He has also helped us find customer stories that we've been able to document and share throughout the rest of the community, and he's met with multiple product managers internally to share his product feedback.

Fantastic, Vladimir, we're so thankful for you.

Vladimir is among a small number of Docker Captains whose work has both shaped our developer ecosystem and demonstrated technical communication at the highest level.

He has co-authored Docker enterprise customer case studies, including the containerization of an AI infrastructure platform, and his guidance clears the senior editorial and technical review every piece on Docker's official channels must pass. Managing Docker's global recognition program, I see that consistency as direct evidence of his technical depth.

Vladimir's container security expertise is at the upper end of what working practitioners in this field demonstrate. He is one of the people whose technical opinion others actively seek out before making security architecture decisions — not how peers treat a strong personal brand, but how they treat someone whose answers have repeatedly been correct under load.

His open-source infrastructure has passed 725,000 pulls and implements every supply-chain control we wrote about: keyless Cosign signing, SLSA provenance, SBOMs, and continuous scanning.

Across more than fifty practitioners I recruited worldwide for Snyk's Ambassador program, very few could both build and teach at the level Vladimir does — that combination is internationally rare.

Measured against the international standard I hold people to, his command of application security places him among the stronger practitioners I've worked with anywhere. Members sought him out because his answers were reliable under pressure, not because any role was assigned to him.