The company and the job
Halden makes payments software for small businesses: card payments, invoices and payouts in one app. The payments team owns checkout and the first payment a new customer makes.
The job: A senior product role in payments. Expect technical questions on metrics, risk and trade-offs.
They want: Payments, Experimentation, Fraud and risk, Stakeholders, SQL, Roadmaps
- Why you: At Fernway you fixed the first payment step and took completion from 41% to 58%. That is the problem this team works on.
- Why you: You grew checkout conversion by 17% at Brightpay, for customers much like Halden’s.
Your best answers
I paused a quarter’s roadmap halfway through, because the data showed we were fixing the wrong problem. I was leading onboarding at Fernway, and we were two months into a redesign when support flagged that new users weren’t leaving during onboarding. …
If pay comes up
Practise “Talking about pay” and your best answer appears here.
This is the stage to be specific. Ask about every part of the package before you say yes.
Which story for which question
- Pausing onboarding to fix payments (Fernway, 2023)For: Changing the roadmap; A payments metric drops
- Disagreeing with engineering on fraud rules (Fernway, 2023)For: Disagreeing with an engineer; Build or buy fraud detection
- Growing checkout conversion by 17% (Brightpay, 2021)For: Growing conversion 17%; Measuring a payment flow
- Moving from design into product (Brightpay, 2021)For: Design to product
They’re likely to probe
- Eight months at Fernway before moving onLead with what you delivered there, then why the next move made sense. Two sentences, no apology.
- Switching from design to product in 2021Frame it as a step towards owning outcomes, with the Brightpay conversion work as the proof.
Questions to ask them
- When growth and fraud risk pull in different directions, how does the payments team decide?
- What would a great first six months look like in this role?
- How do product and engineering share decisions on the payments roadmap?
Three things to remember
- 1Answer first: your decision or result in the first sentence.
- 2Say “I” for your part. Keep “we” for the team’s.
- 3Keep to time: one sentence of background is enough.