Experience· JPMorganChase

From implementation engineering to Automation CoE leadership

JPMorganChase · April 2013 - April 2018. Five years of growing ownership across enterprise implementation, live production operations and automation strategy.

Implementation engineering L2/L3 production support Automation CoE leadership 50% less regression effort
← Back to experienceDiscuss this journey

Three chapters, one progression

Choose a chapter to see the engineering work behind the title.

Implementation Engineer

Apr 2013 - Dec 2013

Provisioned Oracle environments, migrated client data and configured enterprise SaaS implementations for production.
Oracle + PL/SQLClient onboardingIntegrations
Read the implementation chapter →

L2/L3 Production Support Engineer

Jan 2014 - Dec 2014

Investigated live application, database and integration issues in a distributed 24×7 support model.
P1 / S1 incidentsITSM changeRoot cause
Read the production chapter →

Automation CoE Lead

Jan 2015 - Apr 2018

Built reusable automation capability across business units: architecture, standards, training, execution and ROI.
4 direct reports50%+ reuseFramework strategy
Read the automation chapter →

The foundation for a systems-level approach

Each stage added another layer of ownership.

Implementation taught me how the product was built. Production support taught me how it behaved when real users depended on it. The Automation CoE gave me the opportunity to turn that context into reusable engineering capability across projects.

Understand the system → understand the operational risk → build reusable engineering solutions → measure the business impact.

50%+ increase in automation reuse50% reduction in regression effortEnterprise financial applications

What JPMorgan added to my engineering approach

My JPMorgan experience connected database and application understanding, production ownership, automation architecture and organizational influence. It is the origin story of the Staff/Architect profile I bring to quality engineering today.

Automation is not simply about writing automated tests. Done well, it reduces operational risk, improves delivery speed, increases reuse and makes quality more scalable.

Contact me