About Wrapbox

I'm building Wrapbox — security infrastructure for AI agents. AI agents now write to company repos, databases and payments, and nothing checks the action before it runs. Wrapbox does: every agent action is allowed, constrained, held for human review, or blocked before execution enforced on the device, on the network, and at a gateway in front of company systems.

A working prototype exists end-to-end, the company is a Delaware C-Corp, and we're raising pre-seed with paid enterprise pilots as the goal.

The role

I'm looking for a Co-Founder & CTO to own the technical side of the company the way I own product, design and business. At this stage that means three things, and they're all the job:

Build. The core of Wrapbox is deep systems software: kernel-level enforcement on macOS (Endpoint Security), Windows (minifilter drivers) and Linux (eBPF/LSM); network and gateway enforcement; agent isolation; filesystem and process controls; identity and device trust; bypass resistance. You'll set the architecture and write the code that everything else depends on.

Deploy. Our first customers are design partners, and at pre-seed the founders are the deployment team. You'll run technical demos and POCs, understand each customer's environment, integrate Wrapbox with their MDM (Jamf/Intune), SSO, GitHub, AWS, databases and MCP servers, and debug what breaks — the way forward-deployed engineers work at Palantir and OpenAI, except you'll own the product you're deploying.

Grow. Founder-led sales is how security infrastructure gets its first pilots. You won't carry a quota and you don't need a sales background — but you'll join me in rooms with CISOs and platform leaders, run technical discovery, and help carry deals from first call to signed pilot.



If the idea of explaining what you built to the person buying it excites you rather than drains you, that's the signal.

You might be a fit if

You've shipped real systems or security software — endpoint agents/EDR, kernel extensions or drivers, eBPF, network proxies, sandboxing, or zero-trust infrastructure — in Rust, C, C++ or Go. You understand trust boundaries and how attackers think about bypass. You don't need every technology listed; you need to have genuinely built and shipped at this level, and to want the customer-facing half of the founder job, not just tolerate it.

This is explicitly not a GRC, compliance, SOC-analyst, or security-management role, and not a fit if you want to code in isolation.

How we'd work

Remote, open globally. Solid English matters — we'll do architecture, product, customers and fundraising together. Initial involvement can be part-time while we establish founder fit, building toward full-time.

Compensation

Co-founder equity with standard vesting — no salary until financing supports it (I'm not taking one either). Equity, scope and the full-time transition are discussed openly with the right person.

To apply — cover letter required. Please cover these 3 areas:

BUILD — What systems/security software have you personally built and shipped? Which parts did you own end-to-end? (kernel/drivers, eBPF, endpoint agents, proxies, sandboxing — Rust/C/C++/Go)

DEPLOY — Your experience integrating or deploying software in real customer environments — MDM, SSO, cloud, databases, POCs, troubleshooting rollouts.

GROW — Your experience in front of customers — demos, discovery calls, pre-sales, or helping close a deal or pilot. If limited, that's okay — tell me why you want this part of the job.

And a few lines on why this problem pulls you in.

[email protected] · wrapbox.io · linkedin.com/company/wrapbox/

📌 Co-Founder & CTO — Wrapbox ( Security Infrastructure for AI Agents (India)
🏢 Wrapbox
📍 India