Skip to content
Olimjon Akhmadjonov

Data Scientist & Software Engineer · Tashkent, Uzbekistan

I design and build secure, well-architected software — and bring AI automation and multi-agent systems into your processes.

Turnkey projects for businesses — from a first review of the task and the architecture to launch and support. Telegram bots and stores, CRM, point of sale, platforms and AI assistants, with security by default and code your team can run without me.

See case studies

4+ years building production software · 2+ years in applied AI · Works in English, Russian and Uzbek · Available for projects and consulting

Career: Datamicron · 4DX · Fizmasoft · ITGO

Selected work

Systems that hold up in production.

Platforms and services I have designed and built — commerce, credit decisioning, fintech and AI systems. Client and product names are withheld; the engineering is real.

Design first

Architecture before code.

A polished interface on top of a system nobody thought through is a liability, not a product. Before development starts I work out the domain, the data, the architecture and how the system fails — and write the decisions down. That is why these projects work in production, not just in a demo.

systems designed and built
10
automated tests across them
2,000+
design and operations documents
300+

  1. Domain and requirements

    Processes, roles, rules and edge cases are mapped before the first line of code — contradictions are resolved on paper, where they are cheap.

  2. Architecture and data

    Module boundaries, the data model, integration contracts and ADRs with the alternatives that were rejected.

  3. Failure and security

    What happens on an outage, an attack or bad data — and how we find out. Security is part of the design, not a final checklist.

  4. Verification

    Tests, evaluation sets and CI gates that keep the system from breaking quietly as it grows.

Consumer-electronics retailer (Uzbekistan)NDA

Telegram commerce platform with installment checkout

An online store that lives inside Telegram — catalogue, installment checkout, SMS sign-in, payments, an operator bot and a full back office — in production for a consumer-electronics retailer.

  • Python
  • FastAPI
  • PostgreSQL
  • SQLAlchemy

Read case study

Installment retailer, risk departmentNDA

Credit decision engine for installment lending

A scoring and decision service that turns a risk department's process diagram into versioned, executable policy — two gates, limit rules, a manual-review queue and strict control over paid credit-bureau checks.

  • Python
  • FastAPI
  • Pydantic
  • structlog

Read case study

Own SaaS product (Uzbekistan & CIS)

AI analyst SaaS: ask your database and documents in plain language

A multi-tenant product where business owners connect a database or upload documents and get numbers, tables and charts from questions in Russian, Uzbek or English — with every SQL query checked before it runs.

  • Python
  • FastAPI
  • PostgreSQL + pgvector
  • sqlglot

Read case study

Fintech product for small businesses (Uzbekistan)NDA

Financial analysis and financing platform for small businesses

A rewrite of a live fintech product: statement analysis with 14 ratios and a score, a catalogue of 595 loan offers from 31 banks, report import from tax forms, and an AI consultant that only explains numbers the engine computed.

  • Python
  • FastAPI
  • PostgreSQL
  • Redis

Read case study

Confidential document workflows (R&D prototype)

Offline document intelligence for Uzbek-language archives

A fully local RAG system for long Uzbek PDFs — Latin or Cyrillic, including scans — that answers questions with page citations and generates insights, without a byte of data leaving the machine.

  • Python
  • FastAPI
  • Docling
  • Tesseract OCR

Read case study

Retail company, analytics teamNDA

Natural-language assistant for corporate databases

An internal tool that lets a team ask several production databases questions in plain language and get the answer, the table and the exact SQL — behind a safety gate that makes changing the data impossible.

  • Python
  • FastAPI
  • PostgreSQL + pgvector
  • MySQL

Read case study

Also designed and built

What I build

Web platforms, internal tools, APIs and AI-powered products.

For companies, startups and public-sector teams — from a first version to a system your team runs for years.

AI automation & agents

LLM agents and multi-agent workflows that take routine work off your team's plate — with guardrails, an audit trail and human approval where it matters.

Typical deliverables

  • Workflow design
  • Agent orchestration
  • System integrations
  • Accuracy evaluation set

Assistants that answer from your documents (RAG)

Assistants that answer from your own documents and data in Uzbek, Russian or English — accurate, with sources, and safe to put in front of customers or staff.

Typical deliverables

  • Ingestion pipeline
  • Search & ranking over your documents
  • Chat interface
  • Quality monitoring

Backend platforms & APIs

The core system behind your product or internal tool — APIs, integrations, accounts and permissions — structured so new features don't break old ones. Python/FastAPI, PostgreSQL.

Typical deliverables

  • Architecture document
  • OpenAPI-documented API
  • Tests & CI/CD
  • Deployment runbook

Data engineering & analytics

Pipelines, dashboards and models that turn raw data into answers your team can act on.

Typical deliverables

  • ETL / ELT pipelines
  • Data models
  • Reporting dashboards
  • ML prototypes

Every engagement ships with documentation, tests and a handover, so your team can run and extend the system without depending on me.

How I work

A calm, transparent process.

Five steps, each ending in a written output that you keep.

