Senior Engineer - Agentic Systems

About this role

Building the Intelligence Layer for How Pretzl Works
Pretzl is redefining what a B2B marketing agency can be. As a B2B Technology-and-People-as-a-Service (TaPaaS) agency with approx. 350 people globally, we're not just advising clients - we're building the technology that transforms how businesses connect with their buyers.

We are now creating an Agentic Layer across the business: a platform that can safely connect AI systems with the context, tools, knowledge and workflows people need to do useful work.

The Role

We’re looking for a Senior Engineer to join our newly forming Agentic Systems squad and help us shape, build and operate this platform from the ground up.

This is an early-stage, greenfield engineering opportunity. You will join while the first use cases, architectural hypotheses and prototypes are being explored, but before the production architecture, delivery model and technical boundaries have been settled.

You’ll need to be confident operating in that environment: turning an ambitious vision into a practical technical direction, making sensible decisions with incomplete information, identifying what needs to be learned first, and delivering narrow working slices rather than waiting for every future requirement to be resolved.

This isn’t a role for someone who wants to be handed fully specified tickets and churn out code. We need someone who wants to get involved while problems are still being clarified, workflows are being understood, trade-offs are being discussed, and the right platform shape is still emerging.

You’ll be the first fully allocated technical contributor within a new team that will grow with you to up to 3 fully allocated engineers, as well as additional resource pulled in from other pods. You’ll own substantial parts of the platform from early shaping through to production, help establish its technical foundations, contribute strongly to architectural direction, mentor other engineers, and raise the standard for how the team plans, builds, reviews and operates its work.

You will not be expected to arrive with every answer. You will be expected to create clarity, make good decisions, test assumptions quickly, and take meaningful ownership rather than waiting for somebody else to define the path.

This is a fully remote, UK-based role with the expectation to travel to London approximately once per month. We are not currently hiring this role as an overseas remote position.

What We’re Building

The Agentic Layer will give AI agents and automation workflows safe, useful context about how Pretzl operates: who people are, which clients and projects matter, what work is in flight, what has already been agreed, what has changed, and which information can appropriately be used for a particular task.

This is not a generic chatbot, a thin wrapper around an LLM, or simply a vector database connected to company documents.

The platform needs to understand business entities, relationships, ownership, permissions, project state, decisions, risks, workflows and source systems. It must be able to load the right context for a task without exposing information the user is not entitled to access.

We expect to use external models, frameworks, connectors and infrastructure where that makes sense. The capabilities we need to own are the parts that are specific to how Pretzl works: our context and memory models, permission boundaries, business events, source-of-truth decisions, evaluation criteria and rules around how agents can use information and take action.

The first version will not attempt to create a universal agent for the whole business. We will begin with a small number of valuable, clearly defined workflows where we can understand the users, context, systems, permissions, approval points and measures of success.

What You’ll Actually Do

Greenfield Technical Ownership

• Help turn the Agentic Layer vision into a practical, evolvable technical direction

• Own substantial areas of the platform from early shaping through to production operation

• Identify the important architectural decisions, assumptions, risks and unknowns rather than waiting for them to be surfaced by somebody else

• Work out what needs to be built now, what can be deferred, and what should be bought, reused or integrated

• Establish sensible technical foundations without over-engineering a platform before its first workflows have proved value

• Turn broad platform ambitions into narrow, testable vertical slices that create real business value

• Make architectural decisions within your domain and clearly articulate the trade-offs

• Design systems that are secure, observable, testable, maintainable and appropriately scalable

• Lead debugging and incident investigation for complex issues, looking for systemic causes rather than treating symptoms

• Write code that serves as an example for the rest of the team

Agentic Systems, Context and Integrations

• Build production-grade TypeScript and Node.js services, APIs and internal tools

• Design context-loading approaches that identify what an agent needs to know for a specific user, client, project or workflow

• Help shape models for business entities, events, decisions, risks, workflows and durable memory

• Build permission-aware access across connected systems and document repositories

• Create reliable integrations with workplace and business platforms such as Slack, Microsoft Graph, SharePoint, OneDrive, Outlook, Teams, Snowflake, Jira, Figma and internal systems

• Design agent workflows that can call approved tools, maintain state, handle failures and pause for human approval where required

• Apply agentic patterns such as tool calling, structured outputs, retrieval, Model Context Protocol and human-in-the-loop workflows pragmatically

• Build clear boundaries around tool access, credentials, identity, sensitive data and external actions

• Establish tracing, logging and auditability so that we can understand what an agent…