Oleh Talaver

Is there a part of your work that only happens because someone does it by hand?

That is the kind of thing I remove. I write software that takes over a process, measures one that nobody can see, or makes an AI feature checkable instead of merely confident — and I design the screens myself, so a small build does not need two people.

TELL ME THE PROBLEMSEE WHAT I BUILT

Problems I take on

stated the way you would say them

“We shipped an AI feature and now nobody can tell whether its answers are right.”

I build the checking: claims verified against the source they came from, evaluations with model judges, and guardrails that correct the output instead of hiding the failure. The useful deliverable is usually the evaluation harness, not the prompt.

CASE STUDY 1 →

“We cannot tell where the process actually stalls.”

I instrument the steps you care about rather than the ones the code happens to have, so you can see how often a process finishes and where instances get stuck. This is also the subject of my doctorate.

CASE STUDY 2 →

“Someone re-types the same data between two systems every week.”

I connect them, or build the small service that sits between them. The win is rarely the hours saved — it is that the two systems stop disagreeing with each other.

CASE STUDY 4 →

“The tool we bought assumes conditions we do not have.”

Sometimes the honest answer is to configure around it. Sometimes it is to build the narrow thing that fits. I will tell you which, and I have done the second one more than once.

CASE STUDY 3 →

“It works, but it looks like nobody cared.”

I do the interface and the visual work myself — layout, type and the actual screens, not only the code. On a small build that removes an entire person from the project.

CASE STUDIES →

“Only one person understands this system, and it is not you.”

Tests, documentation, and a release process somebody else can run. I hand over software that does not need me afterwards.

CASE STUDY 5 →

If what you have is none of these, say it in your own words anyway. Half of this work is deciding what the problem actually is, and that part happens before you have paid anything.

Case studies

COMMISSIONEDNOBODY PAID FOR IT
2023 —TYPESCRIPT · NESTJS · LLM

An AI agent that edits a course while you watch

PROBLEM
An e-learning platform needed authoring help from a language model that users could trust: suggestions arriving live, in the document, with a way to tell a good answer from a plausible one.
BUILT
A course-authoring agent with real-time edits over WebSocket, a multi-provider SDK across OpenAI, Mistral, AWS Bedrock and ElevenLabs, prompt management, phased evaluations judged by models, and guardrails that correct their own output. Alongside it, R&D on hybrid retrieval with source-aware routing and conflict detection.
SINCE THEN
Part of 500+ merged pull requests across 70+ repositories on that engagement. The client is not named.
2023 —OPENTELEMETRY · GRAFANA

Telemetry across thirty-plus services

PROBLEM
A microservice platform where nobody could say what was slow, or whether a business process had actually completed. Traces answered which service called which, and stopped there.
BUILT
OpenTelemetry tracing and metrics rolled out to more than thirty services through a shared service SDK that also carries logging, auth, messaging and the AI clients, with Langfuse and Grafana on top for model and service observability.
SINCE THEN
Ongoing. The same question — what telemetry cannot tell you about a business process — became my dissertation topic.
2025 —ELECTRON · TYPESCRIPT

A presenter for a church with no internet

PROBLEM
A Sunday service needs different content on four screens at once, run by a volunteer who changes most weeks. Every tool available assumed one projector and a live connection.
BUILT
«Показ»: a desktop application that caches everything from the planner beforehand and drives four synchronised outputs from one laptop, with phones joining over a short PIN to advance slides from the stage. Single click previews, double click goes live — the inverse of every media tool, and the only arrangement volunteers did not get wrong.
SINCE THEN
In service since 2025 across forty releases. Handover to a new volunteer is still two minutes.
2023 —NODE · TYPESCRIPT

One planner instead of four documents

PROBLEM
Service plans, song lyrics, their revisions, sermon outlines and media lived in separate documents, and nobody could tell which copy was current.
BUILT
A web planner with revision history and AI helpers, so a correction made on Saturday is what appears on Sunday, and the presenter reads from the same source.
SINCE THEN
In weekly use since 2023 at a church in Zhytomyr.
2024 —TYPESCRIPT · PYTHON

Software that can be changed while someone depends on it

PROBLEM
A self-hosted personal assistant I use daily and also need to keep modifying. Breaking it on a Tuesday is not acceptable.
BUILT
Multi-agent workspaces with messaging intakes and telemetry, behind a release train and a merge gate: changes are staged, rehearsed and rolled back automatically when they fail. A separate toolkit provisions the machines it runs on — rootless containers, encrypted backups to two providers, restores that have actually been tested.
SINCE THEN
Running daily since 2024. A failed release has never reached the running copy.

Screenshots come from fixture data. Nothing on this site links to a live service that holds other people's information.

How it goes

FIRST, FREE

You describe it, I ask questions

One call. It often ends with me saying the problem is smaller than you thought, or that it is not a software problem at all.

THEN, WRITTEN DOWN

A scope and a price

What will exist at the end, what will not, and what it costs. Fixed price when the scope holds still, a weekly rate when it cannot.

EVERY WEEK AFTER

Something you can run

Working software weekly, not a status report. At the end you get the tests, the documentation and a release process you can run without me.

Writing

Nothing published here yet. The peer-reviewed papers are on the experience page, with their DOIs.

Behind all of that: self-employed since 2023, two years at Easygenerator before it, a PhD at Zhytomyr Polytechnic on telemetry and business processes, and three courses I teach there.

THE WHOLE RECORD →