Design
Design Engineer
“If you've ever spent an evening pulling apart someone else's product because you couldn't stop thinking about how they solved it - this is probably for you.”
About us
We're hiring for a role we haven't finished naming. We already have a design team. This is one seat, and it's a high-trust one. You won't be handed a queue of screens - you'll be handed problems, most of them before anyone has written a ticket for them. We've spent the last few years building a product that works, with a small team and no shortcuts. We're now at the point where the quality of the product is the quality of the thinking behind it, and we want one more person whose thinking we trust that far. Call it Design Engineer. Call it Product Designer. Call it whatever fits on your LinkedIn - the title is the least interesting part of this.
The role
Here's what we know about the person, even if we haven't settled on what to call them: - They find the problem before anyone writes a ticket for it. - They take the user's pain personally. - They take apart great products to understand why they're great - not to copy the UI, but to find the decision underneath it. - They design systems, not screens. Things that hold up at 10x the users and don't need a rewrite every quarter. - They ship, then measure. If it didn't move a number, it isn't done. - They think about the business, not just the flow. - And they're someone the team actually wants to sit next to. You'll own products end to end - from the messy problem to the thing people pay for. That means you're in the room when decisions get made, and your opinions carry weight. If you need a perfect brief to start, this isn't the place. If you've ever spent an evening pulling apart someone else's product because you couldn't stop thinking about how they solved it, it probably is. How to apply: portfolio > CV. Show us one thing you owned end to end, and the number it moved.
What you'll do
- Find the problem before anyone writes a ticket for it, and frame it well enough that the team can act on it.
- Own products end to end - from the messy problem to the shipped thing people pay for.
- Design systems, not screens: patterns that hold up at 10x the users without a rewrite every quarter.
- Ship, then measure. Define the number a piece of work is meant to move, then go back and check it.
- Take apart great products to find the decision underneath the interface, and bring that thinking back to the team.
- Weigh the business alongside the flow - what we charge for, what it costs, and what actually compounds.
What we look for
- Real product design experience with end-to-end ownership, not just execution against briefs.
- A portfolio over a CV: one thing you owned start to finish, and the number it moved.
- Systems thinking - you build patterns and primitives, not one-off screens.
- Comfortable enough with code to design things that can actually be built (frontend is a big plus).
- Fluent with AI tools and a strong intuition for AI-native products.
- Self-directed. You don't need a perfect brief to start, and you're someone the team wants to sit next to.