Skip to content

Open role · Product & Design

Product Designer, AI Systems

Design clear, trustworthy product experiences around complex AI behavior, operational workflows, and the moments where human judgment matters.

Remote — internationalRemoteFull-time

Job description

About the role

AI products fail when the interface hides uncertainty, asks users to trust unexplained automation, or ignores the workflow around the model. This role designs the product experience from discovery through production handover.

The mandate

You will work with founders, operators, engineers, and researchers to understand the job, decision, data, and consequence of error. You will shape information architecture, interaction models, prototypes, design systems, and production details for AI-assisted and agentic workflows.

The role requires curiosity about system behavior. You should be comfortable designing confidence, provenance, review, correction, fallback, permissions, and monitoring—not only ideal-state screens.

What strong performance looks like

You turn an ambiguous technical capability into a coherent workflow that users can understand and control. Prototypes answer meaningful questions, engineering receives clear interaction logic, and the released product remains usable when the AI is uncertain or wrong.

How we work

Design is part of the delivery team, not a downstream service. You will participate in discovery, challenge technical assumptions, test concepts directly, and stay engaged through implementation and refinement.

Responsibilities

The work this role is expected to own.

  • Lead discovery and workflow mapping with users, buyers, domain experts, and technical teams
  • Design interaction patterns for AI suggestions, agents, review, correction, provenance, and fallback
  • Create information architecture, prototypes, production UI specifications, and design-system components
  • Plan and run focused usability studies that change product or engineering decisions
  • Collaborate closely with software and AI engineers through implementation and quality review
  • Document edge cases, states, accessibility behavior, and responsible interaction boundaries

Requirements

Capabilities and experience that support success in this role.

  • Professional product-design experience on complex software or workflow products
  • Strong interaction, information architecture, prototyping, and visual-design fundamentals
  • Portfolio evidence showing how research and iteration changed a shipped product
  • Ability to understand technical constraints and design for incomplete or uncertain system behavior
  • Strong written and verbal communication across product, engineering, and business contexts
  • Commitment to accessibility, clarity, and user control

Nice to have

Useful adjacent experience, but not a substitute for the core requirements.

  • Experience with AI-assisted, agentic, analytics, or developer-facing products
  • Ability to contribute to frontend implementation or design-system code
  • Experience in enterprise, industrial, regulated, or high-consequence workflows

How to apply

Send a concise introduction connecting your experience to the mandate. Include links to shipped, published, measured, or inspectable work, and identify the decisions or tradeoffs you personally owned.

Compensation, engagement structure, benefits, jurisdiction, eligibility, and working-time overlap are discussed early in the process. Generic cover letters are not required.

Email your application

Interested in a different mandate?

View all open roles

Built for accountable delivery

Clear scope. Technical evidence. A team that can ship.

We begin with the operating constraint, agree on what success looks like, and build a delivery path your technical and business teams can review.

01

Defined outcomes

Scope, constraints, milestones, and decision owners before build work starts.

02

Evidence at every stage

Evaluation plans, working artifacts, and reviewable technical decisions—not presentation-only progress.

03

Production handover

Integration, observability, documentation, and an operating path for the teams who own the result.