Life at the studio

What working here is actually like.

A small team changes the shape of the job. Here's what that means, day to day.

  1. You touch the whole build.

    Front-end one week, back-end the next, sitting in on the client call after that — never parked on one narrow slice.

  2. Your work ships, and gets used.

    We're too small to build things that sit in a drawer. What you make goes live — to real people, usually within weeks, with your name on it.

  3. You learn next to the people doing it.

    You pair directly with senior work — ask the "obvious" questions, watch a messy problem get solved, then take the next one.

  4. You see the whole business.

    How a project gets scoped, priced, built, and looked after. The parts most people don't meet until years in, you'll see from the start.

The work

Where you'd get your hands dirty.

The studio takes on a bit of everything. Come in strong in one of these and curious about the rest — you'll end up touching more than one.

  1. Front-end — web & app

    Interfaces that load fast and feel right, on a phone and on a laptop.

    HTML · CSS · JS · React
  2. Back-end & APIs

    The logic, data, and integrations that make an app actually do its job.

    Node · databases
  3. Mobile

    Turning web apps into installable apps people keep on their home screen.

    Capacitor · native
  4. Design & UX

    How a thing should look, feel, and flow — decided before a line is written.

    Figma · the brand
  5. Data & reporting

    Scattered numbers pulled into dashboards people actually read.

    SQL · charts
  6. Testing & quality

    Breaking things on purpose, so they don't break for the client.

    the safety net
  7. DevOps & shipping

    Getting the work live, keeping it up, and making deploys boring.

    Vercel · CI
  8. Client & product

    Turning "we need something for X" into a plan someone can actually build.

    the human side

Nobody's expected to do all eight. The point is you get to try more than one — and find the ones that fit.

Internships

A real internship — not a coffee run.

We run internships the way we wish ours had gone: a real project, a real mentor, and your name on work that actually ships.

  1. A project that's yours.

    Scoped to something you can genuinely own — small enough to finish, real enough to go live.

  2. Someone in your corner.

    A senior who reviews your work, unblocks you, and pushes you further than you'd push yourself.

  3. A path, if it fits.

    Interns who click with how we work are the first people we call when a role opens up.

We take interns year-round, in whichever of the areas above you want to learn. There's no fixed intake window — if the timing's right for you, tell us.

The fit

More curious than credentialed.

We don't have a checklist of years and acronyms. We hire for three things.

  1. You'd rather understand than pretend.

    "I don't know yet, but I'll find out" beats bluffing, every single time. Curiosity is most of the job.

  2. You care how the thing is made.

    Not just that it works — that it's clean, clear, and the next person can pick it up without cursing your name.

  3. You want the whole picture.

    You're here to learn how software and a business actually fit together — not just to close tickets.

A degree is fine; it isn't the point. Show us one real thing you've built — a repo, a site, a rough sketch — and you already have our attention.

How to apply

Introduce yourself.

We're small, so there isn't always a formal opening — but we always want to meet people who'd fit, and internships are open year-round. Send a short note: who you are, what you'd love to work on, and one real thing you've made.