Fractional Fullstack Product Engineer

Other Jobs To Apply

No other job posts for this day.

<h2>Location</h2> <p>United Kingdom</p> <h2>Employment Type</h2> <p>Contract</p> <h2>Location Type</h2> <p>Remote</p> <h2>Department</h2> <p>Product</p> <h2>Deadline to Apply</h2> <p>March 27, 2026 at 1:00 PM EDT</p> <h1>About the Role</h1> <p>The project involves building the core of a platform with a 10-step coaching flow for founders, integrating AI-generated pitches and strategic planning. You will work on a clean codebase with solid foundations already in place.</p> <h1>What you’d work on</h1> <ul> <li><p><strong>LLM integration pipeline</strong> — building the routing layer that connects the platform to frontier models (OpenAI, Anthropic) via Vercel AI SDK, with streaming responses, cost tracking, and governance</p> </li> <li><p><strong>Core coaching flow</strong> — implementing the step-by-step journey where founders provide input, receive AI-generated pitches, face explicit challenges, and make binding strategic decisions</p> </li> <li><p><strong>Database modelling and state management</strong> — translating domain concepts into a normalised PostgreSQL schema that encodes business rules and enforces sequencing</p> </li> </ul> <p>You’d take ownership of discrete chunks of work end-to-end. There are requirements from the product and business, but you have genuine creative freedom in how you implement them.</p> <h1>The stack</h1> <ul> <li><p><strong>React Router v7</strong> (Remix lineage) with TypeScript</p> </li> <li><p><strong>PostgreSQL</strong> with Drizzle ORM</p> </li> <li><p><strong>Tailwind CSS</strong> with shadcn/ui components</p> </li> <li><p><strong>Vercel AI SDK</strong> for LLM integration (OpenAI, Anthropic)</p> </li> <li><p><strong>BetterAuth</strong> for authentication</p> </li> <li><p><strong>GitHub</strong> with linear history, commit signing, and CI/CD via GitHub Actions, deploying to <strong>Render</strong></p> </li> <li><p><strong>Sentry</strong> with OpenTelemetry for monitoring</p> </li> <li><p><strong>Vitest</strong> and <strong>Playwright</strong> for testing</p> </li> <li><p><strong>pnpm workspaces</strong> for monorepo structure</p> </li> <li><p><strong>Devenv/Nix</strong> for development environment (Docker available as alternative)</p> </li> </ul> <h1>Hard requirements</h1> <p>These are non-negotiable. If you don’t meet them, we won't be able to consider your application.</p> <ul> <li><p><strong>Production experience with PostgreSQL.</strong> 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).</p> </li> <li><p><strong>Production experience with React and server-side rendering patterns.</strong> You must understand SSR and data loading patterns, and be ready to work with loaders and actions from day one.</p> </li> <li><p><strong>Strong TypeScript skills.</strong> You should be comfortable with discriminated unions, generics, and using the type system to prevent bugs rather than just satisfying the compiler.</p> </li> <li><p><strong>API integration experience.</strong> You’ll be building the LLM routing layer that integrates with multiple providers.</p> </li> <li><p><strong>Exceptional English, written and spoken.</strong> Clear communication is essential for remote collaboration.</p> </li> <li><p><strong>Discerning use of language models.</strong> You need enough production experience to know when a model is producing unmaintainable code and impose the right guardrails.</p> </li> </ul> <h2><strong>Nice to have</strong></h2> <ul> <li><p>Experience with LLM integration, streaming responses, or AI product development</p> </li> <li><p>Familiarity with observability and governance patterns (OpenTelemetry, structured logging)</p> </li> <li><p>Experience with Drizzle ORM or similar TypeScript ORMs</p> </li> <li><p>Familiarity with state machine patterns or domain-driven design</p> </li> </ul> <h1>How we work</h1> <p>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.</p> <p>A few principles we take seriously:</p> <ul> <li><p><strong>Transparency by default.</strong> Project communication happens in shared channels.</p> </li> <li><p><strong>Small leaps, committed landings.</strong> Scope is agreed and designs understood before implementation.</p> </li> <li><p><strong>Ownership, not delegation.</strong> Each piece of work has a single owner who drives it to completion.</p> </li> <li><p><strong>Over-communication.</strong> Async progress updates replace stand-up meetings.</p> </li> <li><p><strong>Considerate coding.</strong> We think about the impact of our actions on the rest of the team.</p> </li> <li><p><strong>Productivity over presence.</strong> We care about what you ship, not when you’re online.</p> </li> <li><p><strong>Treat your process like your product.</strong> We ship a version of how we work, get feedback, and iterate.</p> </li> </ul> <h1>The team</h1> <ul> <li><p><strong>Matt</strong> — Founder, product lead.</p> </li> <li><p><strong>Mike Harris</strong> — Founder.</p> </li> <li><p><strong>Tariq</strong> — Founder.</p> </li> <li><p><strong>James</strong> — Fractional CTO.</p> </li> <li><p><strong>Laura</strong> — UX/Product Designer.</p> </li> <li><p><strong>Christa</strong> — Developer.</p> </li> </ul> <h1>Engagement details</h1> <ol> <li><p><strong>Start:</strong> Early to mid-March 2026</p> </li> <li><p><strong>Duration:</strong> Through to July initially, with strong potential to continue</p> </li> <li><p><strong>Commitment:</strong> 3–5 days per week (flexible based on fit)</p> </li> <li><p><strong>Location:</strong> UK based, or Europe with exceptional English and significant UK hours overlap</p> </li> <li><p><strong>Rate:</strong> Depends on experience and location</p> </li> <li><p><strong>Contract:</strong> Direct with IconicShift (no intermediaries)</p> </li> </ol> <h1>Interview process</h1> <ol> <li><p>Initial screening based on your application</p> </li> <li><p>90-minute live pairing session with the CTO.</p> </li> <li><p>Founder call.</p> </li> <li><p>Offer.</p> </li> </ol>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...