Senior backend engineer·Co-founder, Qarz-Qurs & Himoyam·Founder, Bahola·Tashkent (UTC+5)

Jamshiddin IsmailovBackend engineer for systems where every number must be right.

Ledgers, netting, refunds, identity checks. I build PHP backends where the record must match the money: a person-to-person debt ledger live on the App Store, the business-automation system a retail company has run on every day since 2023 — and now two more products: Himoyam, an insurance platform that starts with agents' commissions, in production since September 2026, and Bahola, appraisal automation for real estate and all types of vehicles, still in development.

Role
Senior backend engineer
Stack
PHP · Laravel · Symfony · Postgres
Domain
Lending · Ledgers · KYC
Based
Tashkent · UTC+5
Engagements
A few scoped ones a year
Now · Sep 2026 — 01
Qarz-Qurs

Co-founder · backend engineer · a person-to-person debt ledger, live on the iOS App Store (Uzbekistan) · Android in development, business accounts planned

Now — 02
Himoyam

Co-founder · an insurance platform for Uzbekistan, starting with commissions for insurance agents · in production · himoyam.uz

Now — 03
Bahola

Founder · appraisal automation for real estate and all types of vehicles · early stage · bahola.uz

Now — 04
Retail automation

Contract client · CRM, contracts, documents and integrations for a retail company · since Sep 2023 · in daily use

01 — Work

What I have built.

01.1 Jan 2026 — present Co-founded · live on the iOS App Store (Uzbekistan)

Co-founder · backend engineer — the idea and the iOS app are my co-founder's; we build it together

A person-to-person debt ledger for private individuals. Friends, family and groups record who owes whom; every debt, expense and cash handover counts only after both parties confirm it. Kim kimga qarzdor — ikkala tomon tasdiqlagan yozuv — who owes whom, a record confirmed by both parties.

  1. My part is the backend: data model, API, auth, background jobs, realtime, automated tests, CI and deploys.
  2. An obligation-and-allocation ledger as the single source of truth — balances are derived, never stored as facts; opposite obligations between two people net automatically.
  3. Direct and group scopes, equal or custom splits, expense bundles, multi-currency balances, due dates and reminders.
  4. Cash handovers that count only once the receiver confirms; phone OTP sign-in, then MyID identity verification before any financial action.
  5. Realtime websocket events (Laravel Reverb), push notifications, queue workers, scheduler, admin panel.
PHPLaravelPostgreSQLRedisReverbMyIDDockerGitLab CI

Technical or integration questions about Qarz-Qurs: write to me. Commercial partnerships: via qarz-qurs.uz.

01.2 Sep 2023 — present Contract client · in daily use

Business automation for a retail company

Contract · CRM, contracts, documents and integrations — built from scratch and maintained since September 2023

The system a retail company runs on: clients, contracts, orders, calls, generated documents and marketing analytics in one place, replacing spreadsheets and manual steps. Client not named until they agree; references on request.

  1. Clients as individuals and legal entities; contracts with document generation; orders.
  2. Call and communication log; reminders for follow-ups.
  3. Sync of CRM orders to Yandex Metrika conversions, including historical imports; sync errors are persisted, not lost.
  4. Upgraded in place across major framework versions, while the business kept using it.
In use
daily, since 2023
Reference
on request
PHPLaravelVueInertiaTailwindPostgreSQLDocker
01.3 Sep 2026 — present Co-founded · in production

Co-founder · I build the platform end to end; the insurance side of the business is my co-founder's

An insurance platform for Uzbekistan, starting with the agents who sell the policies. An agent sees what they have sold and what they have earned, and can withdraw it to their own bank card; the operator team runs the rest from an admin panel. Mening himoyam — my protection.

  1. My part is the whole platform: data model, backend, the Vue and TypeScript frontend, automated tests, CI and Docker deploys.
  2. Sales are picked up automatically and become each agent's earnings, to the whole so'm — each one counted exactly once however many times it is processed, and corrections are taken back off.
  3. Commission rates are the operator team's to set, and every change is on the record: who changed it, when, and what it was before. Each credit keeps the rate it was calculated at.
  4. Payouts to an agent's own bank card through a licensed payment provider. The card is confirmed by a code the bank sends to the phone number it has on file — the platform never issues that code and never learns what it should be, only whether it was right — and it stores no card number in the clear.
  5. Paying twice is worse than paying late: a payout claims its earnings in the database before anything leaves, goes to the provider under a key of its own, and is settled once. An unclear answer is never a reason to send again — a scheduled job asks the provider what became of it and records the outcome.
  6. An agent's figures update on screen the moment the money moves; the operator panel shows, agent by agent, what is earned, what is still owed and what is already on its way. Agent and admin areas in Uzbek and Russian.
