Principal Engineer, Confidential AI

<div class="content-intro"><p><strong data-stringify-type="bold">About OPAQUE</strong><br>OPAQUE is the Confidential AI company. Born from UC Berkeley’s RISELab, we solve the core challenge blocking AI adoption at scale: security concerns about data leaks or compliance violations. OPAQUE provides verifiable privacy and governance for AI so organizations can safely run models, agents, and workflows on their most sensitive data. Its Confidential AI platform delivers verifiable runtime governance backed by cryptographic proof that data, models, and agent actions remain private, governed, and compliant with approved policies throughout every AI workflow. This extends traditional data governance tools with real runtime verification, enabling teams to responsibly deploy AI using their most valuable proprietary data, and move from pilot to production 4-5X faster. Customers and partners include ServiceNow, Anthropic, Encore Capital, Accenture, and leaders across high tech, financial services, insurance, and healthcare.</p>
<p>Learn More at <a href="http://opaque.co/">Opaque.co</a></p>
<p>Read about our Values at <a href="http://opaque.co/about">Opaque.co/about</a></p>
<p> </p></div><h2><span style="font-weight: 400;">ABOUT THIS JOB</span></h2>
<p><span style="font-weight: 400;">We are hiring a Principal Engineer to bring the open agent-governance stack we help lead into the heart of the platform. The open projects (the Agent Governance Toolkit, Confidential MCP, Agent Manifest, and TRACE, under agentrust-io) define how autonomous agents prove what they did. You will harden them into our two commercial layers: OPAQUE Agent Control™, the software governance layer built on AGT that controls every agent, and OPAQUE Confidential Core™, the hardware and TEE layer that proves every action. Software helps you build; hardware helps you scale; verifiable AI requires both.</span></p>
<p><span style="font-weight: 400;">This is a deeply technical, customer-facing engineering role that spans software and silicon. You will own the integration end to end, ship it as platform offerings like OPAQUE Confidential MCP™ and OPAQUE Confidential Agents™, represent OPAQUE in the standards communities defining this space, and carry the work from open-source spec to scaled, attested product.</span></p>
<p> </p>
<p><span style="font-weight: 400;">What you will do</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">Own the integration of the open agent-governance stack (Confidential MCP, Agent Manifest, TRACE) into OPAQUE Agent Control and OPAQUE Confidential Core, bound to hardware attestation and TEEs (AMD SEV-SNP, Intel TDX, NVIDIA Confidential Computing).</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Make policy enforcement and verifiable evidence run inside the TEE: a governed agent workflow that emits a single hardware-rooted, independently verifiable record.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Production-harden and scale the confidential agent path across multi-cloud Confidential Containers (AKS, GKE) to enterprise reliability and latency targets.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Ship platform offerings such as OPAQUE Confidential MCP and OPAQUE Confidential Agents on top of that foundation.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Work directly with customers to turn their hardest confidential-AI problems into platform capabilities.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Represent OPAQUE as a technical contributor in the foundations that standardize this work (Agentic AI Foundation, CoSAI): upstream contributions, spec influence, and credibility in the community.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Make the open-source-to-product calls: what to harden, what to keep experimental, what to upstream.</span></li>
</ul>
<p> </p>
<p><span style="font-weight: 400;">What we are looking for</span></p>
<ul>
<li style="font-weight: 400;"><span style="font-weight: 400;">10+ years building production systems, with depth across both application software and low-level/systems work.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Hands-on confidential computing / TEE experience (SEV-SNP, TDX, NVIDIA CC) and fluency in attestation (RATS, EAT, measured boot, key release on attestation).</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Strong cryptographic engineering fundamentals.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Fluency in Go and/or Rust; comfort in Python and the agent frameworks (LangChain, LangGraph, CrewAI, AutoGen).</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Experience scaling distributed systems on Kubernetes, ideally multi-cloud.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Demonstrated customer curiosity: you start from the user’s problem and work back to the architecture.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">A track record in open source and standards: shipped meaningful upstream work and can represent a company technically in a community.</span></li>
<li style="font-weight: 400;"><span style="font-weight: 400;">Bonus: prior work in agent governance, policy engines (Cedar), SBOM/supply-chain, or verifiable credentials.</span></li>
</ul>