I'm a Senior Product Manager with 7+ years building platform infrastructure, fintech products, and e-commerce systems — with a background in data analysis and project management that means I was working in the details long before I had the title.
At Ally Financial, I've led platform modernization across the digital product org — owning roadmaps for API integrations, a migration to React/Next.js, and a headless CMS adoption that modernized how millions of customers interact with financial products online. I also led the 0-to-1 build of the consumer content platform — taking it from a disconnected WordPress blog into a full editorial destination on AEM, then serving as the strategic lead for its evolution onto our new React/Next.js headless stack, making it the first property in the org to complete that migration.
At Lowe's, I led the migration of 250+ e-commerce pages off a platform that had failed during Black Friday — rebuilding on a headless CMS and Google Cloud architecture that improved mobile performance, SEO, and conversion.
I'm the team's translator — I turn complex technical and organizational challenges into clear product decisions and break down that work into language stakeholders can act on. I thrive tackling initiatives that are technically demanding, cross-functionally messy, and high-stakes enough that most PMs step back. That's where I do my best work — and where I help teams avoid the headaches that come from getting those tradeoffs wrong.
Where I've worked:
- 🏗️ Platform / Infrastructure — APIs, headless CMS migrations, cloud-native architecture, and systems that other teams depend on
- 💳 Fintech — navigated regulatory constraints, compliance requirements, and the nuance of building trust in financial products
- 🛍️ E-Commerce — shipped features at scale with a focus on performance, SEO, and conversion
These projects demonstrate how I approach real PM challenges — from system design to data analysis to product strategy.
| Project | Description | Domain |
|---|---|---|
| 🗂️ PRD: Enterprise CMS Platform Migration | End-to-end product requirements for migrating a 500+ page FinTech web platform from a legacy monolithic CMS to a modern composable stack — covering architecture, OKRs, personas, risks, and success metrics | Platform / Fintech |
| 🗂️ PRD: E-Commerce CMS Platform Migration | Product requirements for migrating a large home improvement retailer's 250+ page e-commerce web presence from Adobe Experience Manager to an in-house headless CMS on Google Cloud — covering SEO restructuring, mobile performance, on-prem to cloud infrastructure, and cross-functional stakeholder alignment | Platform / E-Commerce |
| 🧪 A/B Test: AI-Generated Blog Post Summarization | Full experiment design, results, and decision rationale for a 5-week A/B test evaluating an AI summarization CTA feature on long-form FinTech blog content — including inconclusive results analysis and a data-informed ship decision | Fintech / AI |
| 📊 CMS Migration Scoring Model | Data-driven Excel scoring model used to prioritize the migration sequence of 500+ pages across 8 weighted dimensions — built collaboratively with product, UX, engineering, and analytics stakeholders to replace ad hoc prioritization with a transparent, objective framework | Platform / Fintech |
| 🔌 API Spec: Apigee Proxy — Marketo REST API | Technical API specification for an Apigee proxy layer abstracting Marketo REST API credentials from consumers — covering SSO auth enforcement, OAuth 2.0 token lifecycle management, request transformation, field mapping, rate limiting, and error normalization | Platform / Fintech |
| 🗂️ PRD: FinTech Consumer Content Hub | Product requirements for the MVP launch of a consumer financial content hub migrated from a disconnected WordPress blog into AEM — covering content model, taxonomy, SEO, accessibility, tagging, feature prioritization, content migration strategy, and a phased roadmap through engagement, personalization, and delight | Consumer / Fintech |
| 🏛️ System Design: FinTech Consumer Content Hub | AEM component architecture for a FinTech consumer content hub — covering author/publish/delivery tier design, component library, content model, JCR taxonomy, authoring pipeline, Dispatcher caching strategy, search and analytics integration, and a phased future state evolution through personalization and authenticated experiences | Consumer / Fintech |
| 🗂️ PRD: Visual Stories | Feature PRD for Visual Stories — a short-form, mobile-optimized content format for a FinTech consumer content hub. Phase 4 of the content hub roadmap, covering Editorial and Merchandising story types, AEM content model, CTA pathing logic, navigation constraints, and a phased future state through motion graphics, polls, and native app | Consumer / Fintech |
| 🗂️ PRD: Email & SMS Signup Toast | Feature PRD for the first native email and SMS subscriber acquisition mechanism on a large e-commerce platform — a first-visit toast with DIY/Pro segmentation, mobile SMS variant, cookie-based suppression, and A/B test validation — replacing offline and third-party acquisition with an owned digital channel | E-Commerce |
| 🗂️ Installation Services Lead Capture Widget (CAAS) | PRD, system design, and API spec for a configurable stepped-form widget consolidating 40+ installation service forms across 7 categories — CAAS-driven service type determination, Microsoft Dynamics lead consolidation, dual standalone and embedded modes, and a self-service config dashboard for the business unit. Discovery complete; deprioritized ahead of platform migration | E-Commerce |
More projects added regularly — check back or ⭐ star this repo to follow along.
Working prototypes built independently using AI-assisted coding — no engineering sprint required. Demonstrates how I use AI to close the gap between product specification and testable software.
| Project | Description | Domain |
|---|---|---|
| ⚙️ POC: CaaS Install Widget | Working React prototype of a configurable installation services lead capture widget — built independently with AI assistance over ~2 days to validate the adaptive flow, service type logic, and API feasibility defined in the PRD and system design. Closes the loop between product specification and a runnable artifact without an engineering sprint. | Platform / E-Commerce |
| Discovery → | Define → | Deliver → | Measure |
|---|---|---|---|
| User research | PRDs | Sprint planning | Dashboards |
| Competitive anal. | Tech specs | Eng. partnership | Experimentation |
| Opportunity sizing | API contracts | Stakeholder mgmt | Retrospectives |
Stack fluency: React · Next.js · Headless CMS · AEM · REST APIs · SQL · Apigee · Kong Gateway · Adobe Analytics · Figma · JIRA · Confluence · Qualtrics · TypeScript
I can hold my own with: PowerBI · DAX · Tableau · System architecture · API contract design · Basic data modeling
Domains: Platform / Infrastructure · FinTech · E-Commerce · Consumer
I'm actively looking for Senior PM and Principal PM roles — Seattle-based or remote. I'm especially drawn to platform, infrastructure, and fintech teams where technical depth is a real advantage, not just a nice-to-have.
📄 Resume (PDF) 💼 LinkedIn 📧 thomas-edmons@outlook.com
This portfolio is a living document. I build in public and update it as I work through new problems.