Engineering leader at Bank of America. I own Phoenix — the bank's internal Angular design system, CLI and form platform — backing 50 applications, with a 24-person team and a $3–4M budget I negotiate at the executive table. Sixteen years of frontend depth, from payment screens to the framework itself.
Frontend platform architect at Bank of America. I designed Phoenix — the bank's internal Angular component library, CLI, Loom form engine and design system — from its first reusable components in 2016 to a platform behind 50 applications and 300+ developers. Still hands-on: I built Loom's prototype and the context layer that makes Copilot accurate against Phoenix's APIs.
I do both jobs. Pick the view that fits why you're here.
24
Person team, 10 direct reports
$3–4M
Annual budget owned
30
Delivery teams migrated
100K→40K
Vulnerability findings cut
80%
Smaller bundles, per-component entry points
1 wk
Per upgrade, down from 3 months
300+
Developers building on Phoenix
200+
Payment types on Loom
The bank's internal Angular 22 component library, CLI and platform — 50 applications, 300+ developers, including CashPro Online's 30+ sub-applications. Moved 30 delivery teams off legacy stacks onto it; upgrades that took three months now land as a one-week version bump.
How work moves through itA form engine covering 200+ payment types, shipped to production in place of a legacy system. Business analysts build and publish forms themselves under maker-checker approval — nobody releases their own work.
A framework-specific instruction layer for GitHub Copilot: per-entry-point API docs, usage constraints and canonical patterns, indexed so completions resolve against Phoenix's real APIs rather than generic Angular. Plus prompt-based CLI commands for code scanning and codebase mapping.
A React-based alternative to Phoenix, launched so teams already fluent in React could onboard to the platform without retraining — same enterprise UX standards, security posture and delivery pipeline, a second framework door into the ecosystem.
A JSON-driven form authoring and rendering platform. I built the original prototype and carried it to production, replacing a legacy engine across 200+ payment types. Business analysts build forms in four stages — Layout, Config, Weave (rules between fields) and Preview — and the Loom renderer turns the saved JSON into the live form.
Per-component secondary entry points that cut bundle sizes by 80%. Micro-frontends on @angular/elements, so teams ship features as self-contained custom elements. Core logic split from presentation, with UI and mobile wrappers sharing one API, so apps get native mobile components without a rewrite.
How work moves through itEach major Phoenix release ships 4–5 version-specific Angular schematics that apply its breaking changes, and Angular's, through ng update. 30 teams reached Angular 22 this way, including the move to the esbuild application builder with Vite as the dev server. Upgrades that took three months now take about a week.
A framework-specific instruction layer for GitHub Copilot: per-entry-point API docs, usage constraints and canonical patterns, indexed so completions resolve against Phoenix's real APIs rather than generic Angular. Plus prompt-based CLI commands for code scanning and codebase mapping.
What owning a platform that 300+ developers depend on involves, day to day.
24 people across onshore and offshore: 15 engineers, 3 QA and 6 UX designers, with 10 reporting directly to me. I moved from engineer to manager in 2022.
Hired 4, promoted 3, nobody has left.
Took over Phoenix's $3–4M annual budget in 2025 and negotiate it directly with peer executives, alongside the roadmap and release plan for all three platform products.
A central intake pipeline for 300+ developers. UX and UI requests, enhancements and defects all come in one way and are prioritized in one place.
Bugs carry a two-week SLA.
Accountable for security posture and compliance across the platform, held to the bank's Global Information Security standards. Consolidating the portfolio onto one supported version did most of the work.
Open-source vulnerability findings down from 100K to 40K.
Hesitant app teams moved once upgrades stopped being projects. Tech-feasibility sessions during design catch non-standard component usage before it gets built.
30 delivery teams migrated onto Phoenix v8 and Angular 22.
Copilot instructions tuned to Phoenix, plus prompt-based CLI commands for code scanning and codebase mapping, available to every developer on the platform.
The calls that shaped Phoenix, and what each one changed for the teams building on it.
Restructured Phoenix 6 with ng-packagr so each component ships as a secondary entry point. Applications import and bundle only the components they use.
80% smaller bundles.
Every major release carries 4–5 version-specific Angular schematics that apply Phoenix's breaking changes, and those of the underlying Angular version, through ng update.
Three-month migrations became one-week version bumps.
Features ship as self-contained custom elements, so teams build and release them independently and compose them into host applications.
Component logic sits in a core layer, with separate UI and mobile wrappers on top; the mobile variants publish as a tertiary entry point. I built the foundation and guided the team extending it across the library.
One API, so apps get native mobile components without a rewrite.
Loom's authoring stages — Layout, Config, Weave and Preview — produce a plain JSON definition, and one renderer turns it into the live form. Publishing goes through maker-checker approval.
200+ payment types, built by business analysts without code.
Per-entry-point API docs, usage constraints and canonical patterns, indexed so Copilot resolves completions against Phoenix's real APIs instead of generic Angular.
Own Phoenix end to end: 24-person onshore/offshore team, $3–4M budget, security posture, roadmap and releases across all three platform products. Hired 4 engineers, promoted 3, zero attrition.
Own architecture and technical direction for Phoenix: component library, CLI, the Loom form engine and design system. Built Loom from prototype to production, designed the micro-frontend and mobile-native layers, and rebuilt the CLI on oclif.
Set Phoenix strategy for its next major release. Launched Griffin, a React-based alternative, and extended the framework for accessibility and mobile.
Set the technical strategy for Phoenix v7. Re-architected upgrades around version-specific Angular schematics, launched Griffin as a React counterpart, and extended the library for accessibility.
Led the Phoenix framework team; set the upgrade and migration path for every application built on it. Built Docsmot.
Technical lead for Phoenix. Cut bundle sizes by 80% by giving every component its own entry point, and built Docsmot, a canvas editor that generates Angular code.
Built the reusable Angular component library that became Phoenix; published it to a private internal npm registry for delivery teams.
Built payment types for a global payments hub — Financial-i Innovation of the Year, 2011. Core contributor to the Dynamic Payment Generator; Infosys Dynamo Award.
Angular 22, Signal store, framework authorship, migration strategy, code generation, LLM support
TypeScript, JavaScript, Angular 22+, React 18+, HTML5, CSS3, SASS, Bootstrap
Copilot custom instruction sets, workspace indexing, LLM context design for proprietary codebases, prompt-based CLI tooling
Vitest, Playwright, WCAG 2.2 AA, Section 508, CI/CD automation
Node.js, npm, Webpack, Git, GitHub, GitHub Copilot, Figma
Java, Spring MVC, REST, Oracle, OpenShift, Splunk, SDLC governance
Angular 22, Signals & Signal Store, schematics, @angular/elements micro-frontends, framework authorship, migration strategy
Component-library packaging & versioning (ng-packagr, secondary entry points), private npm registries, Node.js, npm, Vite, esbuild, Webpack, CLI tooling (oclif), project scaffolding, Git, GitHub, Figma
Copilot custom instruction sets, workspace indexing, LLM context design for proprietary codebases, prompt-based CLI tooling
TypeScript, JavaScript, React 18+, HTML5, CSS3, SASS
Vitest, Playwright (Phoenix held at 90% test coverage), WCAG 2.2 AA, Section 508, CI/CD automation
Java, Spring MVC, REST, Oracle, OpenShift, Splunk, SDLC governance
Minneapolis, MN · open to engineering leadership conversations.