Open role · Context Architect
Design the system the agents work against.
You design the structure that lets AI agents do real work in regulated environments — what they reuse, what they have to pass before output lands, where a person reads. Most weeks you sit between domain owners and engineers and produce the written design they build against.
Mission
What the role does and why it matters here.
The Context Architect designs the structure that lets AI agents do real work in regulated environments without producing output a human has to redo. You design a context layer once for each workflow, alongside the validators that check every step against it. Most weeks you work alongside the founder and domain owners on live regulated-enterprise work, and write down the design the build team ships against. The output lives in the engagement document and in the codebase.
Responsibilities
What you would own.
- Design the reusable context layer
For each workflow, you define the structured context an agent step can draw on. You make the architecture decision in writing; it lands in the engagement document and does not get relitigated.
- Define the validator set
Working with compliance, platform, and engineering owners at the client, you specify which checks must pass before an agent run can land and which are advisory. Validators end up as code, written by the AI Engineer, to a spec you author.
- Set approval boundaries
You decide where the agent stops and a person has to read. Defined per workflow, documented before the engagement starts, so those decisions do not get made under pressure later.
- Maintain the audit trail spec
Every agent step records what it used, which validators ran, and what the reviewer saw. You specify that record so an auditor can reconstruct the decision from it.
- Scope and phase each engagement
You write the phasing plan at the start: which workflow ships first, what it has to demonstrate before the next one begins. Not at the retrospective.
How you think and work
Six traits the work demands.
These roles don't filter on industry pedigree. They filter on disposition. The traits below name what the work actually demands; the patterns underneath them are what we'd read in an application as evidence those traits are real.
How you think and work
Agentic intuition
You read agents the way a manager reads a direct report — when to trust the output, when to interrupt the run, when to take the wheel back.
You've watched an automated process produce confident output that was wrong, and you intervened before it landed.
Critical thinking
Confident-sounding output gets the same scrutiny as anything else — your own work included.
You've replaced a stakeholder's stated requirement with the better one underneath it.
Curiosity
You pull on threads. You read outside the lane. You follow a question past the first plausible answer.
You'd rather understand why a workflow is stuck than write the design someone asked for.
Agency
You move without being told. You decide, ship, own the call. No one has to write the playbook for you.
You've written the design that didn't exist because waiting was not going to produce one.
Systems thinking, long view
You see how the parts connect — and where this goes in three years.
You design the model knowing the third workflow built on top of it will surface the real test.
Leadership instinct
You orchestrate work across humans, agents, and stakeholders. You switch register between a Linear ticket, an architect call, and a senior bank room in the same day without losing what you came in to say.
You've held a design steady while engineers, compliance, and operators pulled in different directions.
Shape of work that maps
You've designed a structure — data model, taxonomy, API contract, ontology — that other teams were required to use, and defended it against pushback from outside engineering.
You've shipped into an environment where the cost of being wrong was real. Regulated industries count. So does anything where a bug wasn't just bad UX.
You've written design documents that replaced meetings — artifacts engineers built against, not retrospectives written after the fact.
You've sat between technical and non-technical stakeholders and held a decision steady through both rooms.
Regulated-industry experience is not required. Curiosity about it is. The work is shaped by patterns the founder earned in regulated-bank production.
Logistics
How the role is set up.
- Engagement type
- Contract or full-time. Contractors run on a defined engagement scope and can convert to full-time. Full-time runs on a yearly review with a quarterly written check-in.
- Location
- Remote. Lucentive is EU-based; we expect at least four hours of overlap with CET on a working day. Travel for engagement kickoffs is occasional, not weekly.
- Compensation
- Discussed in the written exchange. We pay at market rate for senior people in regulated industries; the band depends on contract or full-time and on location.