skip-loans - Senior Product Engineer

• Own outcomes, not tickets. You'll take a business problem and turn it into a working, scalable system. • Ship product. We care about what's live and working, not what's in a design doc. You'll ship frequently and iterate based on real usage from our customers or team. • Make product decisions. You'll scope what to build (and what not to build), sequence work, and make trade-offs between speed, quality, and complexity. You'll talk directly to the people who use what you build • Create solid code. Our stack is React, Node, TypeScript, AWS. You'll create production code that other engineers can extend and follow - not prototypes that need to be rewritten. • Direct AI to build. We're an AI-native engineering team. You'll use agent-first workflows to ship at a pace that would be impossible manually. The bottleneck isn't implementation — it's judgment about what to build and why. • Prioritisation - While you’ll be responsible for making product decisions and moving quickly, you’ll need to work with the team to ensure your velocity is always pointed in the right direction and aligned to our commercial goals. • A curious generalist, not a narrow specialist. You cross disciplines naturally. You've done product thinking, systems design, user research, or ops problem-solving - not because it was in your job description, but because you wanted to understand the whole problem. • Product instinct. You naturally ask "should we build this?" before "how do we build this?" You can talk to a non-technical stakeholder, understand their pain, and translate it into the right technical solution. • End-to-end ownership. You've shipped features or systems where you were the person responsible for the outcome — from problem definition through to production and iteration. You've built a tonne from scratch, not just inherited and extended. • Strong technical fundamentals. You write clean, maintainable code, understand systems design, and make pragmatic architecture decisions. • Comfort with ambiguity. We're a small team at a growth-stage fintech. Requirements are often fuzzy. You're energised by that, not paralysed. • Clear communication. You write well. You can explain a technical trade-off to a founder and a product decision to an engineer. • You're in it for the love of the game - you love building. You are a technical builder who loves solving problems, if “software engineering” to you is just a “good job” - this probably isn’t the shop for you.