Careers at Zentrik / 8 open roles

All roles

Customer Adoption Lead

Own onboarding, education, community, and customer success for teams changing how product work gets done.

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

Customer

Zentrik evidence graph with source-backed product context.

Work context

Roles connect to real product systems

Hiring brief

Customer Adoption Lead

Onboarding, enablement, community, and customer success

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

Customer / Leadership role

Customer Adoption Lead

Onboarding, enablement, community, and customer success

A senior customer and community role for someone who can help teams change how product work gets done.

Own onboarding, education, community, and customer success for teams changing how product work gets done.

Start a conversation

A concise note is enough to start.

What you would own

  • The customer success motion across onboarding, implementation, education, product adoption, lifecycle health, expansion, and renewal learning.
  • Community programs, customer education, practitioner content, reference libraries, and customer stories.
  • Feedback loops from customer conversations, support, community signal, adoption data, and renewal risk into product and growth decisions.

What we would look for

  • You have meaningful community and customer success experience in SaaS, especially around workflow change, adoption, or category creation.
  • You understand product leaders, PMs, founders, operators, and customer-facing teams well enough to teach without flattening their context.
  • You can tell the difference between a team trying a tool and a team changing how work actually gets done.

Questions you would help answer

  • How should teams learn Zentrik without feeling like they are just learning another tool?
  • What community should exist around better product work before the category is settled?
  • How can customer signal become adoption help, product insight, trust-building content, and stronger retention each week?
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.