Russell White Get in touch
Russell White

Engineering leadership for systems that cannot go down.

Senior Vice President at JPMorgan Chase, leading senior full-stack and SRE teams. Open to director-level roles, remote.

Get in touch LinkedIn

Summary

I started as a field engineer replacing hardware in bank branches and now lead senior full-stack and SRE teams inside one of the most heavily regulated technology environments in the world. The range matters more than the tenure: hardware, operations, reliability, application development, and now AI-enabled delivery.

My current team built and runs the platform that tracks more than $7 billion in philanthropic funding, carrying the controls and reporting the Community Reinvestment Act requires. Regulated software where the numbers have to be right, not approximately right.

The work I am proudest of is not only what shipped. It is the automation that took manual intervention out of an incident path, the standards that let teams adopt AI tooling without the firm inheriting risk nobody scoped, and the engineers who can now do both without me.

The record

$7B+2024-now
Philanthropic funding tracked by a platform my current team built and operates, under Community Reinvestment Act reporting requirements.
$21M2016-2024
Estimated annual savings from automation that reduced ATM downtime across the branch network.
99.99%2016-2024
Uptime on critical services, supported by SRE automation my teams built and operated.
40%2016-2024
Reduction in manual intervention across operational workflows, through engineering rather than added headcount.
25%2016-2024
Faster incident resolution, from tooling that made response consistent instead of heroic.
15+2016-2024
Applications standardized onto one enterprise ETL framework and a shared data model.
90K+2011-2016
Endpoints across 5,800 branches covered by refresh programs I directed, on budgets from $2M to $150M.

How I lead

AI adoption is a controls problem before it is a tooling problem.

I set the standards and guardrails for AI-assisted development inside a regulated environment, so teams get the speed without the organization absorbing risk nobody scoped. Evaluating a capability honestly, including deciding not to adopt it, is part of the job.

Reliability is a product decision.

An uptime target is a commitment to the business, not an engineering vanity metric. I plan for it explicitly, staff for it, and hold the line on the operational work that keeps it true.

Modernization has to survive contact with a running bank.

Core systems cannot be paused while they are replaced. I sequence architectural change so the business keeps operating through it, and so the people doing the work know what changes next.

Capability is built, not bought.

Organizations try to purchase their way into a new technology, then wonder why adoption stalls. I train the engineers I already have: AI application development, cloud-first architecture, and secure engineering practice, taught hands-on so the team can evaluate and ship these things itself rather than depending on a vendor or a single specialist. I have led global engineering teams for more than a decade, and I plan for what they can do after I stop being in the room.

Timeline

  1. 2024now

    Senior Vice President, Lead Software Engineering Manager

    JPMorgan Chase & Co.

    Nine direct reports, 20 indirect. Together we built and now run the platform that tracks more than $7 billion in philanthropic funding and carries the reporting the Community Reinvestment Act requires. I set product direction and architectural principles, work with technology and business leadership on where the portfolio goes next, and own how this organization adopts AI into the way it builds software.

  2. 20162024

    Vice President, Lead Software Engineer

    JPMorgan Chase & Co.

    Eight years, three countries. My teams grew to around 30 engineers across the United States, India, and the Philippines, and the work was to make critical banking infrastructure boring: fewer manual touches, predictable behavior, faster recovery when something did break anyway. The enterprise ETL framework, the SRE automation behind four nines, and the incident tooling all came out of this stretch.

  3. 20112016

    Assistant Vice President, Technical Operations Manager

    JPMorgan Chase & Co.

    Where I learned scale. Thirty-five indirect reports around the world, 5,800 branches that had to stay open, and refresh programs moving through 90,000 endpoints on budgets between $2M and $150M. Mostly it taught me process: at that size nothing survives if it depends on a person remembering to do it.

  4. 20102011

    Technical Operations Analyst

    JPMorgan Chase & Co.

    The year I stopped thinking about individual machines and started thinking about the estate as one system.

  5. 20042010

    Lead Technical Support Analyst, Field Service Engineer

    Insight, on contract to JPMorgan Chase

    Onsite and remote support across the branch estate. I wrote the first automations of my career here, for the least noble reason available: I was tired of fixing the same failure twice.

MBA, Ohio University. BS in Computer Information Systems, DeVry University.

Still close to the work

I am a working leader, not a manager who left the tools behind. A normal week spans people management, data architecture, strategic planning, and delivering code alongside the team. That is deliberate: a leader who cannot evaluate a technology has no business governing its adoption. Outside of work I run my own infrastructure end to end and build on the same stack my teams use.

  • LLM and RAG systems
  • Agentic AI tooling
  • TypeScript, Next.js
  • SQL and data modeling
  • Self-hosted networking
  • Cloudflare, CI/CD

Get in touch

If you are hiring for a director-level engineering role that can be done remotely, I would like to hear about it. Email is fastest.