UX Designer

Remote: (almost) anywhere,

Workbrew’s mission is to make all the world’s software discoverable and instantly available to everyone. Our customers, IT administrators, use Workbrew to promote their security posture and enable tool choice in their organizations.

Our fully-remote team is spread across North America, Europe, and Asia, and includes alumni of remote-first organizations like 37Signals and GitHub. There is no “HQ” and we have no plans to open one.

You can read more about our philosophy and values here.

About the role

We’re hiring a UX Designer to own customer research and UX design at Workbrew.

This is a research-weighted role, and we mean that literally. Roughly half your time goes on talking to customers, testing ideas with them, and turning what you learn into recommendations the company acts on. The other half is the UX design work that follows from it: flows, prototypes, and the interface for a product that IT administrators live in every day.

We are a scaling company, one product team, and more bets to place than we can properly de-risk. We run product discovery continuously — every bet has a problem statement, a stated outcome, and a confidence level attached to it before we commit engineering time. What we want is more depth behind those decisions: more customers talked to, more ideas tested before they’re built, and evidence carried all the way through to a recommendation. That’s what this role owns.

In this role, you will

• Own customer research end to end: recruiting participants, writing user research scripts, moderating sessions, synthesizing, and writing recommendations.
• Build static and interactive prototypes — putting them in front of real IT administrators before we commit engineering time to a specific direction.
• Design parts of our web and native applications upfront, reducing the amount of time that we need to spend on “UX refactoring”.
• Work with sales, customer success, and channel partner managers as your route to users — and then building your own relationships directly with those customers.
• Describe how our segments actually differ between user personas and buyer types — so that we can focus on the right problems for the right people.
• Decide and understand how much attention a given initiative deserves. Some things we know well enough to just build — some things we’re guessing at and need to test properly. Knowing the difference is the job.
• Run our quantitative research: surveys, satisfaction and sentiment measurement, and unmoderated testing, so we hear from a lot more customers than we can get on a call.
• Help set up and read quantitative product analytics, so we know whether what we shipped worked.

Success in this role looks like

• Product decisions cite evidence instead of assumptions, and everyone in the company can see the evidence.
• Initiatives get reshaped or killed before engineering starts, not after.
• Significant pieces of work have had some form of prototype in front of real customers before we commit a long cycle to it.
• We can describe how IT administrators, security teams, developers, and managed service providers each experience the product, and we design for them differently.
• We have a running read on customer satisfaction, and we can see it move.
• Workbrew gets measurably better to use, and the pace of shipping doesn’t drop.

Our tool set

• GitHub
• Figma
• SQL querying tools
• Claude
• Slack