Careers at Zentrik
8 senior roles
Agent-native brains
All roles

The Adoption Brain

Turn customer learning into a community and success system that helps teams adopt AI-native product management with proof, confidence, and better judgment.

Read role detailsStart a conversation
Strategic opening

The Adoption Brain

Customer learning, community, enablement, adoption, and expansion

A chief customer officer and community-led growth shape, expressed as one hands-on operator.

Turn customer learning into a community and success system that helps teams adopt AI-native product management with proof, confidence, and better judgment.

Start a conversation

A useful first note shows how you think and what you have made.

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, proof libraries, and customer stories around AI-native product work.
  • Feedback loops from customer conversations, support, community signal, adoption data, and renewal risk into product and go-to-market 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 teams experimenting with AI and teams changing how work actually gets done.

Questions you would help answer

  • How should teams learn a new product operating system without feeling like they are just learning another tool?
  • What community should exist around AI-native product management before the category is settled?
  • How can customer signal become adoption help, product insight, trust-building content, and stronger retention each week?
What the work feels like

The product is the operating layer for better product decisions.

The role is not to add AI decoration to old workflows. The role is to preserve product intent from customer evidence to shipped work, while making every loop more inspectable, more reliable, and easier for a human team to trust.

Product intent stays human

AI can accelerate the work, but the reason to build still comes from evidence, taste, tradeoffs, and accountability.

Visible systems beat claims

We look for artifacts: GitHub repos, workbenches, eval notes, customer loops, market systems, prototypes, and operating docs.

The harness matters

Great AI-native work depends on context, evals, guardrails, review loops, and proof that the next cycle gets sharper.

Zentrik agent workflow graph showing product context moving into agent work.
How we think about fit

Range matters, but judgment matters more.

We are more interested in visible systems of work than in claims of AI fluency. Strong candidates can show how they create leverage without confusing output volume for customer value.

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

Show us the system behind the work.

A strong note could include a GitHub repo, product teardown, prototype, GTM system, research synthesis, eval harness, personal workbench, shipped product, or a short memo about where you think Zentrik should go.

Contact Zentrik
Tell us which role fits your strongest proof.
  1. 1

    Send a proof artifact

    Share a repo, product teardown, prototype, GTM system, research synthesis, eval harness, customer system, or short memo.

  2. 2

    Work through the role shape

    We will talk about the domain, 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 the initial domain clearly enough that you can start creating leverage quickly.