About
About Me
I'm a Senior Technical Product Manager with 10+ years of experience building and scaling platforms in regulated industries — healthcare, fintech, and telecom. My path into product management started in software engineering — I hold a BS in Computer Science from Stephen F. Austin State University — and that technical foundation has shaped everything about how I work. I understand systems, I understand developers, and I know how to translate complex technical realities into product strategies that actually ship.
My career has spanned startups and enterprises, and the thread running through all of it is platform scale and technical complexity. I've built products that held up under extraordinary pressure — from a COVID-19 results platform serving 15M+ patients on behalf of Walgreens, to a data platform consolidating hundreds of millions of mortgage loan records, to integrations infrastructure spanning 250+ partners in a regulated healthcare environment.
I've led teams, launched 0→1 products, driven API standardization across enterprise ecosystems, and embedded AI into engineering workflows to measurably improve delivery velocity. I care deeply about developer experience, platform reliability, and building products that hold up under real-world pressure.
Right now, I'm embedded with Waymo's Requirements Process and Tools team (via Appko) as a Technical Program Manager and Senior Lead Jira Administrator, engineering the Atlassian environment behind Waymo's org-wide testing requirements process.
Outside of work
I was born in Houston and went to school at Stephen F. Austin State University. I've called Austin home since 2014, aside from 2018–2021 in New York — including the height of the pandemic, when I was building EverlyHealth's COVID-19 results platform from the front lines of the response. I share my place with three dogs — an Aussie, a corgi, and a pitbull puppy — and one cat, who is very much in charge.
I'm an enthusiastic board gamer — not Monopoly and Risk, but Settlers of Catan, Ticket to Ride, Food Chain Magnate, and the like. I play regularly with friends and have found the board game community through local Meetup groups, which is a genuinely good way to meet people in a city you've lived in for over a decade.
More recently, I've gone down the home lab rabbit hole. It started with running Pi-hole for network-wide ad blocking, which led to firewall rules on my Synology NAS and UniFi router, and from there into self-hosting a growing list of apps — with a reverse proxy in front of them, automated cert rotation, Tailscale for secure remote access, and automated backups of my email, photos, and Google Drive. It's the same kind of hands-on systems work that got me into engineering in the first place.
A few things I've learned
The senior PM market has been genuinely difficult.
Layoffs, hiring freezes, and a deep pool of strong candidates have made searches take far longer than they used to. It's a market reality that's affected a lot of experienced people at once — not a reflection of individual value.
When it got hard, I built tools for it.
Rather than grind through the search manually, I used Claude Code to build a small suite of job-search tooling. Three tools, in order:
- A resume and cover letter tailoring tool that customized my application materials against a given job description and whatever other context it could pull in.
- A job-search scoring engine that indexed listings from major job boards like Indeed (LinkedIn doesn't expose a public listings API, so I couldn't index it), scored each posting against my industry, title, and skills, and organized results by weighing match score against recency and applicant count.
- An end-to-end automation tool, still in beta when the search closed, that combined the two — auto-generating tailored resumes and cover letters for the listings the scoring engine surfaced, with a one-click apply path where possible.
I also tracked every application in a spreadsheet and eventually imported that data into the scoring tool for analysis — an early, still-rough attempt to see which roles and channels were actually converting. Together, the tools made a high-volume, messy problem legible and taught me a lot about the market I was competing in.
Referrals still beat applications.
Even with better tooling, my current role came through a former coworker's referral, not a job board. Tools sharpen how you compete on volume; relationships still decide outcomes.
Specificity beats length.
The resume language that actually opens doors leads with outcomes and named metrics — 15M+ patients, 90% cycle time reduction, 65% fewer redundant API calls — not generic competency statements. Numbers open doors; narratives close deals.
AI adoption is a change-management problem first.
Leading the GitHub Copilot rollout at Alma taught me that the biggest gains came where the tool fit into existing workflows — not where it asked people to change how they worked to accommodate it.