Skip to content

Backend Developer · Node.js & TypeScript

Backend systems that keep real businesses running.

Two years of commercial experience building production systems with Node.js and TypeScript — a company-wide business ecosystem, ERP and HR platforms, installment and debt management, AI automation, and Telegram bots.

Currently
Backend Developer, Probox Group
Focus
APIs, data modeling, queues, integrations
Building professionally
Since 2024
Based in
Tashkent, Uzbekistan
Commercial backend experience
2 yrs
Companies and clients
4
Systems and bots shipped
10+

Core stack

Node.js · TypeScript · NestJS · PostgreSQL · Redis · BullMQ · Docker

01Selected work

Business systems built for daily operations.

6 products where I owned or contributed to the backend — data models, APIs, queues and scheduled workflows, and the integrations that connect them.

01 / 06

Probox Ecosystem

Enterprise platform · Installment phone retail

In development · Internal

The internal business ecosystem of one of Uzbekistan's largest installment phone retailers — finance, legal case management, customer relations, and HR in one platform.

Problem

Every department worked from its own view of customers, contracts, and payments. The business needed one consistent source of truth that all of them could build on.

My contribution

  • Designing domain models and module boundaries with NestJS and PostgreSQL so every department works from shared customer, contract, and payment data.
  • Building queue-based background processing and asynchronous workflows with Redis and BullMQ.
  • Developing modules across finance, legal case management, customer relations, and HR.

Key capabilities

  • Shared domain model
  • Module boundaries
  • Queue-based jobs
  • Cross-department data
System outline
  1. Entry
    • Finance
    • Legal
    • Customer relations
    • HR
  2. Service
    • NestJS REST API
  3. Modules
    • Customers
    • Contracts
    • Payments
    • Legal cases
    • Staff
  4. Async
    • BullMQ workers
    • Redis queues
  5. Storage
    • PostgreSQL
    • Redis
Simplified outline of the Probox Ecosystem backend — not a product screenshot.
Role
Backend developer · Probox Group
Status
In development · Internal
Year
2026
Stack
Node.js, NestJS, TypeScript, PostgreSQL, Redis, BullMQ, REST API
02 / 06

CarWashGo

SaaS · Business management

A car wash management platform that runs daily operations: orders, staff shifts, payroll, cash, and analytics — in production at carwashgo.uz.

Problem

Owners tracked washes, shifts, and payouts by hand. They needed one system for orders, staff compensation, and cash — with each role seeing only its own data.

My contribution

  • Designed the database schema and REST API for services, prices, orders, and customer and vehicle history.
  • Implemented employee and shift tracking with percentage-based salary calculation, so the owner no longer calculates payouts manually.
  • Built a finance module: cash desk, income and expenses, and reports per shift and period.
Show 2 more
  • Built an analytics dashboard: revenue by day, week, and month, wash counts, top services, and retention.
  • Configured owner, administrator, and washer roles, so each sees only their own data.

Key capabilities

  • Role-based access
  • Shift-based payroll
  • Financial reporting
  • Revenue analytics
System outlineDocker · Nginx
  1. Entry
    • React web app
    • Owner · Admin · Washer
  2. Service
    • NestJS REST API · JWT
  3. Modules
    • Orders & pricing
    • Shifts & payroll
    • Cash desk
    • Analytics
  4. Storage
    • MongoDB
  5. External
    • SMS API
Simplified outline of the CarWashGo backend — not a product screenshot.
Role
Full-stack developer · Freelance
Status
Live product
Year
2024–25
Stack
NestJS, React, MongoDB, Redux Toolkit, JWT, Docker, Nginx, SMS API
03 / 06

Dono AI

AI automation · Telegram & web

Team product

An AI-powered reminder system that turns text, voice, and even images into reminders delivered by message or automated phone call.

Problem

A reminder only helps if it reaches the person. Dono AI accepts requests in any form and escalates to a real voice call when a message is not enough.

My contribution

  • Implemented text-to-speech so user tasks become automated voice calls, and integrated AI-based audio processing for voice input.
  • Built image-reading logic that extracts structured data from uploaded images.
  • Designed REST APIs with Express.js, TypeScript, and PostgreSQL, with cron-based reminder triggers.
Show 2 more
  • Integrated the Telegram Bot API and telephony services.
  • Built subscription logic, payment-based activation, and background job processing.

Key capabilities

  • Voice & TTS calls
  • Image-to-data
  • Scheduled triggers
  • Subscriptions
System outline
  1. Entry
    • Telegram bot
    • Web app
  2. Service
    • Express.js · TypeScript API
  3. Modules
    • Reminders
    • Audio processing
    • Image-to-data
    • Subscriptions
  4. Async
    • Cron triggers
    • Background jobs
  5. Storage
    • PostgreSQL
  6. External
    • TTS API
    • Telephony
    • Payments
