Skip to content
All disciplinesWe are hiring

Design

Flows and screens, agreed before any code is written.

  • Flows, states and edge cases
  • Wireframes through to final screens
  • The design system underneath them
  • A handover the front-end can build to

The work

You decide how a thing works before anyone decides how it looks: the flows, the states nobody thinks to ask about, and the screens that come out of them. All of it is agreed with the client before the build starts, so the work is finished when somebody else can build from it without coming back to you with questions. Most of the job is the unglamorous half — the empty screen, the error, the form filled in wrongly — because that is where a product is actually judged. You will spend as much time explaining a decision as making one, and you are expected to have a reason for both.

What the week contains

  • Flows, states and edge cases

    Every path traced end to end, including the ones that fail, stop halfway, or are taken by somebody without permission. The edge cases are the deliverable rather than an appendix to it.

  • Wireframes through to final screens

    Structure and hierarchy settled before colour and type enter the conversation, then the same flows taken all the way to screens a developer can build from.

  • The design system underneath them

    Components, spacing, type scale and colour defined once and reused, so the twentieth screen still agrees with the first.

  • A handover the front-end can build to

    Measurements, behaviour and states written down. If the built version has to approximate anything, the handover was not finished.

Who you work with

A project reaches every discipline in turn. These are the people the work comes from and goes to.

Open roles

No role is posted here right now. We read applications in every discipline above, posted role or not.

How applying goes

  1. Send your work

    A repository, a portfolio, or whatever you consider your best work. No cover letter, and no form that asks you to retype a CV you have already attached. If the best thing you have made is not public, describe what it did and what your part in it was.

  2. A reply from a person

    Either way, and from somebody who actually opened what you sent. Not an automated acknowledgement, and not silence — an application that goes no further still gets an answer.

  3. A conversation with your discipline lead

    With whoever leads the discipline you applied to, not with a recruiter relaying answers. It is a conversation about work you have done rather than a quiz, and you are expected to ask as much as you answer.

The other disciplines

Get in touch

Every one of these reaches us directly, and is answered by a person.

11:15Triple A