—
A full-stack engineer with an unusually broad technical range, Kelly Guo has worked across languages, frameworks, and cloud platforms with ease. But what sets her apart isn’t just versatility, it’s her ability to take an idea with no technical foundation and turn it into something scalable, reliable, and built for real-world use.
That ability has defined her work at Ditto, where she remains a core part of the company’s engineering leadership. She joined at the earliest stage, before a single line of production code existed. “I was involved at the idea stage, before any technical foundation existed,” she explains. From the beginning, she owned the entire stack, frontend, backend, infrastructure, and operations, while also helping shape the product itself.
In those early days, Kelly wasn’t just writing code; she was making the foundational decisions that would determine how the system evolved. She built the backend from scratch, designed the service architecture, and translated product ideas into working systems. As Ditto grew from an MVP into a production platform, her role grew with it.
Today, she operates in a Head of Engineering capacity, though her influence has long extended beyond any title. She still drives architectural decisions and reviews, but her focus has shifted toward long-term direction and system design. Along the way, she has onboarded engineers, established coding standards, and ensured that the system remained coherent as the team scaled.
A large part of Ditto’s stability today traces back to the infrastructure Kelly designed early on. She built a system that could move fast without constantly breaking or needing to be rewritten, a balance that’s harder to achieve than it sounds. “One of the key challenges was building something that could evolve quickly without frequent rewrites,” she says.
To make that possible, she introduced a background task architecture that separates asynchronous work from core application flows, along with delayed task execution to support time-based product logic. These systems quietly power much of the user experience, from notifications to workflow orchestration. Later, she led the move to Kubernetes, enabling zero-downtime deployments and giving the team far more confidence in shipping changes.
Kelly also played a critical role in enabling Ditto’s matchmaking system. While she wasn’t the one designing the algorithm itself, she built the infrastructure that allows it to work at scale. That meant creating flexible data models and systems capable of handling asynchronous, evolving logic. The result is a product that moves away from traditional swipe-based interactions and instead focuses on helping users meet in real life.
Her work directly supports that goal. By designing systems that guide user behavior through timing, automation, and structured flows, she helped reduce the friction between matching and actually meeting. “The goal wasn’t endless in-app engagement,” she notes, “but helping people get to real-life dates faster.”
Beyond the technical layer, Kelly Duo’s impact has been just as important on the organizational side. She helped build not only the system, but the engineering culture around it, one that could scale without losing clarity or direction. Strong early decisions meant the company avoided major rewrites, a factor that proved critical as Ditto grew and raised funding.
Looking back, she doesn’t point to a single feature or system as her biggest achievement. Instead, it’s the bigger picture: building something from scratch that didn’t have to be torn down and rebuilt later. “I’m most proud of building the MVP and evolving it into a production system that scaled without major rewrites,” she says.
It’s a simple statement, but in engineering, that kind of outcome is anything but.
—
