Prague, CZ - CETAvailable now

AI automation engineer - operations and platforms

The work runs itself.

Agents that clear the queue. Platforms that end the spreadsheet. Interfaces your team lives in.

Support triaged by hand. Operations on spreadsheets. Sixteen systems that don’t talk to each other. I replace work like that with systems that run themselves, solo, in weeks rather than quarters.

By hand → runs itself

2K+

Support tickets automated
inside six weeks

170+

Hours of manual triage
removed in six weeks

16

Scattered systems
unified in one place

1K+

Automated tests across
shipped systems

Most of the work your team does by hand is a system
nobody has written yet. I write those systems.

(01)

If someone reads and sorts every incoming request by hand

Autonomous agents

Agents that do real operational work: triage, routing, reconciliation, follow-up. They own the queue end to end and escalate only what genuinely needs a person. Not chatbots.

(02)

If the real source of truth is a spreadsheet nobody trusts

Internal platforms

One system where there were sixteen. Warehouse, support, finance and analytics behind a single interface, so the spreadsheet stops being the source of truth.

(03)

If the internal tool is the one everyone avoids opening

Production interfaces

React and Next.js front ends on top of it all. The screens your team opens every morning, built to production standard rather than prototype standard.

(01)

The queue reads itself

Replacing manual ticket triage with an agent that reads, classifies, routes and resolves on its own.

(02)

Six weeks, not six months

Kickoff to production in six weeks, with a narrow slice doing real work in week one.

(03)

What still reaches a person

Genuine exceptions only. Over 2,000 tickets closed in the first six weeks without anyone touching them.

2,000+

Tickets automated

170+ hrs

Manual triage removed

6 wks

Kickoff to production

drop: agent dashboard / ticket flow

(01)

Sixteen logins, one screen

Warehouse, support, finance and analytics behind a single interface.

(02)

The spreadsheets went with them

Removing the informal layer that had been filling every gap between the sixteen systems.

(03)

Ask it anything

A chat layer that answers across all sixteen sources at once, built solo in six weeks on more than a thousand tests.

6 wks

Solo, to production

16

Systems connected

1,000+

Tests in CI

drop: platform UI / system map

(01)

Thirty-four blocks

A block based page builder on Next.js and Payload, typed end to end.

(02)

Structure they control

Page structure, SEO and routing back in their hands, after a platform that offered them none.

(03)

No developer in the loop

Marketing composes and publishes without filing a ticket.

34

Blocks in the builder

0

Devs to publish a page

aimsapi.com (opens in a new tab)

The aimsapi.com home page, with its reference track and lyric search entry points

(01)

Four techniques, one sequence

An orchestrated intro, mouse driven parallax, a drag carousel and scroll snapping.

(02)

Fast on a laptop

Motion primitives and modern CSS rather than a 3D scene, so it holds up on hardware that is not a workstation.

strv.com/vision-pro (opens in a new tab)

The Vision Pro concept site, a spatial app card floating in a rendered room

(Next) Unwritten

Your operation goes here.

One paragraph about your operation is enough to start.Start the conversation

(02.1) - Shipped forEvery one of them came through a referral.

VilgainE-commerce & nutrition

ForbesMedia & publishing

STRVSoftware & design agency

AIMSMusic-AI API platform

References available for every engagement on this page.

I automate the work I used to do by hand. That is the part you cannot learn from a spec.

I spent my first years in IT and end user support. I know what operational work actually feels like from the inside, because I did it: the queue, the escalations, the same question asked forty times a week.

I taught myself to build, moved into engineering at STRV inside a year, and spent the next four years shipping production front ends and leading delivery. Now I build the systems that remove the work I used to do by hand.

Jonas Arden — The person you brief · Prague, CZ

(A)

One person,
accountable

No agency layer, no handoffs, no juniors. The person you brief writes the code, ships it, and answers for it in production.

(B)

Judged by
software

The first slice ships in days, not quarters. You judge progress on running software in your environment, never on decks.

(C)

Tested and
yours

Over 1,000 automated tests, type checks and CI gates. Everything lands in your repository, yours from the first commit.

(D)

Contract, not
headcount

Remote from Prague, overlapping EU and US hours. No hire, no ramp-up - the contract ends cleanly when the work is done.

(01)

You write one paragraph

What still runs by hand, and roughly how much of it. That's enough to start - no brief, no spec, no discovery workshop.

(02)

You get a plan back

What I'd build first, what it replaces, how long it takes and what it costs. In writing, within a few days. Not a sales call.

(03)

Something runs in week one

A narrow slice, in your environment, doing real work. You decide whether to continue on running software, not a proposal.

(04)

It ends cleanly

Documented, tested, in your repository, handed to your team. No dependency on me, and no notice period to negotiate.

hi@jonasarden.com

The work runs itself.