Careers
Build what matters. Document what you learn.
We are a technical team where building, research, documenting, and professional services reinforce each other. The documentation exists because we build real things; what we build is informed by our documentation.
Build software for teams who care how it works underneath.
We are a distributed team working asynchronously across time zones. We build our own products and client software for teams who care how things work under scrutiny, turning real production work into open, checkable guidance.
Paid trial tasks, clear expectations, and asynchronous onboarding.
You
Distributed ContributorA Technical Team
Web Specification Studio combines product development, technical documentation, research, and professional services into a single practice. The systems we build inform the knowledge we share, and the knowledge we share improves everything we build.
Our teams work closely across disciplines, so research, implementation, documentation, and professional services continuously inform one another.
Life at WSS
Every role at Web Specification Studio contributes to a larger goal: improving the quality of the web through thoughtful implementation, careful research, and openly shared knowledge. Whether you're building products, researching browser behavior, writing documentation, or helping organizations apply modern standards, your work becomes part of that mission.
What you'll work on
Building
We build websites, applications, products, developer tools, and internal systems with a strong emphasis on performance, accessibility, maintainability, and standards compliance.
Research
We deep-dive into browser rendering engines, WHATWG/W3C specs, security policies, and performance boundaries to trace how the web behaves at a fundamental level.
Publishing
Publishing is a core part of WSS. Depending on your role, you may contribute technical documentation, implementation guides, research notes, or editorial reviews that help other developers build better software.
Professional Services
We help organizations improve websites, applications, products, and technical systems, solve complex technical problems, and apply the same standards and practices documented throughout this site.
Our working principles
Our day-to-day work reflects the same principles described throughout our Practices documentation:
Standards over shortcuts
Verify before publishing
Build with accessibility from the start
Measure performance instead of assuming it
Share knowledge openly
How we work
Why WSS is different
Fluid boundaries
Collaboration across disciplines is part of how we work. Teams regularly share knowledge between implementation, research, publishing, and professional services.
Production grounding
We publish documentation because we build real things. The guides we write are grounded in standard browser behaviors we have personally run and measured, not textbook examples.
No content silos
Documentation is part of how knowledge is shared across the team, not an isolated function.
Standards-first culture
We trace every claim back to the primary specification rather than secondary blogs. This rigor ensures that what we build and what we publish remains correct for years.
Why people join WSS
Work across building, research, and publishing instead of staying in one discipline
Contribute to work that is publicly shared and trusted by developers worldwide
Learn directly from web standards and browser engines rather than secondary summaries
Solve real-world production problems and turn them into public, checkable knowledge
Help shape the future of Web Specification Studio as it grows
What success looks like
Success at WSS isn't measured by how many tickets you close or how many words you publish. It's measured by whether your work remains technically correct, useful to others, and grounded in real implementation. We care far more about the long-term quality and usefulness of your work than the number of tasks completed.
What we look for
Curiosity to investigate how technologies actually work rather than accepting conventional wisdom
Comfortable reading W3C, WHATWG, and IETF specifications directly to verify technical claims
Can write plainly and directly about complex technical subjects without marketing copy or jargon
Hands-on experience with HTML, CSS, and JavaScript, enough to test hypotheses rather than take them on faith
Commitment to precision: fact-checking your own assertions, writing tests, and accepting editorial peer review
Hiring process
Introduction & Sample
Send a short note and a technical writing sample or a project you built to strict specifications.
30-Minute Conversation
We discuss your sample, your experience, and how we work as a team. No puzzle questions.
Paid Trial Task
A short, real assignment with full editorial and technical support, paid regardless of the hiring outcome.
Offer
A clear offer scaled to your weekly hours. We keep you informed and update you either way.
Open roles
Technical Content Writer, Intern
2 OpeningsResearch web standards, verify implementation examples, reproduce browser behavior, and write technical documentation covering performance, accessibility, architecture, and related topics.
View role →Not seeing the role you are looking for? We are always open to the right people.
Send us your work anyway
We keep strong applications on file and reach out when something opens up. Show us a project you built to strict specifications, or a piece of technical writing you're proud of.
Introduce yourself →Before you apply
Do I need a computer science or journalism degree?
No. We look for technical writing samples or projects you have built that get a specific detail right. Practical competence and a clear mind matter more than credentials.
Is this remote-only?
Yes, every role here is remote. We are a small, distributed team working asynchronously across various time zones.
No open roles fit me right now. Should I still reach out?
Yes. We are always open to the right people. Send us your work anyway, and we will keep your application on file for future openings.