Founding Engineering Operator — Deployment & Infrastructure at Okren

Amsterdam-based preferred. Remote possible for the right person in Europe. Pre-seed. Flexible starting structure. Senior paid role expected after funding.

Okren is building the separate check before AI takes an important action.

AI is moving from answering questions to taking actions. It can now move money, trigger workflows, approve access, change records, place trades, and interact with live infrastructure.

A bad answer is one problem. A bad action is another.

The problem is not that AI acts. The problem is that the system making the move is often also the system approving it.

Okren restores that separation.

Before a consequential action executes, Okren evaluates the proposed move and returns one of four deterministic verdicts:

Allow. Block. Constrain. Escalate.

We already have unusual technical depth and live proof in financial conditions: thousands of governed decisions across live financial infrastructure, with full reconstructability. The next step is turning that proof into something serious customers can deploy, trust, and scale.

That is the role.

This is not a generic CTO role. It is a founding engineering operator role for someone who knows how to turn rare architecture into repeatable infrastructure.

The core question:

How do we make Okren deployable for 10 serious customers without the original architect needing to personally carry every deployment?

What you would own

Your job is to make Okren transferable. That means:

* documenting the core architecture

* mapping the current deployment process

* reducing founder and architect dependency

* creating the first customer onboarding flow

* defining production-ready Okren v1

* building deployment checklists and integration notes

* joining early technical buyer conversations

* preparing the system for security, reliability, and implementation review

* deciding what should be standardized and what must stay custom

Your first job is not to manage a team. Your first job is to make future engineers and customers able to work with the system.

What success looks like in six months

* the system is no longer only understandable by its original architect

* the core architecture is documented

* the deployment path is mapped

* the first customer onboarding process exists

* we know what can be standardized, what must stay custom, and what cannot be touched yet

* customer technical conversations are easier, sharper, and more credible

* Okren feels less like founder magic and more like infrastructure

Who this is for

This is for someone who has helped take a hard technical product from early proof to real customer deployment.

Strong signal if you have worked in: financial infrastructure, crypto or Bitcoin infrastructure, trading systems, security infrastructure, authorization or policy systems, platform engineering, developer infrastructure, enterprise AI infrastructure, or any system where a wrong action has a real cost.

You are likely right for this if you can work close to the architecture and close to the customer; explain complex systems without flattening them; talk to technical buyers without overselling; work with a rare architect without trying to replace what makes the system unusual; and build directly, not just manage.

Most importantly: you believe autonomous systems need independent authorization before consequential action. That is not a values statement. It is the product.

Who this is not for

This is probably not right if you mainly want a management role; need a large team before you can be useful; want a high salary immediately; want a polished company with everything figured out; are excited by AI generally but not by infrastructure; have only built standard SaaS applications; or are more interested in title than responsibility.

Compensation

Okren is pre-seed and preparing for a raise. This is not a normal salaried full-time role today.

The right person would likely begin through one of these structures: paid sprint, advisory role, part-time founding role, project-based engagement, equity-based founding path, or contractor-to-founding-role path.

After funding, this becomes a senior paid role at founding engineering, VP Engineering, or CTO level with meaningful equity.

We are looking for someone who sees the category early and wants to help build it before the market fully names it.

How to apply

Send a short note answering:

1. What hard technical product have you helped make deployable for real customers?

2. Why does AI action need independent authorization before it executes?

3. Tell me about a time you reduced founder or architect dependency on a hard technical system.

No generic cover letter needed. We care more about how you think than how polished your application looks.