The company builds tools that help teams spot broken product experiences, work out what caused them, and fix them before more users are affected.
The team cares a lot about how software behaves, so design sits at the centre of the work: complex problems need to become easy to grasp, and teams need a clear route to a fix.
Responsibilities
You'll work day to day with the founder, the design engineer, and the engineers to decide what gets built and how it behaves.
Help shape the product by deciding what to build and why, questioning assumptions, and weighing trade-offs in scope and priority.
Turn complicated workflows into clear, intuitive interfaces, paying close attention to layout, typography, interaction, and motion.
Take a problem from the first user conversation to the shipped result: choose what is worth solving, make product calls, explore options, and resolve details with engineering.
Talk with users to learn how they work and how they use the company, and let what you learn guide your decisions.
Prototype interactions and keep improving the experience after launch.
Notice what is confusing, missing, or due a rethink, and push it forward without waiting to be asked.
Requirements
At least 3 years of product design experience, including shipped products you can walk through, covering your contribution, your decisions, and what you learned.
An exceptional eye for UI: strong sense of typography, layout, spacing, colour, and interaction, visible in your work.
Sound product judgment: you look beyond single screens, identify the root problem, challenge proposed solutions, and help decide what deserves building.
High agency: you turn ambiguous problems into clear next steps, find the context you need, make decisions, and follow through.
Drive: you want work you're proud of, seek honest feedback, keep raising your own bar, and have taken on ideas or responsibility beyond what was asked.
Curiosity about users: you reach out, ask questions, and test your assumptions to see whether your designs actually help.
Experience designing developer tools or other complex software.
Experience at an early-stage startup or taking a product from zero to one.
Familiarity with observability basics such as logs, traces, metrics, and session replays.
Helpful, but not required: technical knowledge, or the ability to prototype and build interfaces in code.
Send your portfolio and a short introduction. Choose one or two projects that best show your work, explain what you owned, which decisions you made, and what shipped. Side projects are welcome too.