In-houseMay 2023 — Aug 2026 · 3 yrs 4 mos

Head of Technology, Partner Experience & Payments

Discover Financial Services (a Capital One company)

Brought in to set the technology direction for a newly formed Partner Enablement and Experience domain — then to carry it through the Capital One merger. Accountable for architecture, engineering and data strategy for Discover and Diners partner-experience and payment platforms, and for platform convergence after the merger.

Days to onboard a partner
73 → 5–7
Days to onboard a partner
Volume surge absorbed by the same service team
3,200%
Volume surge absorbed by the same service team
Transactions a day
200M
Transactions a day
Convergence across 144 platforms
£40M
Convergence across 144 platforms

Context

Partner Enablement and Experience was a newly formed domain with a sprawling estate of in-house, SaaS and legacy applications. Functionality was duplicated across systems, and the partner and customer experience suffered for it.

Onboarding a new partner took 73 days, with manual steps — including testing — along the way. Applications were slow, Party Hierarchy performance was poor, and legacy applications and the modern Profile data were frequently out of sync.

Diners applications lacked a clear technology direction and carried open vulnerabilities, and PCI DSS 4.0 compliance was a pressing requirement across the estate. The brief: make the platforms resilient, expose them through APIs, and move to an event-driven architecture.

Role & scope

Reporting to
Head of Application Architecture
Remit
Partner Enablement and Experience, plus platform convergence after the Capital One merger
Team
30-person architecture & engineering organisation, led through Architecture and Engineering Managers
Platforms
Discover and Diners partner-experience and payment platforms, integrated with settlement, fraud and disputes
Data
Data strategy and governance: metadata curation, data at rest, OLTP/OLAP integration and data lake ingestion
Stakeholders
Product, business and executive leadership; the post-merger Integration Management Office
Scale
200M transactions a day at 10K+ TPS, against 99.999% availability expectations

Milestones

  1. May – Jul 2023

    Set the North Star

    Defined the North Star for Partner Enablement and Experience: platform consolidation, and modernisation wherever it paid back. Standardised on event-driven architecture with a domain-driven model, CQRS and hexagonal architecture.

  2. Aug – Dec 2023

    Moved Profile data to a multi-region cloud

    Designed and led the move of Profile data from the data centre to a highly resilient, multi-region, multi-cluster OpenShift platform on AWS (US East and US West). Ran a GraphQL proof of concept on MongoDB Atlas for Party Hierarchy, and managed the MongoDB vendor relationship, including contract management and risk analysis.

  3. Jan – May 2024

    Made the platforms merger-ready

    Assessed the impact of the post-merger volume surge on availability, SLAs and SLOs. Worked with the Integration Management Office to prioritise scalability work, brought in third-party contractors to scale capacity fast, and supported successful testing of the Capital One network transition.

  4. May 2024 onwards

    Converged platforms, unified the experience

    Led platform convergence and the new P3 solution to eliminate duplicate functionality and unify the customer experience, cutting partner onboarding from 73 days to 5–7. Introduced Agentic AI to the Referral Management Service to absorb the post-merger surge.

Key achievements

Partner onboarding: 73 days to 5–7

Challenge
Onboarding a partner took 73 days, slowed by functionality duplicated across systems and manual steps, including testing.
Approach
Consolidated platforms and built the modern P3 solution to remove duplication, unify the experience and streamline the onboarding journey.
Outcome
Onboarding cut to 5–7 days, depending on the merchant, with a unified customer experience.

Absorbing a 3,200% surge with Agentic AI

Challenge
The Capital One merger drove a 3,200% surge in referrals — the cases merchants raise when a transaction doesn't go through.
Approach
Introduced an AI agent into the Referral Management Service that triages, classifies and prioritises every referral, and resolves the simple cases itself. Live in four months.
Outcome
The same customer service centre team absorbed the surge within SLA, with less reliance on temporary contractors.

Merger-ready resilience

