Senior Product Engineer

About The Role
We're hiring builders - curious, technical generalists who think across disciplines and can take something from idea to shipped product.
There's no handoff here between "product" and "engineering." You'll talk directly to ops, sales and product to understand the real business problem, then build it, ship it, and iterate. Nobody hands you a spec — you write the spec and the code, directing AI to handle the implementation by default.
Key Responsibilities
Own outcomes, not tickets - turn business problems into working, scalable systems
Ship product, not design docs - release frequently and iterate on real usage
Make the product calls - scope what to build (and what not to), sequence work, and balance speed, quality and complexity, working directly with the people who use what you ship
Write code that lasts - stack is React, TypeScript, Python and AWS; production-grade code other engineers can build on, not throwaway prototypes
Direct AI to build - this is an AI-native engineering team, using agent-first workflows to ship at a pace that isn't possible manually; the bottleneck is judgement, not implementation
Prioritise with the team - you'll move fast and own product decisions, while working with the team to keep that speed pointed at the right commercial goals
What You'll Bring
A genuine generalist, not a narrow specialist - you move naturally across product thinking, systems design, user research and ops, because you wanted to understand the whole problem
Strong product instinct - you ask "should we build this?" before "how do we build this?", and can turn a non-technical stakeholder's pain point into the right technical solution
End-to-end ownership - you've shipped features or systems you were fully responsible for, from problem definition through to production and iteration, building plenty from scratch
Strong technical fundamentals - clean, maintainable code, solid systems design, pragmatic architecture decisions
Comfort with ambiguity - this is a small team at a growth-stage fintech, requirements are often fuzzy, and that energises rather than stalls you
Clear communicator - you write well, and can explain a technical trade-off to a founder as easily as a product decision to an engineer

Work arrangement
Yes