Isenbrook

Careers

Build systems that stay up, with people who have done it before.

We are a small, senior, remote-first team. You own features end to end, talk to clients yourself and ship every week. If that sounds like relief rather than pressure, read on.

Open roles

3 roles open right now.

EngineeringFull-timeRemote (Americas or Europe)

Senior Full-stack Engineer

Own features end to end on client systems built with Next.js, Node and Postgres, and demo them to the client every week.

Apply by email

What you will do

  • Design and build features across the stack, from schema to UI
  • Run weekly demos and talk directly with clients in the shared workspace
  • Write the decision records for the choices you make

What we are looking for

  • 5+ years building production web applications
  • Strong TypeScript, React and SQL
  • Comfortable owning deployment and monitoring of what you ship
AI EngineeringFull-timeRemote (any overlap with GMT)

AI Engineer

Build extraction, prediction and retrieval systems, and the evaluations that prove they work.

Apply by email

What you will do

  • Design LLM pipelines with confidence scoring and review paths
  • Build and maintain evaluation sets for each system
  • Work with platform engineers to deploy models in client clouds

What we are looking for

  • Shipped at least one LLM-powered feature to production
  • Python, plus enough TypeScript to integrate with product teams
  • You care more about the eval score than the demo
PlatformFull-timeRemote (Europe or Middle East)

Platform Engineer

Own cloud infrastructure, pipelines and on-call for a portfolio of client systems on AWS and Azure.

Apply by email

What you will do

  • Build and maintain Terraform modules and GitHub Actions pipelines
  • Design monitoring and alerting that pages for the right reasons
  • Run incident reviews and write the runbooks

What we are looking for

  • Deep experience with AWS or Azure, Docker and Kubernetes
  • Terraform in anger, not just tutorials
  • Calm on call

Nothing that fits? Write to hello@isenbrook.com with what you have built. We read every message.

How we work

The same rules apply inside the team.

  • Scope by what we leave out

    A scope lists what the system will not do as clearly as what it will. Most arguments on a project trace back to something nobody wrote down.

  • Prove it with a number

    An AI feature without a baseline and an evaluation is a guess. We do not call it working until it beats the number it was meant to beat.

  • Build what we would run

    We operate the systems we ship, so we build them the way you build something you expect to be paged about.

  • Say the awkward thing early

    If the right answer is to buy a product, build less or not build at all, you hear it on the first call. It costs us work sometimes and keeps clients for years.

What you get

  • Remote-first, with overlap windows rather than fixed hours
  • You talk to clients directly and demo your own work
  • Hardware budget and a yearly learning budget
  • Four-day weeks in August and the last two weeks of December off
  • Written decisions and blameless incident reviews
  • Senior team; most people have run things in production before joining