Skip to main content

Do the best engineering of your career

Small senior teams. Real production AI. Clients who ship. No bench, no utilization targets, no theater.

Life at ChainCraft

Built by builders, for builders

You'll work in a team of 3–5 seniors with direct client access and real decision power. We write things down, demo weekly, and retro honestly. Most of our leads started as engineers here — we promote from within because we hire people worth promoting.

  • 3–5

    people per project team

  • 9+

    yrs avg. engineering experience

  • 0

    hours on a bench

  • 4.8

    Glassdoor rating

Benefits

Taken care of, properly

What the work is actually like

You will be on one project at a time, in a team of three to five, with direct access to the client’s engineers and decision-makers. There is no account manager between you and the person whose problem you are solving, and there is no separate team that scoped the work before you arrived — you were probably in the room.

A typical week has one live demo on real client data, a written update you contribute to, and four days of building. We default to writing: decisions, architecture, trade-offs and post-mortems all get written down, partly because clients need the record and partly because writing is how we find out whether we actually understand something.

The work is unusually varied for a delivery role. Over a year you might build an agent that handles logistics exceptions, a retrieval pipeline over ten years of clinical guidelines, and a voice system that books appointments for forty dental practices. The domain changes; the engineering standard does not.

It is also unusually accountable. Every system we ship launches with agreed KPIs and a dashboard. You will find out whether your work moved the number, which is uncomfortable occasionally and is the main reason people who join tend to stay.

How we are structured, and what that means for you

There is no bench and there are no utilisation targets. Between projects you are working on internal tooling, the evaluation frameworks, or the research that feeds our writing — not being marketed to a client as available capacity.

We promote from within because we hire people worth promoting. Most of our leads started as engineers here. Career progression is discussed openly twice a year alongside compensation, which is benchmarked at the same cadence rather than negotiated when someone threatens to leave.

Seniority at ChainCraft means judgement rather than tenure: knowing which problems are worth solving, when to tell a client no, and when the correct engineering answer is something simpler than the interesting one. We interview for that specifically, which is why the technical round is a conversation about systems you have built rather than a puzzle.

Open positions

We're hiring

Hiring process

Four steps, two weeks, no puzzles

  1. 01

    Intro call (30 min)

    Mutual fit, your story, our honest pitch. With the hiring manager, not a recruiter.

  2. 02

    Technical deep-dive (60 min)

    A conversation about systems you have built — no leetcode, no trick questions.

  3. 03

    Paid work sample (½ day)

    A realistic, scoped problem from our actual work. Paid, and yours to keep.

  4. 04

    Team fit + offer

    Meet your future team, ask anything. Offer within 48 hours of the final round.

Apply now

No cover letters. Show us something you've built instead.

We reply to every applicant, successful or not.