We hire people who read the spec for fun.

Half our work is client implementation; the other half is writing the documentation that sits on this site. If you've argued about semantic HTML in a code review, filed a browser bug, or read the WCAG success criteria rather than the summary, we'd like to talk.

What the job involves

Everyone here writes. Not as a side task, publishing is a real part of the role, and you'll have your name on documentation that other developers use. If you've wanted to write technically but never had the time carved out for it, that's most of what makes this place different.

The rest is client work built to the same standards we publish, which means you won't be asked to cut accessibility testing in week three to make a date.

What we look for

• Real fluency with web standards, not just familiarity with the tools that implement them
• The ability to explain something clearly in writing to a reader who isn't in the room
• Comfort with being told a PR doesn't meet the bar, and treating that as information
• Willingness to say 'this deadline is unrealistic' in week one rather than week four

Open Roles

We do not have any specific roles open at this exact moment.