openashbyhqlsvp
Staff Product Engineer
Stacks
LocationLondon, Amsterdam
WorkplaceHybrid
EmploymentFullTime
Posted2026-05-21T14:53:54.447+00:00
Last observed2026-06-13 05:23:37.917944
Job idlsvp-stacks-ai:ashbyhq:a2dd73bb-7318-4440-b953-c645cd6e52d9
About Stacks Stacks is building an AI-native platform that reinvents how modern finance teams run the monthly close. The opportunity is massive: every growing company depends on accurate, timely financial data, yet most are still operating with tools and workflows built for a different era. In just two years, we’ve grown from a team of 2 to 30+ and are on a rapid trajectory towards $10m ARR. We’ve raised a $23m Series A led by Lightspeed Venture Partners https://stacks.ai/resources/stacks-raises-23-million-to-reinvent-finance-operations-with-agentic-ai, and we were recently recognised as one of Harmonic’s Hottest Startups of 2026 https://harmonic.ai/hot-25-companies/q2-2026. We’re already trusted by leading European scale-ups including Pleo, Freetrade, and Motorway. Our team is a blend of finance, product, and technical experts from top-tier companies like Uber, Plaid, Miro, Meta, Mollie, and Bunq, united by the drive to create a game-changing solution. We’re a team that is deeply customer-obsessed, plays to win, and isn’t afraid to take big, bold bets. We move fast, hold a high bar, and are committed to growing together as we scale. 🔎 About the Role Stacks is looking for a Staff Product Engineer to set the technical standard for how we build. This is not a management role. It is an individual contributor role with outsized influence, where your decisions shape architecture, unblock teams, and define what great looks like across the entire engineering organization. You will work at the intersection of complex technical problems and real customer outcomes. You will be the person others come to when the problem is hard, when the trade-off is unclear, or when the stakes are high. You will define the approach, not just execute it 🧱 What You'll Do - Own the most technically complex and highest-impact problems in the product, end to end, from architectural vision through to production reliability. - Define technical direction across the engineering team: set patterns, establish standards, and make foundational decisions that others build on for years. - Leads cross-functional technical discussions, partnering closely with product, design, and the founding team to translate ambiguous problems into elegant, scalable solutions. - Join customer calls and engage directly with finance leads and CFOs. You will bring technical depth to commercial conversations and use what you learn to sharpen what we build. - Identify and resolve systemic risks before they become production incidents. You design for failure, not around it. - Raise the bar for the whole team: through code reviews, technical mentorship, and by modelling what rigorous, thoughtful engineering looks like in practice. - Lead by example as an active contributor: not only setting technical direction, but consistently writing production code, raising the bar in code reviews, mentoring engineers, and evolving AI-native engineering workflows. Our product and technology are always evolving, so being a fast learner matters more than knowing our stack on day one. Here is what we are currently building with: Frontend: React, Next.js Backend: Node.js, Express, TypeScript, Python, Protobuf Data and Infrastructure: PostgreSQL, Redis, Google Cloud Platform, Terraform 🧩 What You Need Ownership and DRI mindset: You own problems end to end, create clarity when none exists, and take responsibility for outcomes without waiting to be told what to do next. Full stack depth with a backend focus: Strong TypeScript and Node.js fundamentals, comfortable across the stack, solid on API design, async processing, failure handling, and data modelling. Judgment under ambiguity: You make high-quality trade-offs between speed, correctness, and long-term system health. You choose simple and scalable where others over-engineer. Product and customer mindset: You think in customer problems, not tickets. You have talked to users and used what you learned to change what you built. Learning speed: You close gaps...
This page is generated from the committed OpenOpps static snapshot. Use the source posting or apply link for the employer's current canonical posting state.