Role Description
You'll join as our second designer, working closely with our design lead across two areas:
-
Growing the design system:
The Daybreak Design System covers our demand planning product today. As we expand into new adjacencies, each one needs patterns that don't yet exist. You'll design them, and help make sure the decisions hold up across the whole system.
-
Improving what's already live:
Our product is in daily use, and user feedback gives us a steady stream of things to sharpen. You'll own that work: take a piece of feedback on an existing screen, understand the need behind it, and ship a better version.
What you'll do:
-
Design end-to-end: problem framing, flows, interaction, and visual detail for features on live product surfaces, with support on the more ambiguous calls.
-
Build and maintain our Figma libraries: components, variants, tokens, and documentation that other designers and engineers can rely on.
-
Keep the system legible to our AI tooling, so components and documentation serve Claude Code as well as they serve a designer.
-
Prototype in code with AI assistance, so the team can respond to a working interface.
-
Assist in conducting user research β interviews and usability sessions, and turn what you learn into something the team can act on.
-
Work alongside product, engineering, enterprise services, and training teams, from kickoff through release, and hold the quality bar on what ships.
Qualifications
-
1-3 years designing software products. Enterprise or data-dense tools are a plus, and the portfolio matters more than the number.
-
Strength in both UI and UX. Visual craft that holds up at real data volumes: hierarchy, typography, density, tables and charts that stay readable, alongside clear thinking on problem framing, information architecture, and flows.
-
Figma at a systems level. You've built and maintained a component library.
-
An AI-first way of working. You use LLMs throughout your process, and you can take a Figma frame to a working prototype with Claude Code or a comparable tool.
-
A portfolio that shows how you solve problems. Three or four cases is plenty. For each, we want the problem as you framed it, the constraints you worked inside, the decisions you made and why, and what changed once it shipped. Polished screens on their own won't tell us much. Academic and personal projects are welcome if the thinking is visible.
-
Genuine interest in agentic products, and in helping define what planning software becomes when agents handle the routine work.
Requirements
-
Working knowledge of GitHub: branches, commits, pull requests.
-
Exposure to supply chain, retail, CPG, or analytics products.
-
Design system documentation you can point to.
How we work
Design at Daybreak is AI-first. Work usually starts in conversation with an LLM to sharpen the problem, moves into Claude Code to prototype flows and interactions against real components, then returns to Figma for system alignment and polish, with the Figma MCP keeping design-system context in the loop. We do expect you to pick up new tools quickly, and without being asked.
Applying
A resume and portfolio are required. Send us a portfolio link with a password if it needs one to
[email protected]
with the subject
Associate Product Designer
.
If you're early in your career and this is the work you want to be doing, apply. We'd rather read three careful case studies than count years.