Simplified outline of the Dono AI backend — not a product screenshot.
Role
Backend developer · BEHAD LLC
Status
Team product
Year
2025–26
Stack
Node.js, Express.js, TypeScript, PostgreSQL, Telegram Bot API, TTS API, Cron Jobs
04 / 06

Nasiya

Fintech · Installment sales

No public link

An installment sales system that tracks customer debt, payment schedules, and upcoming payments — and reminds both sides before a due date.

Problem

Shops selling on installment need to know who owes what, when the next payment is due, and which accounts are overdue — without checking by hand.

My contribution

  • Developed customer and product records with installment sales, payment schedules, and automatic outstanding-balance calculation.
  • Built a daily background job that checks schedules, notifies the shop owner via Telegram, and sends customers an SMS before the due date.
  • Created overdue-payment and total-debt reports showing who owes what on a single screen.

Key capabilities

  • Payment schedules
  • Balance calculation
  • Daily reminders
  • Debt reports
System outline
  1. Entry
    • Shop owner
    • REST API
  2. Service
    • NestJS service
  3. Modules
    • Customers
    • Products
    • Payment schedules
    • Debt reports
  4. Async
    • Daily cron job
  5. Storage
    • PostgreSQL
  6. External
    • Telegram Bot API
    • SMS gateway
Simplified outline of the Nasiya backend — not a product screenshot.
Role
Backend developer
Status
No public link
Year
2025
Stack
Node.js, NestJS, PostgreSQL, Telegram Bot API, SMS Gateway, Cron Jobs
05 / 06

Argus

ERP · HR management

No public link

An employee management ERP focused on attendance, salary history, bonuses, and HR reporting.

Problem

HR teams need attendance, payroll, and bonuses in one system, with clear access boundaries between administrators and HR managers.

My contribution

  • Built attendance tracking with check-in and check-out and work-hour calculation.
  • Implemented salary history, payment records, and bonuses.
  • Created HR reports on activity and payroll, with role-based access for admins and HR managers.
Show 1 more
  • Designed a normalized PostgreSQL schema and optimized queries for fast data retrieval.

Key capabilities

  • Attendance tracking
  • Payroll records
  • Role-based access
  • Query optimization
System outlineDocker
  1. Entry
    • Administrators
    • HR managers
  2. Service
    • NestJS REST API · JWT
  3. Modules
    • Attendance
    • Salary history
    • Bonuses
    • HR reports
  4. Storage
    • PostgreSQL
Simplified outline of the Argus backend — not a product screenshot.
Role
Backend developer · Vintorum
Status
No public link
Year
2025
Stack
NestJS, Node.js, TypeScript, PostgreSQL, Docker, JWT, REST API
06 / 06

Perfume Store

E-commerce · Marketplace

No public link

A mobile-first perfume marketplace with a searchable catalog, cart and checkout, and an admin panel for the whole store.

Problem

Most of the store's traffic comes from phones. Customers needed fast browsing and checkout; managers needed to hear about every order immediately.

My contribution

  • Developed a product catalog with categories, brands, filters, and search, plus product pages with photos, descriptions, and stock.
  • Built cart and checkout with a manager notification for every new order.
  • Built an admin panel for products, categories, stock, prices, images, and order statuses.
Show 1 more
  • Built a mobile-first Next.js interface for phone-heavy traffic.

Key capabilities

  • Catalog & search
  • Checkout flow
  • Order notifications
  • Admin panel
System outline
  1. Entry
    • Next.js storefront
    • Admin panel
  2. Service
    • NestJS REST API · Prisma
  3. Modules
    • Catalog & search
    • Cart & checkout
    • Orders
    • Inventory
  4. Storage
    • PostgreSQL
  5. External
    • Manager notifications
Simplified outline of the Perfume Store backend — not a product screenshot.
Role
Full-stack developer
Status
No public link
Year
2025
Stack
Node.js, NestJS, PostgreSQL, Prisma, Next.js, TypeScript

Also built

Smaller production systems and Telegram bots delivered alongside the work above.

  • Debt & loan management · Vintorum

    Fintrack

    • Debt lifecycle for lenders: creation, tracking, partial payments, and full settlement.
    • Cron jobs that email debtors before due dates.
    • REST API with validation and error handling.

    NestJS · PostgreSQL · Nodemailer · Cron Jobs

  • Loyalty bot · BEHAD LLC

    MegaFarm Pharmacy Bot

    • QR-code user identification at the counter.
    • 1% cashback accumulation and redemption.
    • Admin panel for users, receipts, bonuses, and suspicious-activity detection.

    Express.js · PostgreSQL · Telegram Bot API

  • Subscription bots · BEHAD LLC

    Qadam Plus · LifePlanner · SSSAFE

    • Registration, subscription purchase, and payment flows for Qadam Plus and LifePlanner.
    • SSSAFE: licensed medicine support with order tracking and support workflows.

    Express.js · TypeScript · PostgreSQL · Telegram Bot API

02About

Practical engineering for operational problems.

