Help us build the content engine for the next decade
We are a small, deliberate team, and right now we are hiring for one role.
Open positions
What working here looks like
Small team, every voice ships product
We are deliberately small. There is no six-person committee between an idea and a shipped feature. If you have an opinion worth having, it will be heard and it will have a chance to influence what we build.
Remote-first, not remote-tolerant
The whole team is distributed. There is no office to be close to, no in-person meeting that matters more than an async one, and no timezone that gets treated as the default. The tools and practices are built for remote from the ground up.
Ship weekly, not annually
We have a changelog. It gets updated. Features go from idea to production in days or weeks, not quarters. If you thrive in slow-moving environments with long planning cycles, this is probably not the right fit.
We say no a lot, focus is the asset
Good ideas get rejected here too. Not because they are bad ideas, because saying yes to everything means shipping nothing well. We are building a focused product, and that requires a focused team.
Async-first, sync where it pays off
Most decisions happen in writing, well-reasoned, easy to reference later. Synchronous calls are for things that genuinely benefit from real-time back-and-forth: brainstorming, complex debugging, relationship-building. Not status updates.