Whering

Join us at a pivotal moment to help maintain and evolve our B2C products used by millions, while playing a key role in building our new B2B offering from the ground up. You'll build the TypeScript/NestJS services powering our mobile app and ship full-stack features (backend through frontend) on our web products. Who You Are You're a Product Engineer first, an engineer second. Code is a tool, the goal is user value and business impact. You're backend-heavy and full-stack capable. Your home base is backend (TypeScript/NestJS), and you ship full-stack on the web (React/Next.js/similar) when the work calls for it. Angular & Vue experience is fine! You build for mobile without building the mobile app. You design APIs and services that serve mobile clients beautifully, accounting for offline, network, battery, and app-release realities and are able to partner closely with mobile engineers. You own features end-to-end. From API design and data modelling to web frontend implementation, deployment, and post-launch iteration. You're a proactive collaborator. You ask the right questions, propose solutions, and work effectively with teammates whose depth complements yours, including mobile, design, and product. You thrive in fast-paced, early-stage environments where speed, user feedback, and product-market fit drive decisions. What You Bring You have strong backend depth in TypeScript and NestJS (or comparable Node.js frameworks). You bring solid web frontend skills with React, Next.js, or similar enough to ship polished, production-quality interfaces independently. You have a working knowledge of cloud infrastructure; ideally GCP (Cloud Run, Cloud Functions, Firestore), CI/CD pipelines, and event-driven patterns (BullMQ/Redis or similar). You can ship and operate your own services. You have awareness of mobile constraints. You know what makes an API painful or delightful to consume from a mobile client, even if you don't write the mobile code yourself. You value pragmatism over purism. You make calibrated calls on architecture, scale, and tech debt based on what the product actually needs. How You Work You push back on the why, not just the how. You ask "why are we building this?" before "how do we build this?" You propose simpler alternatives when a 3-day version captures 90% of a 3-week feature's value. You're comfortable telling PMs and designers when something isn't worth building. You treat technical debt as a tool. You ship throwaway prototypes to validate hypotheses with real users. You delete what flops and re-architect what succeeds. You know when "the right way" is a luxury vs. a necessity, and can tell the difference. "Done" to you means users are using it. A merged PR isn't done. A feature is done when it's live, adopted, and the metrics prove it was worth building. You actively monitor analytics post-launch. You're a strategic partner. You sit with PMs and designers to shape what we build and what we don't. You're as comfortable in a product strategy conversation as you are in a code review. You contribute insights from user data, technical constraints, and implementation realities to inform product decisions. Must be based and have the right to work in the United Kingdom.