Careers at Zentrik / 8 open roles

All roles

Head of Product Experience

Own the product and interaction quality across Zentrik’s core workflows, design system, and AI collaboration patterns.

Read role detailsStart a conversation
8
open roles
4
role paths
1
small team

Experience

Zentrik evidence graph with source-backed product context.

Work context

Roles connect to real product systems

Hiring brief

Head of Product Experience

Product experience, interaction design, and design systems

You bring
Strong judgment and visible work
You own
A clear role with real company scope

Experience / Leadership role

Head of Product Experience

Product experience, interaction design, and design systems

A senior product design and product leadership role for someone who still wants to shape the work directly.

Own the product and interaction quality across Zentrik’s core workflows, design system, and AI collaboration patterns.

Start a conversation

A concise note is enough to start.

What you would own

  • The end-to-end experience across discovery, definition, planning, agent collaboration, and future product surfaces.
  • The interaction language for evidence, tradeoffs, AI suggestions, confidence, recovery, and human review.
  • Design systems, prototypes, edge-case reviews, and product quality rituals that help a small team ship better work.

What we would look for

  • You have strong product and interaction judgment for dense workflow software.
  • You can make complex systems feel clear without flattening the work.
  • You can show prototypes, product surfaces, design artifacts, or shipping examples that reveal how you think.

Questions you would help answer

  • What should a product team trust to an AI teammate, and what should remain explicitly human?
  • How should Zentrik make evidence, recommendations, and review feel legible in daily work?
  • Which product details separate useful automation from generic output?
Zentrik workflow graph showing product context moving into agent work.

What the work feels like

Work here should feel direct, concrete, and high-trust.

We are a small team building a product for product teams. You should expect to work close to customers, code, evidence, product decisions, and the systems that help the company learn faster.

High ownership, small team

You should expect real scope, close collaboration, and enough context to make decisions without waiting for layers of approval.

Artifacts matter

We learn more from repos, prototypes, teardown notes, customer loops, growth systems, eval harnesses, and operating docs than from generic claims.

AI is part of the work

We use AI seriously, but the bar is better judgment, clearer systems, faster learning, and work that can be reviewed.

How we think about fit

Show us how you think and what you have made.

We do not need a polished application package to begin. Strong candidates can point to visible work and explain the choices, tradeoffs, and lessons behind it.

  • GitHub or public work artifacts

  • Agent harness or eval loop

  • Product or business judgment

  • Market or customer learning system

  • Infrastructure or MLOps system

  • Community or enablement motion

  • Personal workbench or knowledge system

Hiring process

Start with a short note and one useful artifact.

Tell us which role you are interested in and why. Include a repo, product teardown, prototype, GTM system, research synthesis, eval harness, shipped product, or short memo if it helps us understand your work.

Contact Zentrik
Tell us which role you want to explore.
  1. 1

    Send a focused note

    Tell us which role fits and include one or two artifacts: a repo, product surface, teardown, GTM system, research synthesis, eval harness, or short memo.

  2. 2

    Talk through your work

    We will talk about the role, the level of ownership, the systems you have built, and where your judgment is strongest.

  3. 3

    Review a real operating problem

    The useful signal is how you structure ambiguity, design feedback loops, and decide what is worth doing next.

  4. 4

    Define the first scope

    If there is a fit, we will shape an initial domain with clear ownership, expectations, and success criteria.