Fullstack Product Engineer

• These are non-negotiable. If you don’t meet them, we won't be able to consider your application. • Production experience with PostgreSQL. You need to understand normalised schema design, foreign keys, indexes, migrations, and the trade-offs between different approaches (e.g. UUIDs vs serials as primary keys). If you’re primarily a MongoDB or Firebase developer, this isn’t the right role. • Production experience with React and server-side rendering patterns. We use React Router v7 (Remix lineage) with loaders, actions, and nested routing. You don’t need prior React Router v7 experience specifically, but you must understand SSR and data loading patterns, and be ready to work with loaders and actions from day one. If your instinct is to add REST API endpoints alongside the framework, this isn’t the right role. • Production experience with React and server-side rendering patterns. • Strong TypeScript skills. We avoid stringly-typed code. Types are documentation. You should be comfortable with discriminated unions, generics, and using the type system to prevent bugs rather than just satisfying the compiler. • API integration experience. You’ll be building the LLM routing layer that integrates with multiple providers. You need solid experience designing and consuming APIs, handling streaming responses, managing error states, and architecting systems with clear separation of concerns. • Exceptional English, written and spoken. This is a remote team doing complex technical work. Written communication is how we coordinate — your commit messages, PR descriptions, and Slack messages need to be clear, precise, and professional. We also work through video calls discussing technical architecture, and you need to be able to communicate complex ideas clearly in conversation. Regional accents are welcome; clarity is essential. • Exceptional English, written and spoken. • Discerning use of language models. We have company Anthropic and OpenAI accounts, Claude Code, and skills that encode our processes — from landing pull requests to scaffolding from Figma designs. We're a small team with ambitious goals, and LLMs are a key enabler for doing more with less. But we need someone with enough production experience to know when a model is producing unmaintainable code, impose the right guardrails, and distinguish a plausible answer from a correct one. The tool is powerful; we want someone with the judgement to wield it well. • Discerning use of language models. • Experience with LLM integration, streaming responses, or AI product development • Familiarity with observability and governance patterns (OpenTelemetry, structured logging) • Experience with Drizzle ORM or similar TypeScript ORMs • Familiarity with state machine patterns or domain-driven design • How we work • Fully remote. We communicate via Slack and video calls. Design work lives in Figma. All work is tracked in Linear. Code goes through GitHub with full CI/CD — land a pull request and it’s live on Render. • We embrace the heart of Agile — collaborate, deliver, reflect, improve — without the ceremony. No planning poker. No two-week rituals for the sake of it. We size work relative to previously delivered tasks and forecast based on measured velocity. Lightweight process that actually helps rather than getting in the way. • A few principles we take seriously: • Transparency by default. Project communication happens in shared channels. When we onboard someone new, they should be able to read back through the channels and get up to speed without anyone replaying conversations. • Transparency by default. • Small leaps, committed landings. When we commit to a piece of work, the scope is agreed and the designs are understood. While you’re implementing, the target doesn’t move. If something needs to change, it goes into the next batch. • Small leaps, committed landings. • Ownership, not delegation. Each piece of work has a single owner who drives it to completion. That means talking to Matt about requirements, Laura about design, James about technical approach. We don’t want everything routing through a single bottleneck. • Ownership, not delegation. • Over-communication. We pride ourselves on making sure everyone has the context they need. Async progress updates (progress, problems, priorities) replace stand-up meetings. If you’re blocked, say so early. If you disagree with an approach, raise it. If you spot a better way, suggest it. • Over-communication. • Considerate coding. We think about the impact of our actions on the rest of the team. We have database triggers that set updated_at timestamps automatically, and tests that check every table with an updated_at column has the trigger present. We recognise we’re fallible and use the tools available to prevent mistakes — for ourselves and for each other. • Considerate coding. • Productivity over presence. We care about what you ship, not when you’re online. Flexible hours, asynchronous by default, with enough overlap for meaningful collaboration during UK working hours. • Productivity over presence. • Treat your process like your product. We ship a version of how we work, get feedback, and iterate. Retrospectives are lightweight but genuine. If something isn’t working, we change it. • Treat your process like your product. • We’ve built skills and automation into our workflow using language models. When you want to land a pull request, there’s a skill for that. When you start work on a Figma design, there’s a skill for that. When you’re being onboarded, there’s a skill that walks you through getting your environment set up correctly. We use LLMs to encode our processes and accelerate ourselves — not just for writing code. • Our most recent developer shipped to production in her first week. We’d expect the same from you. • The team • Matt — Founder, product lead. Owns the coaching methodology and product vision. • Mike Harris — Founder. The methodology and strategic experience behind the platform. • Mike Harris • Tariq — Founder. • Tariq • James — Fractional CTO. Architecture, technical leadership, code review, day-to-day collaboration. You’d work closely with James. • James • Laura — UX/Product Designer. Owns the user journeys and interaction design in Figma. • Laura • Christa — Developer. Working on feature implementation. • Christa • This probably isn’t for you if… • You’re an agency or recruiter • You rotate staff on and off projects • You need detailed specifications for every task • You can’t overlap significantly with UK working hours • Engagement details • Start: Early to mid-March 2026 • Start: • Duration: Through to July initially, with strong potential to continue • Duration: • Commitment: 3–5 days per week (flexible based on fit) • Commitment: • Location: UK based, or Europe with exceptional English and significant UK hours overlap • Location: • Rate: Depends on experience and location • Rate: • Contract: Direct with IconicShift (no intermediaries) • Contract: