Worked on dating product systems that needed to represent identity, preferences, and fit more carefully than simple categories allowed.
- role
- Senior Lead Software Engineer, Android
- context
- OkCupid matching product at consumer scale
evidence
- Gender and orientation representation work in a large matching product
- Product architecture for discovery, profiles, and native-client surfaces
- Human nuance translated into product and data-model constraints
At OkCupid, the interesting product problem was not just scale. It was representation: how to model identity, preference, consent, orientation, and fit in a product where crude categories create bad matches and bad user experiences.
That kind of work sits between product strategy, data modeling, interface design, and backend architecture. The software has to respect human nuance without making the product impossible to understand, operate, or evolve.
When a product has to reason about people, the hard part is often the model underneath it. Better output comes from better representations of what the system is actually trying to understand.