What web design careers here look like
You own your work
Small teams and direct contact with the people you are building for. You will not be three layers removed from the person whose problem you are actually solving.
Work across the stack
Front end, back end, infrastructure, and the hardware it all connects to. Most people here end up doing something outside the specialism they arrived with.
Standards over shortcuts
Clean, documented, standards-based work. We would rather take the time to do something properly than ship a shortcut the next person has to unpick.
Straight answers
Clear scope, honest timelines and feedback you can actually act on. That applies inside the team as much as it does with clients.
OPEN APPLICATION
Tell us what you do
We do not always have a role advertised, but good applications get kept on file and we come back to people when something fits. Tell us what you work on and what you would want to be doing — we reply within one working day.
Most of the work here involves more than one discipline. Someone building a business website ends up talking to whoever handles the integration behind it, and whoever specified the hardware it has to reach. You are not expected to know all of that. You are expected to be interested in the parts you do not know yet.
There is no graduate scheme and no fixed intake. If what you do is useful and the work is there, we will find a way to make it work, and if it is not we will say so rather than leave you waiting. Our blog is a fair sample of how people here think about problems.
If you are early in your career and working out where to focus, the MDN learning area is the resource we point people at most often. Web design careers here start from fundamentals rather than frameworks.