Backend Engineer | 36labs
- London
- Full-time
- Posted
Job description
Role: Backend Engineer
Company: 36 Labs https://36labs.ai/
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:
WHAT YOU NEED TO SUCCEED:
EXPERIENCE
HOW YOU WORK
PRACTICALITIES
WHAT YOU GET:
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.