Skip to content
Tech Stack

The toolchain behind shipped AI agents.

Senior software engineer with 15+ years in production banking, fintech, and telecom. Since 2024, focused on production AI agents and evals: multi-agent orchestration, MCP tools, RAG, model routing, LLM-as-judge evaluation, regression benchmarks, guardrails, and PII filtering.

Stockholm, Sweden 15+ years shipping software Full CV ›
01  /  AI Agents & Orchestration

Multi-agent systems with sharp tool boundaries, deliberate routing, and tested handoffs.

  • LangChain
  • DSPy
  • MCP servers & skills
  • Multi-agent systems
  • Agent orchestration
  • Agent routing
  • Tool & function calling
  • LSP
  • Model routing per task
  • Prompt engineering
  • AI agent security checks
02  /  LLMs, Fine-Tuning & Training

Picking the right model for the job, then squeezing cost and latency with fine-tuning and distillation.

  • Frontier & open-weight LLMs
  • Fine-tuning
  • Model training
  • Knowledge distillation
  • Unsloth
  • Google Colab
  • Self-hosted GPU inference
03  /  Evals, RAG & NLP

Golden datasets, LLM-as-judge gates, and guardrails so agents stay reliable in production.

  • LLM-as-judge
  • Golden datasets
  • Trajectory & outcome scoring
  • ML experimentation pipelines
  • NLP
  • RAG
  • Hybrid search
  • Embedding models
  • Vector databases
  • Reranking
  • AI red-teaming
  • Prompt-injection defense
  • Output guardrails
  • PII filtering
04  /  Infrastructure & Serverless

Cheap edge compute when it fits, real clusters when it does not.

  • Cloudflare Workers
  • Durable Objects
  • Kubernetes
  • Google Cloud
  • Docker
  • REST
  • gRPC
  • CI/CD
  • PostgreSQL
05  /  Languages & Frameworks

Python and TypeScript drive most agent work today. Kotlin and PHP cover the production mobile and backend tail.

  • Python
  • TypeScript
  • Kotlin
  • Java
  • PHP
  • Flutter
  • Laravel
  • Go (fundamentals)
  • Rust (fundamentals)
Proof, not promises

Production systems shipped

A snapshot of AI agents and platforms running today, drawn from Royan AB, SBAB Bank, and ParkUp Inc.

AI pricing optimization system

ParkUp Inc. · 600K+ users · +30% revenue (~$400K/yr)

Multi-agent orchestration with RAG, embeddings, and model routing. Contributed to a 30% annualized revenue lift.

Agent eval frameworks

Royan AB

Golden datasets, trace replay, deterministic checks, LLM-as-judge scoring, regression benchmarks, and pass/fail release gates.

Bank-side AI tooling

SBAB Bank · AI forum (5 members) · +40% coding efficiency

MCP servers, agent skills, and model platforms (including AWS Bedrock) in the bank's workflows. Tuned coding agents with LSP servers, RTK, and CLI tools for 40% more efficient AI-assisted coding at lower token use.

PushClub.io

Royan AB · in progress

Developer-focused social platform where AI agents support onboarding, profile enrichment, matching, content workflows, and moderation tooling.

Order-interpretation agent

Royan AB

LangChain pipeline converting natural language into validated JSON with schema validation, judge-based gating, and structured fallback handling.

Embodied 3D AI assistant

Royan AB

Real-time, low-latency LLM agent loop with STT, MCP tools, TTS, and gesture sync. Output guardrails and prompt-injection checks on the deployed voice agent.

Mindset

How I think about agents

The non-negotiables I bring to every project, from a one-off internal tool to a multi-agent system in front of paying users.

  1. 01

    Reliability before novelty.

    A slow, boring agent that always works beats a clever one that fails 10% of the time.

  2. 02

    Evals are the release gate.

    No eval, no merge. Golden sets and LLM-as-judge catch regressions before users do.

  3. 03

    Smaller, task-specific models when they win.

    A fine-tuned 7B can beat a frontier model on cost, latency, and accuracy for narrow tasks.

  4. 04

    Cost-aware model routing.

    Cheap models for easy turns, strong models for hard ones, judges only where they pay back.

  5. 05

    Tool design over prompt cleverness.

    Most agent failures are tool design failures. Tight schemas and small surfaces beat long prompts.

  6. 06

    Guardrails and PII filtering by default.

    Input checks, output guardrails, and prompt-injection defense belong in the first commit, not the second incident.

Sound like the stack you need?

I build production AI agents through Royan AB and talk to teams hiring senior AI engineers. Email is the fastest way in.