LEAD WITH
I build the unglamorous payments infrastructure that quietly moves money correctly at scale.
An About section that proves the payments-operator claim
Three opening hooks (what shows before "see more")
THE OPERATOR'S CLAIM
I build the unglamorous payments infrastructure that quietly moves money correctly at scale.
Your resume says: “auth, settlement, and reconciliation”
THE PROBLEM YOU SOLVE
Money movement breaks quietly. My job for the last eight years has been making sure it doesn't.
Your resume says: “cut auth-decline rate”
THE SURPRISING SPECIFIC
The ledger other teams build on? Someone has to design it. That's the work I love.
Your resume says: “internal ledger other teams build on”
Two complete About drafts
DRAFT 1 · DIRECT OPERATOR
I build the unglamorous payments infrastructure that quietly moves money correctly at scale.
For eight years I have owned payments surfaces end-to-end — auth, settlement, reconciliation — and the cross-functional launches that ship them. I led the roadmap that cut our auth-decline rate on the core flow, and I designed the internal ledger that settlement, treasury, and finance now build on.
The work I am best at sits where product judgment meets risk and revenue: aligning engineering, risk, legal, and GTM on one plan, and making the tradeoffs explicit instead of accidental.
I am most useful to teams whose money movement has become the bottleneck. If that is you, my inbox is open.
Evidence used
- Owned auth, settlement, and reconciliation end-to-end
- Cut auth-decline rate on the core flow
- Designed the internal ledger other teams build on
DRAFT 2 · WARM STORYTELLER
Early in my career I watched a reconciliation bug quietly misplace money for three days, and nobody could say where it went. I have been obsessed with making money movement boring ever since.
Eight years later, that obsession has a track record: I own auth, settlement, and reconciliation for a payments platform, I led the work that cut our auth-decline rate, and I designed the internal ledger our settlement and treasury teams now build on.
What I have learned is that payments is a team sport played across engineering, risk, legal, and GTM — and the product manager's job is keeping all four on one plan.
If you are building somewhere money movement matters, I would love to compare notes.
Evidence used
- Owned auth, settlement, and reconciliation
- Led the roadmap that cut auth-decline rate
- Cross-functional launches across eng, risk, legal, and GTM
Keywords woven in
payments · settlement · reconciliation · ledger · platform · cross-functional · risk · product management
Mistakes these drafts avoid
- No fluff vocabulary — "results-driven" and "passionate" never appear
- No third-person corporate bio voice — the About is a first-person surface
- No claim without a resume line behind it
Next steps
- Pick the hook that sounds like you and paste the matching draft
- Mirror the same claim in your headline so the profile reads as one voice