Puvio
Staff Software Engineer · ex-Robinhood · Austin. Nine portal applications, zero humans. One note to the right name changed that.
Before Puvio
James Park spent four years at Robinhood on ledger and payments infrastructure — Staff-level scope, on-call rotation, two launches that cut settlement failures measurably. He is not bad at interviews. He could not get one.
In February he applied to nine companies through Greenhouse and Workday. Nine confirmations. Not one email from someone who owned the requisition. Recruiters later told him off the record: the queue was hundreds deep before a human opened it.
He knew ATS keyword filters were part of it. The bigger gap was simpler: he never knew who to talk to before he became row #312.
Stripe platform role
He pasted a Stripe Platform Engineering Staff role into Puvio on a Tuesday morning. Company research on the same card pulled an eng blog on ledger migration — detail not repeated in the JD.
Contacts loaded ranked. First name: engineering director whose title matched the team on the posting. Second: recruiter on the req. Third: Robinhood alum now at Stripe — surfaced automatically.
Eight seconds from paste to knowing who owned the headcount. He did not open seventeen LinkedIn tabs or guess from org charts.
One note
The draft led with the migration post — specific, recent, easy to verify. One line from his Mirror profile tied his Robinhood ledger cutover to their problem framing. He sent Wednesday morning.
Friday afternoon the director replied: “Happy to chat next week.” No referral code. No insider. He still submitted through the Stripe portal afterward — compliance — but the calendar invite came from the note.
“Greenhouse told me they received it. It never told me who owned it.”
James was always qualified for the interview. He was not qualified to guess who owned the req — until the name was on the card.