Product Engineer

Kyra is an enterprise influencer marketing platform working with brands like SharkNinja, Coach, H&M, Ray-Ban, and Converse. Our platform manages the full lifecycle — creator discovery, campaign management, content review, payments, analytics, and AI-powered intelligence across TikTok, Instagram, and YouTube.

At Kyra, we build software differently. Our product team uses AI-native tooling (Claude Code, Cursor, agents) to go from requirement to working product in days, not months. This isn't about prompting your way to a prototype. It's about owning the full lifecycle: sitting inside a client's workflow, finding what's broken, and shipping the fix yourself.

The Product Engineer sits at the intersection of three disciplines that used to require three different people. You think like a PM, ship like an engineer, and use AI as leverage to collapse the gap between them.

The heads of product are anchors and the product builders/ engineers will report into them, there are 'zones' which are ever changing areas of the product. Builders can be assigned multiple zones.

First 30 days. Get deep on one enterprise client. Shadow their campaign workflow end to end. Ship one working internal tool that removes a concrete piece of manual work - a creator-brief matcher, a contract-review assistant, a content-approval router. In production, used by a real team, by week four.

First 90 days. Own the last-mile build-out for two enterprise accounts:

• LLM pipelines for creator matching, brief analysis, or performance summarisation with real evals, not vibes

• Custom integrations into the client's existing stack (CRM, DAM, finance systems)

• Workflow automation that replaces 3–5 tools with one surface inside Kyra

• Shipping to production weekly, measured on what the client stopped doing manually

You're the person Nicholas pulls into the room when a new enterprise client signs. You've built reusable primitives (eval harnesses, integration scaffolds, prompt libraries) that the next Product Engineer inherits. You have a point of view on where the platform needs to go, and you're trusted to make the call.

• Join customer calls. Extract the real requirement underneath the stated one. Go build it.

• Design and ship LLM features to production - including the evals that keep them honest

• Build custom integrations and workflows the platform doesn't do out of the box

• Make product decisions under uncertainty: scope sensibly, trade speed against correctness, know when something is good enough to ship and when it isn't

• Think adversarially about your own work. Cover the edge cases. Catch the bug before the user does.

Stack

• Backend: TypeScript / Node, Python for ML and LLM workflows

• Frontend: React, Next.js

• LLMs: Anthropic API (Claude) as primary, in-house eval tooling

• Infra: Vercel, AWS, Postgres

• AI tooling: Claude Code, Cursor, agents - expected fluency, not novelty

You don't need every line of this on day one. You do need to be fluent in at least one backend language, comfortable in the frontend, and able to pick the rest up fast.

You've shipped LLM features to production. Something real users depend on.

You think like a PM, but your hands are in the code. You can sit with an enterprise client, feel what's broken in their workflow, and scope the fix yourself. You write the spec, then you write the code. Product instinct first; technical depth right behind it.

You build things outside work. A side project you shipped. An open-source contribution. A tool you made for yourself that other people now use. This is signal, not decoration - for this profile it's closer to a must-have than a nice-to-have.

You hold opinions and change them fast. You'll be wrong sometimes. You'll ship the wrong thing and replace it a week later. That's the job. The people who freeze waiting for certainty don't last here.

You're post-sale, not pre-sale. You're not selling Kyra - you're making Kyra impossible to rip out once it's in. Comfortable embedding with enterprise teams, but the work is building, not pitching.

• Pure product strategy PMs - the role is 70%+ hands-on build

• Senior ICs whose last two years have been reviewing PRs and running roadmap rituals

• Anyone who needs a fully-scoped spec before they start

• Creator economy, influencer marketing, or social platform experience

• Experience inside an FDE, Solutions Engineering, or Deployed Engineer function

• Startup shipping experience (you've been early at a company that scaled)
  

• Location: London-based with an office; team mostly remote with regular in-person days

• Work authorisation: Existing right to work in the UK or EU required. We can't sponsor visas for this role

Team: Small product team of builders and engineers shipping end to end.

💟 Support

If you have a condition or require an adjustment to our interview process - please let us know so we can make adjustments to support you. Please note that when you submit an application or resume, your data will be processed in line with our privacy policy.