I'm a backend developer specializing in Node.js and TypeScript. Over two years I've built a company-wide business ecosystem, ERP and HR platforms, installment and debt management, AI-powered automation, Telegram bots, and e-commerce — most of them running in production today.

I own features end to end: from the database schema and API contract to deployment and production support.

Technical profile

  1. 01Domain modeling and normalized PostgreSQL schemas
  2. 02REST API design with validation at the boundary
  3. 03Authentication with JWT and role-based access control
  4. 04Background jobs, queues, and cron-based workflows
  5. 05Telegram, SMS, payment, TTS, and telephony integrations
  6. 06Docker and Nginx deployments on VPS, with CI/CD

Languages

Uzbek
Native
English
B1
Russian
A2

Education

Najot Ta'lim

Foundation & Full-Stack Bootcamp

Nov 2023 — Oct 2024

03Technical skills

Tools I work with.

Grouped by where they sit in a system. Highlighted tools are the ones I use day to day; the rest I have shipped with in specific projects.

Backend
  • Node.js (daily use)
  • TypeScript (daily use)
  • NestJS (daily use)
  • Express.js
  • Prisma
Databases
  • PostgreSQL (daily use)
  • MongoDB
  • MySQL
  • Redis (daily use)
Async & integrations
  • BullMQ (daily use)
  • Cron jobs
  • Telegram Bot API (daily use)
  • SMS gateways
  • Payment flows
DevOps
  • Docker (daily use)
  • Nginx
  • PM2
  • Linux
  • VPS
  • CI/CD
APIs & tools
  • REST (daily use)
  • GraphQL
  • Swagger
  • Postman
  • Git
  • JWT (daily use)
  • RBAC
Frontend
  • React
  • Next.js
  • Redux Toolkit

04Experience

Where I've built things.

Four backend roles since late 2024, preceded by a year-long full-stack bootcamp.

  1. Mar 2026 — Present

    Probox Group

    Current

    Backend Developer

    • Probox Ecosystem
    • Developing the internal ecosystem of one of Uzbekistan's largest installment phone retailers — finance, legal, customer relations, and HR.
    • Designing domain models and module boundaries so every department shares consistent customer, contract, and payment data.
    • Building queue-based background processing with Redis and BullMQ.

    Stack: NestJS · PostgreSQL · Redis · BullMQ

  2. Sep 2025 — Mar 2026

    BEHAD LLC

    Backend Developer

    • Dono AI
    • MegaFarm
    • Qadam Plus
    • LifePlanner
    • SSSAFE
    • Built Dono AI: TTS voice calls, AI audio processing, image-to-data extraction, and cron-based reminders.
    • Shipped multiple production Telegram bots with registration, subscriptions, payments, and admin tooling.

    Stack: Express.js · TypeScript · PostgreSQL · Telegram Bot API

  3. May 2025 — Sep 2025

    Vintorum

    Backend Developer

    • Argus
    • Fintrack
    • Built Argus HR/ERP: attendance, salary history, bonuses, and role-based HR reports.
    • Built Fintrack debt management with partial payments and automated email reminders.

    Stack: NestJS · PostgreSQL · Docker · JWT

  4. Nov 2024 — Jun 2025

    CarWashGo

    Full Stack Developer · Freelance

    • carwashgo.uz
    • Designed and built a car wash management platform, now live in production.
    • Delivered shift-based payroll, a finance module, analytics, and role-based access.

    Stack: NestJS · React · MongoDB · Docker

  5. Nov 2023 — Oct 2024

    Najot Ta'lim

    Foundation & Full-Stack Bootcamp · Education

    • Studied algorithms, data structures, Node.js, React.js, and full-stack development.

05Engineering approach

How I approach backend work.

Habits that shape the code I write — practices, not metrics.

  1. 01

    Data modeling first

    Entities, relations, and constraints are settled before endpoints are written. Most features are easier once the data is right.

  2. 02

    Clear API contracts

    Explicit request and response shapes, with input validated at the boundary so the rest of the code can trust it.

  3. 03

    Security by design

    JWT authentication, role-based access, and migrations — permissions are modeled as part of the domain, not bolted on.

  4. 04

    Centralized errors & logging

    One place to map failures to responses, and logs that make it possible to answer what happened.

  5. 05

    Queues over blocking calls

    Reminders, notifications, and slow third-party calls move to jobs and queues instead of blocking requests.

  6. 06

    Indexes where they matter

    Queries are shaped around real access patterns, with caching and indexes added when the workload justifies them.

  7. 07

    Reproducible delivery

    Docker and Nginx on VPS, CI/CD pipelines, and database backups — the same build runs the same way everywhere.

  8. 08

    Debug, then refactor

    Production incidents are traced to a cause first; improvements land incrementally rather than in rewrites.

06Contact

Let's build something reliable.

Backend roles, well-scoped freelance projects, or a system that needs untangling — email or Telegram is the fastest way to reach me.

Download CV (PDF)
Location
Tashkent, Uzbekistan · UTC+5