We are building an enterprise AI platform in which AI agents operate business applications through their user interface, the way a person does. It runs inside customers' own environments, including on-premises and air-gapped sites. We are a small, senior team working in two-week sprints towards a first production release in December 2026.
You will lead the design and build of our agent harness
: the framework around the model that turns open-weight LLMs into agents that plan, act, recover, and can be trusted in production. You will also build the agent that operates web applications through the browser. This is the hardest technical problem we have, and you will set the technical direction for the AI engineering team.
- Design and build the agent harness:
- the agent loop
- tool registry and tool execution
- context management and compaction
- memory
- permission and approval gates
- sandboxed execution
- retries and recovery
- Build the agent that operates web applications, using vision-language models and browser automation (Playwright, Chrome Dev Tools Protocol) in isolated browser sandboxes.
- Coordinate specialised agents that work together on a task. Decide where the model should be in control and where code should be (behavioural vs procedural).
- Make every agent run traceable and replayable: structured logs, traces (e.g. Langfuse, Open Telemetry), and step-level replay.
- Integrate self-hosted open-weight models through an OpenAI-compatible gateway, and expose agent capabilities as MCP tools.
- Work with the Backend, Full-stack and Dev Ops engineers to run agents reliably in production.
- Set engineering standards for the AI team, review designs and code, and mentor the L4 AI engineers.
- 10+ years of software engineering, including 2+ years building LLM-powered applications.
- Has designed and built an agent harness or a substantial agent framework that ran in production or a serious pilot.
- Strong Python and/or Type Script , with solid systems design: event loops, state machines, concurrency, failure handling.
- Hands-on experience with browser automation (Playwright, Puppeteer, or Chrome Dev Tools Protocol).
- Deep knowledge of the core AI topics below.
- A track record of technical leadership: owning architecture decisions, mentoring engineers, and raising engineering standards across a team.
- Contributions to an open-source agent framework or harness.
- Experience with vision-language models for UI agents (e.g. Qwen-VL, UI-TARS) or agent-oriented browser frameworks (e.g. Stagehand, browser-use).
- State-machine or workflow engines (e.g. XState, Temporal, Trigger.dev).
- Self-hosting open-weight models (vLLM, SGLang) on Kubernetes and GPUs.
- Building AI systems for on-premises, air-gapped, or regulated environments.
We expect every AI Engineer on our team to be able to discuss these topics with confidence. For this role we expect depth in all of them.
- How LLMs work:
- the Transformer architecture (attention, positional encodings, feed-forward layers), tokenisation, autoregressive decoding and sampling, and KV caching
- the training pipeline: pre-training, SFT, preference optimisation such as RLHF and DPO, and RL with verifiable rewards
- reasoning models and test-time compute;
Mixture-of-Experts, quantisation, and serving - failure modes: hallucination, prompt injection, context rot, and reward hacking
- Agentic AI:
- agent patterns:
ReAct, plan-and-execute, reflection, orchestrator–worker, and evaluator–optimiser - tool design and context engineering: retrieval, memory, compaction, and sub-agents
- the trade-offs of multi-agent systems
- safety controls: permissions, sandboxing, human-in-the-loop, and prompt-injection defence
- Protocols:
- Model Context Protocol (MCP): hosts, clients and servers;…
(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).