Build the future of
agentic experience
We're defining a new category of work. These roles don't map cleanly to traditional UX, engineering, or operations. They are hybrids. They are the future.
Agent System Designer
Design how software behaves when it starts acting on behalf of users. Work at the intersection of product thinking, system design, and human-AI interaction.
Agent Systems Engineer
Build the systems that power agentic behavior. Implement execution systems where agents plan, act, and interact with real tools and data.
Agent Operator
Run, optimize, and scale agent systems in the real world. Own performance, reliability, and outcomes across production agent deployments.
How we actually work
Worth knowing before you write to us, because it suits some people and not others.
Founder-led, partner-delivered
Engagements are led personally rather than staffed out to a bench. You will be close to the client, the decision and the consequence — which means less shelter than a large agency and considerably more say.
Fixed scope, fixed price
Our engagements are scoped and priced before they start — a two-week audit, a three-week sprint, a four-week readiness review. No open-ended retainers dressed as projects, and no billing by the hour.
We publish the method
The heuristics, the playbook, the field guides — all free, all open. If you would rather keep your thinking proprietary, this will frustrate you.
Remote-first, EU-anchored
Based in Warsaw, working across Poland, the UK and the wider EU in English and Polish. On-site where the work needs a room; otherwise asynchronous and written.
Writing is the job
Most of what we deliver is a document someone has to act on: a scorecard, a capability design, a roadmap with named owners. If you think clearly but write vaguely, the work will be harder than you expect.
The professional keeps responsibility
We design systems that hold context and earn autonomy incrementally — never ones that decide on someone's behalf without recourse. That conviction shapes what we will and will not build.
You will probably like it here if
- You have shipped something agentic and know where it broke
- You are comfortable saying "we would talk you out of this" to a paying client
- You would rather define a category than compete inside a crowded one
- Ambiguity reads as interesting rather than unsafe
You probably won't if
- You want a large team, a clear ladder and a defined remit
- You prefer specification handed down rather than argued out
- You would rather build the model than design what it is allowed to do
- Publishing the method openly strikes you as giving away the advantage
How to apply
There is no form and no ATS. Write to us directly with the role in the subject line, a short note on what you have built or designed, and — most usefully — one thing on this site you think is wrong. That last part tells us more than a CV does.
We read everything and reply to everyone, including no. If none of the three roles fits but the category does, say so anyway; the shape of this team is not settled.
New to the discipline? Start with What is agentic user experience?, the ten heuristics, or about auxfirst.
A New Category of Work
We believe software is evolving from tools into agents that act on behalf of users.
This creates a new layer of work:
If you're excited by ambiguity, systems thinking, and shaping how humans and AI collaborate — you'll feel at home here.