Careers

Work on products that actually ship.

Most of what we build goes live and stays live. If you would rather own a product than a ticket queue, and you want to see the thing you built used by real people, this is a good place to do it.

Start a conversation

Why here

What working here is actually like.

Written plainly, including the parts that will not suit everyone.

You own a product, not a ticket

Engineers sit in the client conversation, hear the problem first-hand and push back on requirements. If you want to be handed a fully specified ticket and left alone, this will frustrate you.

Real review, real tests

Every change is reviewed and covered. It is slower on the day and much faster over a year, and it is the reason our people can go on holiday without the release freezing.

Breadth if you want it

Twenty-three service lines and a dozen industries means you can move between stacks and domains without changing employer. People who want depth in one thing can have that too.

Clients you will recognise

Healthcare systems used by hospitals, recruitment platforms used by enterprises, marketplaces with real volume. The work is not internal tooling that nobody sees.

No open role that fits?

Send us what you have built and what you want to work on. We keep good CVs and come back when something matches — several of our team joined that way.

Send an open application

How we work

How our hiring process runs.

Four steps, roughly two weeks. You will know where you stand at every point, and you get a decision either way.

  1. Application

    CV plus anything you have built. A GitHub profile, a shipped app or a written explanation of something you solved counts for more than a covering letter.

  2. Intro call

    Thirty minutes on what you have worked on and what you want next. Also your chance to ask what the work actually looks like before investing more time.

  3. Technical conversation

    A practical problem in your own stack, discussed rather than performed. No whiteboard algorithms and no take-home longer than three hours.

  4. Team and offer

    Meet the people you would work with, then a decision within a week. We tell you either way, with a reason.

Questions, answered

Careers, answered.

Yes, in structured intakes rather than continuously. Freshers join a team with a named mentor and ship real work in the first month — supervised, reviewed, but real. We do not hire freshers to sit in training for a quarter.

Hybrid for most roles, fully remote for some senior ones. Delivery teams overlap with client hours, so the constraint is timezone rather than location. We are honest about which roles are which in the posting rather than at offer stage.

An intro call, a practical technical conversation in your own stack, and a team conversation. No whiteboard algorithm puzzles, and no take-home exercise longer than about three hours. The whole thing usually takes two weeks.

Depends on the team: Laravel, Node, .NET and Python on the backend; React, Next.js and Vue on the front; React Native and Flutter on mobile; AWS, Azure and Kubernetes on platform. You can move between them, and people regularly do.

A certification budget, paid time for it, and — more usefully — code review by people who are better than you at something. The breadth of client work means you see problems you would not meet in a single-product company.

From the team

Notes on building software.

What we have learned shipping products, written up for the people who have to make the same calls.

Read all posts

Share your requirements

Tell us about your project and our experts will craft your customized plan.

Fast response, fully NDA-protected.