Challenge
The post-merger volume surge put availability, SLAs and SLOs at risk.
Approach
Assessed the impact, prioritised scalability work with the Integration Management Office, and scaled capacity rapidly with third-party contractors.
Outcome
Supported a smooth transition of the Capital One network; secured Investment Council approval and directed the £40M, 144-platform convergence programme.

Data strategy & governance

Challenge
Data spread across in-house, SaaS and legacy applications, with legacy and modern Profile data out of sync.
Approach
Led metadata curation and the strategy for data at rest; integrated OLTP and OLAP workloads; drove ingestion into the data lake; and anchored it all in domain-driven data models and data governance.

Resilient, modern foundations

Challenge
Slow applications, legacy and modern Profile data out of sync, and a poorly performing Party Hierarchy.
Approach
Moved Profile data to multi-region, multi-cluster OpenShift on AWS; standardised on event-driven architecture with DDD, CQRS and hexagonal architecture; proved GraphQL on MongoDB Atlas for Party Hierarchy.

Highlights

  • Owned the target architecture and transition roadmap for partner-enablement and payment platforms processing 200M transactions a day at 10K+ TPS.
  • Led and coached a 30-person architecture and engineering organisation through Architecture and Engineering Managers.
  • Led data strategy and governance: metadata curation, data at rest, OLTP/OLAP integration and data lake ingestion, built on domain-driven data models.
  • Identified enterprise capacity risks after the Capital One merger, secured Investment Council approval and directed the £40M, 144-platform convergence programme.
  • Drove AWS East/West multi-region resilience, CI/CD and automated quality controls to support 99.999% availability.
  • Translated PCI DSS 4.0 and other regulatory requirements into architecture and controls; applied governed Agentic AI to vulnerability identification and audit monitoring.

How I led

From stressed, siloed teams to one team

The situation
With a heavy delivery agenda, people were stretched and stressed. Teams were working in silos, and collaboration between them had broken down.
What I did
I led people first. I made a point of recognising the hard work behind the results, visibly and specifically. When things went wrong, I took ownership of the mistake myself — no blame game.
What changed
The friction went out of the system. Without the fear of blame, teams stopped protecting their own boundaries and started collaborating across them.
  • Recognise the effort behind the outcome, not just the outcome.
  • Own the mistakes as the leader; give the credit to the team.
  • No blame game — fix problems together, then learn from them.
  • Absorb pressure from above so teams can focus on what matters.

In their words

“Srini set clear technical direction and consistently brought the right issues to leadership’s attention, influencing decisions with sound judgment rather than just executing instructions.”
Senior Software Engineering Manager, Capital One · Worked with Srini
“Srini led the development of a comprehensive vision for a consolidated customer portal that unified the customer experience, eliminated friction points, and significantly improved overall customer satisfaction.”
Director - Application Architecture, Discover Financial Services · Managed Srini
“High-demand work tends to route through a manager first, and instead of passing that pressure down, he absorbed it himself.”
Expert Application Architect, Capital One · Reported to Srini
“No matter how challenging the situation, he remains cool and helps the team focus on finding the right solution rather than assigning blame.”
Principal application architect, Discover Financial Services · Reported to Srini
All testimonials →

Lessons

Silos are rarely a structure problem — they're a trust problem. Remove the fear of blame and collaboration follows.

When a leader owns the mistakes and gives away the credit, teams stop protecting themselves and start protecting the outcome.

Technology & domain

  • AWS multi-region
  • OpenShift (OCP)
  • Event-driven architecture
  • Domain-driven design
  • CQRS
  • Hexagonal architecture
  • MongoDB Atlas
  • GraphQL
  • Data governance
  • Metadata management
  • Data lake
  • OLTP / OLAP
  • Agentic AI
  • PCI DSS 4.0
  • CI/CD
  • ServiceNow
  • Salesforce

Contact

Let's talk.

I'm based in London, UK. Whether it's a leadership role, an advisory engagement or a transformation that needs shaping — my inbox is open.

srini.vankee@gmail.com