Mirtilo IO · Independent software engineering consultancy

Evidence-led software engineering for safer change.

I design, build and document backend software, architecture decisions, quality practices and releases. I present professional experience and public projects with clear limits on what each can show.

Abstract illustration of connected software systems
Clearer links between systems, teams and decisions.

Where I can help

Safer change needs more than code.

Architecture, implementation and release need to tell the same story. I make decisions explicit, build useful slices and leave tests, documentation and evidence for the next step.

01

The system boundaries have become hard to explain.

02

A technical decision needs to become a testable product slice.

03

A release needs to leave signals, documentation and a clear next step.

Three pillars

Decisions that reach delivery.

See the three pillars →
01

Architecture & modernisation

Clarify boundaries, compare options and set an incremental route the team can explain.

View details →
02

Software delivery

Turn a decision into a backend or product slice with code, tests and a maintainable handover.

View details →
03

Quality & release

Make tests, CI/CD, accessibility, security and release evidence visible and repeatable.

View details →

How the evidence is built

Clarity before commitment.

The person and the proof

Senior judgement, close to delivery.

I bring more than 15 years of hands-on experience across Java, distributed systems, enterprise platforms and engineering improvement. The timeline outlines my professional experience; Formatloom and Max Bid document decisions and implementation I can show publicly.

Next step

Explore the experience and projects before you decide.

Review the professional experience, public projects, their limits and technical decisions. If there is a fit, contact is a next step — not the only way to evaluate the work.

Explore experience & projects →