Farmington, Connecticut, United States
I lead enterprise security architecture for complex, high-scale consumer environments — setting the technical direction across identity, security orchestration, privacy, and payment security, and making sure it actually holds together when dozens of platforms, vendors, and business units have to interoperate. I own the architectural decisions, but I also stay close enough to the implementation to know when a design won't survive contact with production. That means I'm reviewing integration patterns, evaluating vendor security postures, and designing the trust boundaries for systems that serve millions of users — not just drawing diagrams and handing them off. The pattern I keep seeing after nearly a decade across multiple iconic consumer brands: organizations invest in best-in-class security tools, then struggle to make them work together securely, consistently, and at scale. The failure point is almost never a single platform. It's the seams between them — where identity meets orchestration, where payment flows cross vendor boundaries, where privacy mandates collide with business velocity. That integration-layer architecture — making the whole security ecosystem coherent, not just the individual pieces — is where I focus. I sit on the Okta Customer Advisory Board, working with their product team on the problems practitioners face in production. I write about these challenges here. If you're navigating a complex security architecture challenge, my DMs are open.
Selected as a member of Okta’s Customer Advisory Board, representing enterprise stakeholders across both Auth0 (Customer Identity) and Okta Workforce Identity platforms. Collaborate directly with Okta product leadership to provide strategic feedback, share real-world use cases, and influence the product roadmap. As part of this role, contribute insights on identity and access management (IAM), authentication flows, security best practices, scalability, developer experience, and enterprise adoption challenges.