Backend Engineer | 36labs

hirehireLondon, EnglandOn-siteFull-timeMid level, 2–5 yearsListed 2 hours ago

Apply now

About this role

Role: Backend Engineer

Company: 36 Labs

Location: London, Baker Street office, four days a week (a move to Primrose Hill is likely within a couple of months). London-based candidates only. No relocation and no visa sponsorship in this hiring cycle.

Job Type: Full-time

About 36 Labs

36 Labs is an applied AI research firm in London. It works on a problem most models are still bad at: making creative decisions, and explaining why they were made. The team wants models to reason creatively, more like a person would.

Today the product is a harness that sits over any frontier model, video generation models in particular. It handles ideation, generation and distribution end to end, and the content goes out to real audiences. The results feed a data loop that keeps improving the harness. The first use case is music marketing, and the clients are the major labels, including Sony, Warner and Universal.

The company has been profitable since it started operating. It is closing its first seed round within the next couple of weeks, and the round was oversubscribed. The team is about ten people, with four engineers who report to the CTO. He is still very hands-on in the code.

You would join at a big moment. V3 of the harness is being released, which is a huge scope of work. A migration to Cloudflare is planned, and it falls mostly to the backend engineer. The stack is Python, TypeScript, Postgres, LLM and generative model APIs, and open-weight models.

What you are expected to do:

- Migrate many of the company's systems to Cloudflare. This is your first big task.
- Work on a bit of everything as needed. Engineers here are not siloed, and the structure is flat.
- Take a direction from the team and own it, without close supervision.
- Explain your approach back to the team and talk it through. Disagreement is welcome.

What you need to succeed:

Experience

- You have 4+ years of experience, including years building and running back-end systems in production. You know how they were deployed and operated.
- You are hands-on as an engineer in the AI-native era, and you keep reviewing how you work. You follow the latest stacks, models and practices.
- You have owned something real before. Ownership and leadership are visible in your CV and your projects.

How you work

- You take initiative and work independently. The culture here is high agency: it is often easier to ask for forgiveness than permission.
- You communicate clearly and can explain your ideas to the team and discuss them. No big ego.
- You are comfortable with an extremely fast pace and very little stability.

Practicalities

- You are based in London and happy to be in the office four days a week.
- You do not need visa sponsorship in this cycle. A visa that expires next June is fine.
- Nice to have: a degree in computer science, engineering, maths or stats. An MSc or PhD is a real plus. With a BSc only, your track record needs to be really strong.
- Nice to have: projects beyond your university or company roles. Where you studied matters little, and what you have built matters more.

What you get:

- Seed-stage experience that builds a wide range of skills and looks good on a CV.
- Room to move into a more senior role as the CTO gradually steps back from the code to focus on strategy.
- A company that is profitable, with an oversubscribed first round and another fundraise planned in the next nine to twelve months.
- Work with the major music labels as clients, and a rare problem: improving creativity in models. The team believes that if creativity in LLMs is solved, human attention is within reach.
- A big scope from day one: the V3 harness release and the Cloudflare migration.
- A flat team where direction is given, ownership is yours and challenge is welcome.

How to apply

Send your LinkedIn profile or CV, plus any projects you are proud of, to the recruiter who shared this role. Use the subject line "Backend Engineer – 36 Labs". We screen candidates first, then introduce a small number to the client. The process: a first conversation with Benedict, Head of Operations (CV, projects, motivation, fit), then a technical interview of about 30 minutes with the CTO, then a take-home assessment. An onsite working session happens only if needed. Timelines are quick, but a notice period of around a month is fine.