Software & Applied AI Engineering / Dmitry Popov

I build software for teams that need to find an answer, make a decision and act on it. I take responsibility for the whole path, from the screen an operator uses to the backend, the release and the checks the next engineer can run.

Three ways to work with me

Repair a workflow that drops or duplicates work
Send one failed event and the outcome you expected. I trace it from input to destination, fix the failing step and replay the same case. We agree what should happen if a request arrives twice or the downstream service goes offline. Your team gets the fix, a regression test and a way to see which records still need attention.

Make search and AI answers trustworthy on your data
Bring a question your assistant gets wrong and the document that should settle it. I check what was indexed, which passage was retrieved and which part of the answer it supports. The first delivery can cover one collection and a small set of agreed questions. We check the cited passage, what happens when the source changes and when the assistant should say it has insufficient evidence. I report the misses alongside the fixes.

Ship an operator-facing feature
Pick one job someone currently does by hand. I build the path they need across the interface, backend and services it touches. We walk one real scenario through to completion, including a case that needs human review. I hand over the release, the checks and instructions for operating it. We choose metrics that help the owner act, such as failed deliveries awaiting retry or questions that returned no supporting passage.

Work you can inspect

Flowdesk is my independent workflow demo with fictional leads and a CRM simulator. Run the recovery demo. A repeated webhook is blocked, an approved delivery fails, and a retry leaves one destination record. The event history shows what happened at each step.
https://flowdesk.rokenshi.com/case

On Daedro I work on source processing, retrieval and AI-provider integration. In a small offline search check I changed a sample returns policy from 14 to 30 days. The next search found the revised passage. Then I asked about an opened parcel. Search returned a rule about unopened parcels. A support assistant needs a separate check before it can use that passage to answer the question.

Starting a paid milestone

Send one anonymised example, the expected result, and your budget and delivery window. I will reply in writing with a proposed scope, acceptance checks, price and handover. If the cause is still unclear, we can agree a paid diagnostic first. It ends with a reproducible case, findings and a scoped next step.

Implementation starts once the agreed deposit is received or the milestone is funded. We agree service costs, revisions and the support period in writing. Briefs, updates and handover can all happen in writing. Please keep credentials and personal customer data out of the initial brief.

Telegram  https://t.me/AllArgsConstruct
Email     rouronikenshi@gmail.com