About Kyra

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.

Role in a nutshell

You build working software live, in the room, while the deal is still on the table.

You sit in Product and go into deals alongside our sellers. You take a prospect's real social and content data, run it through our intelligence layer, and write the code that stands up a personalised, working version of the product before the meeting is over.

You are an engineer first. That is the bar, and it does not move. The commercial instinct sits on top of it. You can hold a room, read a buyer, and connect what the product does to what their business actually needs.

You stay with the client from the first demo through go-live. You win the deal in the room, then run the onboarding that gets their team live on their own data. The deeper, ongoing custom build for an account is our Product Engineer's job.

📍 Location: London (hybrid, 3 days a week in office)
📍 Reporting to: Product Builder

How fast we move

Kyra moves quickly. The product team takes a requirement to working software in days, using Claude Code, Cursor and agents. New product hires ship something real and in production inside their first few weeks. That is the normal speed here.

This role sits at the very front of it. The gap between a client asking "could it show me which creators actually drove sales" and watching it run on their own data is usually minutes.

Why this role exists

The creator economy is full of tools that promise everything and prove nothing. Brands have been burned. CMOs have learned to tune out the slides.

So we stopped pitching ideas. Now we show proof. That takes someone who can grab messy real-world data, put real intelligence on top of it, and turn it into a live demo on the brand's own world. No three-week build cycle hiding behind the curtain.

You are also the highest-bandwidth feedback loop we have. A builder watching real buyers react in real time, then carrying that straight back to the roadmap. Every "wait, it can do that?" becomes the next thing we build, often within days. That loop is why the role sits inside Product.

What you'll actually do

Go into the room. Be the technical lead next to our sellers and own the hard questions. You are often the only technical person in a room full of buyers, improvising answers nobody prepped you for.

Build it live. Capture a brand's data, run it through our proprietary model, and build a working version they can query, chat with, and poke at. When someone asks "can it do this?", you build it on the spot.

Onboard new clients. Once a deal lands, get them live. Run the two sessions: one to configure them on their own data, one a full platform walkthrough that gets their team using it.

Close the loop. The feedback loop into Product is core to the role. Stay across what is working and what needs fixing. Turn every request, gap, and bespoke build from the field into clear, evidenced input for Product and Engineering. Where a fix is small enough to ship yourself, contribute to deploying it.

Hand off deeper build. Where an account needs ongoing custom work, pass what you built and learned to the Product Engineer who embeds with it, so they never start cold.

The stack

You build on the same stack the product runs on. That is what lets you move fast in the room and hand off clean afterwards.

Builds (non-negotiable). Genuinely builds. Comfortable across Backend (TypeScript / Node and Python), Frontend (React, Next.js), and LLMs (Anthropic API and in-house evals). Solid working knowledge of Infra (Vercel, AWS, Postgres) and AI tooling (Claude Code, Cursor, agents). None of it brand new on arrival.

Deep expertise

Backend: TypeScript / Node, plus Python for the ML and LLM work

Frontend: React, Next.js

LLMs: Anthropic API (Claude) and in-house eval tooling

Solid working knowledge

Infra: Vercel, AWS, Postgres

AI tooling: Claude Code, Cursor, agents, used fluently every day

None of this should be brand new to you when you arrive.

Who you are

• You build. It is the first thing people say about you. Give you a problem and you reach for a prototype. The most interesting line on your CV is probably the thing you built at 2am that other people somehow started relying on.

• You are fast. Your bar is speed and fluency in front of people. Deep production hardening is a different job, and someone else owns it.

• You read a room. You can sit across from a CMO, work out what they actually care about, and make a complicated idea land with someone who has never written a line of code.

• You know the creator economy. Or you are hungry enough to learn it fast and keep up with how quickly it moves.
  

Your first six months

• You won't be selling in week one, and we don't expect you to be. The early weeks are about getting you to capable. The pressure to perform in the room comes once you know the product and the stack cold.

• Your first week. In London with the team. Getting set up, learning the product end to end, and shadowing real deals and onboardings to see how sellers and clients actually use it.

• By week three. You have run live demos and client onboarding sessions with support. Internally first, then in lower-stakes deals. You are starting to capture field signal and log it where Product can see it. You are monitoring client sessions and platform use proactively, through tools like LogRocket and PostHog, and flagging what you see.

• By three months. Building personalised demos on real prospect data is routine. More than one seller is pulling you into their deals. Product is already acting on what you bring back from the room.

• By six months. You are the technical edge sellers reach for. Demos are faster to stand up than the day you arrived. And features that exist because you surfaced them from the field are shipped and in use.
  

Who this isn't for

• The slide presenter who doesn't build.

• The engineer who wants to live deep inside one codebase for a year. That is our Product Engineer role.

• Anyone who needs a fully scoped spec before they can start.

• Anyone who loves the standing-ovation demo but has no patience for the data-wrangling and onboarding underneath it.
  

The details

• Right to work in the UK. We can't sponsor visas for this role.

• Reports into Product, with a dotted line into Sales.
  

Benefits

• 📍Hybrid team. Three days a week together in the London office, the rest from wherever you do your best work.

• 🌴 25 days PTO plus public holidays, 4 company-wide days off (Kyra Days), 3 wellness days, and paid sick leave each year

• 📚 Annual Learning and Development budget to invest in your skills

• 💰 Annual bonus scheme to recognise great work

💟 If you need an adjustment to our interview process, tell us and we will make it work. When you apply, your data is processed in line with our privacy policy.

💟 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.