Always included

  • Architecture document
  • Source code with tests
  • CI/CD pipeline
  • Deployment runbook
  • Security checklist
  • Knowledge-transfer session
  • Full ownership of code, infrastructure and accounts

  1. Understand

    Goals, constraints, users and risks, in your own words. We agree on what "done" means before any code is written.

    Output:Scope, risks & estimate

  2. Architect

    Modular structure, data model, security model and a delivery plan. Decisions are written down so they can be questioned and revisited.

    Output:Architecture document

  3. Build in increments

    Typed code, tests and reviews from day one. You see working software every week, not a demo at the end.

    Output:Working software, weekly

  4. Harden & verify

    Security review, edge cases, load testing and monitoring — plus an evaluation set for the AI parts, so quality is measured, not assumed.

    Output:Test & security report

  5. Ship & support

    Deployment, documentation and a knowledge-transfer session — then either a clean handover to your team or ongoing support on a retainer. Your choice.

    Output:Runbook & handover

Stack

Tools I reach for.

Chosen per project, not by habit — proven and boring where reliability matters, current where it clearly pays off.

Languages
PythonTypeScriptSQL
Backend
FastAPIPostgreSQLSQLAlchemyRedisCelery / ArqDocker
AI / LLM
Anthropic & OpenAI APIsLangGraph / LangChainRAG pipelinespgvector / QdrantEvaluation & guardrails
Data
pandasscikit-learnAirflowdbt
Frontend & Ops
ReactGitHub ActionsLinuxCaddy / nginx

About

Olimjon, in short.

I'm Olimjon Akhmadjonov, a data scientist and software engineer based in Tashkent. I graduated from INHA University (School of Computer and Information Engineering) and started out as a Python backend engineer, building APIs and services that had to be reliable from day one.

For the last 2+ years I've focused on applied AI — document assistants, agent workflows, AI chat products and data science. What I care about is making it useful in production: answers people can verify, agents that leave decisions with humans, and systems your team can run without me. I apply the same discipline I learned on the backend: clear architecture, security, tests and documentation.

I work directly with businesses, startups and public-sector teams — in English, Russian or Uzbek — as the person who designs, builds and hands over the system. If that sounds like you, I'd be glad to talk.

Location
Tashkent, Uzbekistan
Education
INHA University in Tashkent · SOCIE
Languages
English, Russian, Uzbek
Availability
Available for projects and consulting
Engagements
Projects · Retainers · Consulting

Experience

From backend to applied AI.

Four roles in four years — from first Telegram bots to production AI systems. The same path the projects above are built on.

  1. July 2024 — present

    Tashkent, Uzbekistan

    Data Scientist · Datamicron

    AI-driven automation: designed and deployed RAG systems, complex LLM workflows and multi-agent architectures (LangChain, LangGraph, LangSmith); prompt engineering for reliable structured outputs; AI data-extraction tools; a chat copilot that builds charts from ontology-driven data sources; shipped as FastAPI and Flask backend services; occasional model fine-tuning.

    PythonLangChainLangGraphLangSmithFastAPIFlask

  2. June 2023 — May 2024

    Tashkent, Uzbekistan

    Python Backend Developer · 4DX

    Medical information system for a private clinic with ~10 user roles (doctors, lab technicians, accountants, cashiers, nurses, warehouse staff), each with its own logic and pages; a Telegram bot delivering test results to patients; unit tests for the API; server administration and Docker containerisation.

    PythonDockerTelegram Bot API

  3. June — August 2022

    Tashkent, Uzbekistan

    Backend Developer · Fizmasoft

    Two large public-services projects: the public site and a large administrative panel for tracking and managing recruitment processes.

    Python

  4. December 2021 — April 2022

    Tashkent, Uzbekistan

    Backend Developer · ITGO

    First role: Telegram bots (e-commerce and HR), administrative panels for websites, landing pages, and CRM/ERP systems for automating business processes.

    PythonTelegram Bot API

FAQ

Questions clients ask first.

Short, honest answers. Anything missing — ask the assistant or write to me.

Who owns the code, infrastructure and accounts?

You do — fully. Everything is created in your accounts or transferred at handover: source code, CI/CD, servers, domains and third-party services. Full ownership is a standard deliverable of every engagement, not an extra.

Can you sign an NDA?

Yes. A large part of my work is under NDA — that is why some case studies on this site are anonymised. I can sign yours or provide a standard mutual NDA before we discuss any details.

How long does a project take?

A focused assistant or automation pilot typically reaches production in 8–12 weeks. Larger platforms are delivered in phases, with working software every week — you see progress from week one, not a demo at the end. A precise estimate comes out of the scoping step.

How do we work together remotely?

Remote-first from Tashkent (UTC+5), with comfortable overlap for European and Central-Asian time zones. Weekly demos, decisions in writing, a shared tracker you can open any time. On-site in Tashkent is possible by agreement.

What happens after launch?

Your choice: a clean handover — documentation, runbook and a knowledge-transfer session for your team — or ongoing support on a retainer. Either way the system is built so your team can run it without me.

How is payment structured?

I work as a registered individual entrepreneur in Uzbekistan — with a contract and invoices. An upfront payment starts the work; the rest is split into milestones, each paid on acceptance, so payment follows working results. Currency — whichever suits you. Public-sector procurement procedures are fine.

Can you join an existing codebase or team?

Yes. It starts with a short audit — architecture, security, tests — and a written list of findings. Then we agree what to improve or which features to build. The rule: the system ends up more maintainable than I found it.

In which languages can we communicate?

English, Russian and Uzbek — meetings, correspondence and documentation in whichever your team prefers.

Contact

Let's build something reliable.

Tell me about your project — a few sentences is enough. I reply within 1–2 business days.

No newsletters, no spam — just a reply.

Start a project

Tell me about it — a few sentences is enough.

I reply within 1–2 business days. Prefer email? oakhmadjonov.uz@gmail.com