Ionel Roiban

How I work

Working systems, not slideware

One senior engineer, end to end: diagnose the real problem, write the architecture down, build with evals before features and human gates on side-effects, then run it in production until your team owns it.

Proven in production

The same approach, across very different systems

Cloud

Multi-region AWS migration at 99.99% uptime — with SOC II visibility and audit trails

Read case study →

Web

Publisher digital transformation: page loads from 8+ seconds to under 2

Read case study →

Email

Deliverability crisis fixed with self-hosted Mautic — 31% open rates, 4.2% CTR

Read case study →

Compliance

Pharmaceutical B2B platform with audit trails for controlled-substance orders

Read case study →

Fleet · own ops

My own operation runs as a Claude agent fleet — shared memory, dispatch channels, verified writes

See the live practice →

By the numbers

Measured on live systems

99.99%
Uptime
multi-region AWS · US-East / US-West
<2s
Page loads
down from 8+ seconds
31%
Email open rates
rebuilt infra · 4.2% CTR
~40%
Infrastructure cost cut
on cloud migration
20yr
Cloud, data & ML
engineer → architect → manager
16yr
On GitHub
shipping in the open since 2009

* Every figure comes from a named engagement — details on the case studies page.

The process

Four steps, no mystery

The same arc whether it’s a two-week audit or a year-long build — only the depth changes.

01 · Diagnose

A frank conversation and a look under the hood: what’s actually broken, what’s actually possible, and what it’s worth — including an AI-readiness read on your data, tooling, and risk posture.

  • Free first conversation
  • AI-readiness read: what your stack will actually support
  • Honest scoping — including "don’t build this"
  • Clear go / no-go recommendation

02 · Design

Architecture in writing before code: components, data flows, failure modes, eval criteria, and where the human gates go.

  • Written architecture doc
  • Evals defined before features
  • Cost model before commitment
  • Audit-trail & compliance design where relevant

03 · Build

Hands-on engineering with the pipelines that keep it honest: automated testing, code review, deploys — and for agent work, eval suites and approval gates from the first commit.

  • Working software over status decks
  • Automated test & deploy pipelines
  • Human gates on every side-effect
  • Blue-green deploys with DNS failover

04 · Operate

Monitoring, alerting, evals drift watched in production, and iteration — then a documented handoff when your team is ready to own it.

  • Dashboards & automated alerts
  • Weekly written review while I operate it
  • Process monitoring on every automation
  • Clean, documented handoff

Guardrails

Nothing writes without a witness

Agent work gets one extra rule the rest of the stack already follows: every side-effect passes a gate. Evals before vibes; approvals before writes.

  • Agents propose; approved actions execute; everything is logged
  • Denied paths are still data — refusals feed the eval suite
  • Scoped credentials: an agent gets the least access that does the job
  • Kill switch and audit trail, from the first deploy
Fig. 04 — the human gateevery side-effect
approve · execute · logdeny · log · learn

Working with me

What an engagement feels like

You work with me

No account managers, no handoffs to a junior team. The person who scopes the work is the person who builds and runs it.

Direct channel

Email that gets answered — usually within a business day — and working sessions instead of ceremony.

Everything written down

Architecture docs, decision records, and runbooks — the paper trail that survives me leaving.

Your accounts, your code

Work happens in your cloud accounts and your repositories. No lock-in, no hostage infrastructure.

Standards

Built to survive an audit

SOC II experience

Designed real-time visibility and audit trails supporting SOC II on a multi-region AWS migration.

HIPAA-relevant work

Pharmaceutical B2B platform with full audit trails for controlled-substance orders.

Security training

Cisco Ethical Hacker certified (Feb 2026) — the attacker’s view informs the architecture.

Audit trails by default

Systems ship with the logging and traceability a regulator, acquirer, or your own future team will ask for.

Get the system out of the meeting and into production

One senior engineer who designs it, builds it, and runs it — with the written record to prove how it works.