Careers at Zentrik / 8 open roles

All roles

Forward-Deployed Product Engineer

Work with strategic customers to connect their sources, workflows, and decision rituals to Zentrik.

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

Customer product

Zentrik evidence graph with source-backed product context.

Work context

Roles connect to real product systems

Hiring brief

Forward-Deployed Product Engineer

Customer implementation, product discovery, and workflow design

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

Customer product / Builder role

Forward-Deployed Product Engineer

Customer implementation, product discovery, and workflow design

A customer-facing product engineering role for someone who can build, explain, and earn trust in the same week.

Work with strategic customers to connect their sources, workflows, and decision rituals to Zentrik.

Start a conversation

A concise note is enough to start.

What you would own

  • Customer deployments that connect Zentrik to real sources, workflows, teams, and decision rituals.
  • Reusable patterns for implementation, data mapping, trust-building, integration design, and adoption evidence.
  • Tight loops between what customers need, what the product should do next, and what the team can safely automate.

What we would look for

  • You can build, explain, debug, and earn trust in the same week.
  • You are comfortable with product discovery, customer calls, light architecture, scripting, integrations, and AI-assisted shipping.
  • You turn customer-specific work into reusable product and implementation patterns.

Questions you would help answer

  • What should the first 30 days of a strategic Zentrik rollout look like?
  • Which customer-specific workflows should become product features or templates?
  • How do we prove value without turning implementation into bespoke services?
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.