Careers · Come build with us

Come build the systems other people run on

We are a small team building real infrastructure — platforms that run in production, with real users and real money moving through them. Nobody here picks tickets off a queue. You get an area, and it is yours.

Small teamsReal ownershipWe ship every week
How we work

Three rules we do not bend

There is no process here for the sake of process. Three decisions shape what the work actually looks like.

  • Small teams

    Two or three people own an entire area. No approval chains, and no meeting whose purpose is to schedule another meeting.

  • Real ownership

    Whoever builds it decides, ships it, and answers for what happens next. Intimidating at first, freeing very quickly after.

  • We ship every week

    Something new goes live every week. Not a demo, not staging — production, with people on the other side of it.

Design, engineering and product sit in the same room. Handoffs are conversations, not documents.

What we look for

Fewer credentials, better judgement

We do not keep a page-long list of requirements. Six things genuinely separate good from great here.

  • Ownership

    You pick a problem up and you do not put it back on the table until it is closed.

  • Taste in product

    You care how it feels, not only whether it works.

  • Code people can live with

    Simple before clever. Whoever reads it after you should understand it in a minute.

  • Speed without sloppiness

    Shipping fast is a muscle you train, not a shortcut you take.

  • Technical curiosity

    New tools do not scare you — and they do not dazzle you either.

  • Straight talk

    You say the hard thing early, before it becomes somebody else's problem.

The process

Four steps, and you always know where you stand

No seven rounds, no disappearing act. This is exactly how it goes, from the first call to the answer.

  1. A first call

    Half an hour. We tell you what we are building here, you tell us what you want to build.

  2. A short task

    A real problem from our world, a few hours of work. No algorithm riddles, no whiteboard theatre.

  3. A technical session

    We go through what you wrote, talk through the decisions, and open real code from the system together.

  4. A decision

    A clear answer within days, either way. Nobody is left hanging.

You can stop at any step, ask anything, and get a straight answer.

What you get here

No grand promises. These are the things we can actually promise

We will not sell you an atmosphere. We will tell you about the work itself, because that is what you meet every morning.

  • An area of your own

    Not tickets from a queue — a whole part of the system that is yours from day one.

  • Code that reaches users

    What you write goes live this week, not next quarter.

  • A modern stack, no legacy debt

    We build new things with current tools instead of maintaining a museum.

  • Direct access to decisions

    There are no layers in between. A good idea can change the product the same day.

  • Real depth

    Multi-tenant systems, twenty languages, payments and real-time data. Things you do not learn on a course.

  • You learn as you go

    Everyone here walks into unfamiliar territory. That is part of the job, not a perk.

The tools you will be working in
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • PostgreSQL
  • Supabase
Open roles

Four doors, all of them open

Every role here is a broad one. If you fall between two of them, write to us anyway — we will find the right seat.

  • Full-stack engineer

    Engineering

    Complete features from the screen down to the database: interface, logic, services and schema. If you like seeing the whole picture rather than one slice of it, this is the seat.

    What you will actually do

    • End-to-end features inside a multi-tenant environment
    • Integrations with external providers and their quirks
    • Full ownership of everything you put live

  • Front-end engineer

    Engineering

    Interfaces that look sharp and feel fast — in twenty languages, in both writing directions, on every screen size. Here pixels are not a luxury, they are the craft.

    What you will actually do

    • Bidirectional interfaces that look right in every language
    • Measured animation and micro-interaction
    • Performance and accessibility as the baseline, not the polish

  • Back-end & infrastructure engineer

    Engineering

    The heart of the system: data, services, payments and real time. Precision is worth more than speed here, and nothing rests on "it will probably hold".

    What you will actually do

    • Schemas, migrations and performance under load
    • Payment rails and flows that are not allowed to fail
    • Security and permissions at the tenant boundary

  • Product designer

    Design

    Design that goes all the way to the real screen: flows, states, and the small details that turn a heavy system into a tool people enjoy using.

    What you will actually do

    • Screens and a design system that holds up over time
    • Working shoulder to shoulder with engineering, not handing over files
    • Design that works in dark mode and light mode alike

Still reading? That is usually a good sign

Send us a few lines about yourself and what you want to build. We read everything, and we answer everyone.

A polished CV is optional — a link to work you are proud of is plenty.