Technical Product Manager / Remote · Open to US time zones
Hi, I'm Kayleigh. I spent nearly six years as a software engineer at Accenture, building for enterprise clients. I learned how software gets built. Now I focus on deciding what gets built, and why.
01The engineering edge
I've built the systems I'll be prioritizing. I can read a sequence diagram, question an API contract, and spot the hidden migration inside a “small” feature.
Six years of estimating my own tickets means I write requirements engineers trust — and timelines that survive contact with reality.
I know what a vague ticket costs a team. My specs come with edge cases, acceptance criteria, and the “why” already answered.
Accenture taught me to align executives, client stakeholders, and delivery teams who all want different things — and to stay calm when priorities shift.
02Selected work
Enterprise engagements told from the product side: the problem, the trade-offs, and what changed as a result. Clients are anonymized.
01
Workflow Digitization
Operations staff were processing shared task updates through email threads and shared spreadsheets. I helped turn a fragile manual process into a tracked, self-serve workflow — starting with the people doing the work.
02
Platform Product
Multiple teams on the same client program were rebuilding the same buttons, tables, and forms — each slightly different. I helped treat our internal UI library as a product, with engineers as its customers.
03
Support & Documentation
Our team was spending 35% of every sprint on the same handful of support escalations. I used ticket data to separate “needs a runbook” from “needs a product fix” — and drove both.
03Writing sample
A complete concept PRD covering the problem, goals and non-goals, personas, prioritized requirements, edge cases, success metrics, and rollout. It's the document I'd hand an engineering team on day one.
Read the full PRD →PRD · Concept · writing sample
Self-serve API key rotation
Letting developers rotate credentials safely — without a support ticket or an outage.
Goal
Zero-downtime rotation
Priority
P0 · 5 reqs
Target
< 1% of tickets
04Toolkit
05About
For nearly six years at Accenture, I shipped software for enterprise clients across developer tooling, cloud infrastructure, and enterprise SaaS. I wrote the code, and the projects I remember best were the ones where I got to shape it: sitting with users, untangling requirements, and helping a room full of stakeholders agree on what mattered most.
I gradually became the engineer who wrote the specs, ran the demos, translated between the client and the team, and turned support tickets into roadmap items. Product management is where that work becomes the whole job.
The best requirement is one an engineer reads once and never has to ask about.
I work best on remote, async-first teams that value clear writing: PRDs, decision records, runbooks, and documentation people actually read. I'm especially drawn to developer platforms, internal tools, and enterprise SaaS.
06Contact
I'm open to remote Technical Product Manager roles. The fastest way to reach me is email.