PHPLaravelVueTypeScriptInertiaPostgreSQLRedisHorizonWebSocketsDockerGitLab CI

In production since September 2026. There are no public pages: himoyam.uz is for agents and the operator team, so the link opens the sign-in page.

01.4 2026 — Founder · early stage

Bahola

Founder · own product — building the backend now

Appraisal automation for real estate and all types of vehicles in Uzbekistan. The goal is one flow from request to finished report: the system prepares the calculations and drafts the document, and a certified appraiser reviews and signs every value. Early stage — the backend is in development.

02 — Work with me

A few scoped engagements a year.

Bounded work that fits next to a full-time role — each item below is something I have already shipped. Outside my working hours, with no employer code or data, and never for a product that competes with my employer.

02.1

Ledger design and review

An obligation ledger where balances are derived, never stored; two-party confirmation; automatic netting; multi-currency balances. Built for Qarz-Qurs — or reviewed in your system before it costs you a customer.

02.2

A KYC or partner integration

MyID identity verification as the gate before any financial action (Qarz-Qurs). CRM orders synced to Yandex Metrika with historical imports and persisted errors. Integrations that fail loudly, not silently.

02.3

Settlement and cash-handover logic

Who paid whom, when it counts, and what the balance is afterwards — the part of a money product where a rounding error is a customer complaint. Shipped in Qarz-Qurs.

02.4

Business automation for a company

Clients, contracts, orders, document generation, call logs, analytics integrations — the system a company actually runs on, then owned long-term: upgrades in production, static analysis, Docker and CI. The retail automation system: kept current through in-place upgrades, in daily use since 2023.

Write a few lines about the system, the stack, and what must not go wrong: [email protected]

03 — About

The record has to match reality.

I am a backend engineer in Tashkent. The main stack is PHP — Laravel and Symfony; when a project calls for it, I take on the JavaScript side as well, frontend and backend — TypeScript, Vue, Next.js, Node. Most of what I build is money-shaped: installment loans and their refunds, debts between friends, insurance agents' commissions, appraised values, contracts and orders. The same question comes up in all of it — does the record match what actually happened, and can someone check?

I prefer to own a backend end to end and to ship systems someone else can operate: Docker images that build the same everywhere, pipelines that deploy with one click, static analysis on every change. Boring tools, chosen on purpose.

Laravel is where I work most, not the boundary. I have delivered the same kind of system in Symfony with a domain-driven layout — a domain layer kept clean of the database — and the TypeScript client that sits on top of it.

This page is about the work itself. The career record — roles, employers and dates — lives on LinkedIn, or in the résumé: PDF in English · in Russian.

Principles
P1

The ledger is the source of truth.

Balances are derived from obligations and allocations, never stored as facts. Every value traces back to something a person can check — a confirmed entry, a signed document, a stored calculation.

P2

Automation drafts; a person signs.

Software can calculate, suggest and remind. What counts is confirmed by the people it concerns — both parties in Qarz-Qurs, a certified appraiser in an appraisal.

04 — Stack

Boring on purpose.

T.1Backend
  • PHP
  • Laravel
  • Symfony · Doctrine ORM
  • PostgreSQL · MySQL
  • Redis · Horizon queues
  • Reverb / Pusher websockets
  • PHPUnit · phpstan · pint
T.2JavaScript
  • TypeScript
  • Next.js · React
  • Vue · Inertia
  • Node.js
  • Tailwind
  • Livewire · Filament
T.3Infrastructure & integrations
  • Docker & Compose
  • GitLab CI/CD · Nginx · Cloudflare
  • MyID biometric KYC
  • B2B partner APIs
  • Yandex Metrika · PDF · Excel
05 — Contact

Tell me what the product does and where the money moves.

Two reasons to write: a scoped backend engagement — lending flows, ledgers and settlement, KYC and partner integrations, a business-automation system for your company, or a backend that needs an owner — or a technical question about Qarz-Qurs. Send a few lines about the system, the stack, and what must not go wrong; I will tell you plainly whether I am the right person for it.

[email protected]