From powering contactless card systems used by 55M+ cardholders to building an enterprise tokenization platform processing over 10B records per day, I build infrastructure and platforms that scale reliably and operate with precision.
Building out Capital One's real-time messaging platform, designed to power intelligent messaging journeys for use cases across our enterprise through a low code contribution model.
Full-stack developer responsible for realtime customer messaging and online banking services, catered towards Capital One's heavy spending small businesses.
Led technical efforts for realtime customer messaging re-haul and expansion, while also enhancing + managing multiple services used to power our online banking customer experience.
Notable products under scope: Venture X Business, Spark 2% Cash Plus
Developer on the Turing Platform - a Capital One ultra high performance, low latency, and cloud-based platform that keeps customer data secure. Turing processes 10B+ records/day, peaking at 2M+ operations/second.
On team responsible for the core platform encryption/decryption service - but I didn't let this stop me from contributing across the other teams responsible of items such as Turing SDKs, Databases, and our onboarding UI.
Initiatives I owned start to finish:
+ Architected and executed an updated DynamoDB approach to optimize connection pooling strategy and reduce DB overload risk
+ Designed and implemented partial detokenization in our core API used across our enterprise, revealing only certain portions of sensitive data when retrieving it from our platform i.e. last four of SSN, last four of bank account numbers
+ Extended partial detokenization by introducing it across our enterprise SDKs in Java, Golang, Python, and Rust
+ Owned re-architecture and redesign of our onboarding UI
+ Streamlined our enterprise support channel by introducing a bot to automate our most common CX workflows with enterprise users
+ Team representative for weekly platform release meetings - collaborating with sibling teams to ensure platform rollouts occurred while maintaining 99.99% uptime across enterprise (I think we coincidentally went down once for <5 minutes during a rollout due to an upstream hiccup).
