PERMISSION/PROTOCOL
Back to careers

Founding role area

Compliance Engineering Advisor / Operator-in-Residence

Help translate emerging AI-agent risk into authorization patterns that compliance, audit, legal, security, and executive teams can trust.

Why this role matters

Most AI governance language is too vague for the moment we are entering. Enterprises do not just need principles. They need control surfaces: who can authorize an agent action, what evidence is captured, when humans must sign, when policy can clear an action, and when an action must be denied.

This role helps make Permission Protocol credible to the people responsible for governance, audit, legal exposure, and regulated operations. It connects emerging AI-agent risk to controls that organizations already understand.

What you will shape

  • How Permission Protocol maps agent actions to recognizable control patterns.
  • Buyer-facing language for auditability, signer-of-record, retention, and human approval.
  • Practical frameworks for deciding which agent actions require human authorization.
  • Role-specific narratives for CCOs, CFOs, CISOs, legal leaders, and compliance operators.
  • Feedback from regulated workflows into product and policy design.

What strong candidates bring

  • Experience in compliance, audit, risk, legal operations, regulated workflows, security governance, or enterprise controls.
  • Ability to translate abstract AI risk into practical approval and evidence requirements.
  • Familiarity with how organizations prepare for scrutiny: audits, reviews, incident response, board questions, or regulator-facing processes.
  • Strong communication with both technical and non-technical stakeholders.
  • Healthy skepticism toward governance theater.

What to send

  • A LinkedIn profile, resume, portfolio, or relevant work sample.
  • Three to five lines on the background that maps you to this role area.
  • A short note on where you think agent authority, governance, or enterprise adoption is going.

How we work

  • We make controls practical enough to be adopted.
  • We avoid vague responsible-AI language when a concrete authorization primitive is needed.
  • We treat evidence and accountability as product requirements.
  • We build for serious organizations without making the product feel bureaucratic.

This role is strongest for people who want

  • Practical controls work that connects policy, audit, product, and implementation detail.
  • Clear language that turns AI governance risk into concrete authorization requirements.
  • Direct collaboration with engineers and product decisions that shape the authority layer.

Start the conversation.

If this role maps to the future you want to help shape, send your background and tell us where you think agent authority is going.

Send background for compliance track