Open to work

Frontend engineer who leads a team and still ships code

Angular and TypeScript as the core stack for eight years, React and Node.js alongside it. B2B platforms, partner portals and admin panels for government and enterprise clients in Malaysia and across the CIS region.

About

Senior frontend engineer with 8 years and 3 months of commercial experience, the last 4 years as a hands-on team lead who still writes production code every day. Core stack is Angular with TypeScript and RxJS, used continuously in every role since 2018; ReactJS and React Native as a second stack, Node.js with NestJS on the backend side.

Track record in B2B platforms and self-service portals: partner dashboards, administrative panels, data marketplaces and integrations with external systems, delivered for government and enterprise clients in Malaysia and for SaaS products across the CIS region. Four years based in Malaysia with a Malaysian company, including client-facing solution consulting in English.

Since 2025 I have run an AI-first engineering process end to end — shipping production systems built with agentic development tooling while keeping code review, manual testing and architectural standards mandatory. The guardrails are the point: a specification with explicit acceptance criteria before the work starts, and automated verification before it is called done.

Experience

  1. Solution Consultant → Solution Architect & Frontend Team Lead

    Datamicron SDN BHDJul 2022 — Aug 2026Malaysia, relocated

    Owned the frontend track across system-integration and BigData programmes for Malaysian government and enterprise clients. Grew from consultant to solution architect and development team lead, working directly with clients in English on requirements and technical documentation.

    • SSM Data Marketplace (Ministry of Domestic Trade) — an online marketplace for statistical data giving individuals and companies access to BigData through complex filtering at the Data Lake and Data Warehouse level. Designed and implemented the frontend architecture in ReactJS and TypeScript, and was the only backend developer on the project: a Java Spring Boot service and a Postgres schema from an empty repository.
    • Non-standard build on that project: bundles embedded into Apache Wicket through a custom bridge and served from a single Tomcat instance alongside Spring Boot, with no separate Node.js runtime in production.
    • Report Service — a standalone NestJS microservice abstracting Data Lake and Data Warehouse access: SQL assembled on the fly from client-side filters, source configurations stored as JSON, Redis caching. Designed, built and tested end to end.
    • JPJ AwAS (Road Transport Department) — automated penalty reporting from road cameras, integrated with a traffic-violation recognition system. Frontend in Angular and TypeScript on top of Java Spring Boot.
    • Contributed to system architecture design, technical documentation, requirement alignment with clients and task distribution across the development team.
    • ReactJS
    • TypeScript
    • Angular
    • NestJS
    • Java Spring Boot
    • PostgreSQL
    • Redis
    • Apache Tomcat
  2. Development Team Lead

    Yuk Markaz 24Jan 2026 — Apr 2026Uzbekistan, project engagement alongside primary role

    Delivered an end-to-end freight logistics platform for the CIS market: a landing page, an administrative panel, a web workspace for logistics operators and dispatchers, and a driver mobile application — four applications to production in four months.

    • Admin panel in Angular 17, dispatcher workspace in ReactJS with TypeScript, driver application in React Native for iOS and Android, landing page in Astro, backend in NestJS with PostgreSQL.
    • Built AI-first from day one: implementation through agentic development tooling, screen and user-flow prototyping before code.
    • Introduced a parallel multi-agent development workflow using Git Submodules as a shared documentation layer — one consistent context space for every agent and every engineer on the team, which stopped parallel work from drifting apart on architectural decisions.
    • Responsible for client-side architecture, business logic design and task distribution across the team.
    • Outcome: platform live in production, mobile applications submitted for App Store and Google Play review.
    • Angular 17
    • ReactJS
    • React Native
    • Astro
    • NestJS
    • PostgreSQL
  3. Team Lead & Frontend Developer

    Smartbooking uzJun 2022 — Dec 2025Uzbekistan, part-time alongside primary role

    Single-window management system for hotels and hotel chains, covering bookings, reporting and dynamic pricing.

    • Core product capability was two-way integration with distribution channels: Booking.com, Agoda, Airbnb, Mybooking.uz and others.
    • Hands-on development in Angular 9 and above with TypeScript, client-side architecture decisions, code review and onboarding of new developers. Backend team worked in PHP.
    • Angular 9+
    • TypeScript
    • RxJS
    • SCSS
  4. Developer → Team Lead

    MatrixSolutionsJun 2018 — Jun 2022Tashkent, Uzbekistan

    Web and mobile interface development in Angular 2 and above with TypeScript. Progressed from developer to team lead across several commercial projects.

    • E-Cinema — a three-product suite (E-Ticket, E-Kino, Kinoprokat) for cinema distribution management, electronic ticket sales and reporting automation. Role: project manager and frontend developer in Angular.
    • Falcon Messenger — a corporate messenger. Role: Android team lead and hands-on development in Kotlin, with AES and RSA encryption and Socket.IO.
    • Angular 2+
    • TypeScript
    • Kotlin
    • Socket.IO

Projects

Products and tools I have built — the source where it is open, the live site where it is not.

  • Developer tooling

    detent

    Runs coding agents against a queue of tasks and lets nothing finish until the repository's own checks pass. A second model reads every green diff and may demote, never approve. Each run is a journal line: which model, how many rounds, how long, how much.

    • Node.js
    • CLI
    • Coding agents
  • React + TypeScript

    Har Kun AI

    A streaming chat with a language model that can be stopped mid-sentence without losing what already arrived. The API key never reaches the browser, and the whole interface runs with no key at all against a built-in mock.

    • React
    • TypeScript
    • LLM
  • Logistics platform

    Yuk Markaz 24

    A freight marketplace that puts cargo owners, logistics companies and drivers in one place — filtered search by route, cargo type, date and price, with ratings and direct contact instead of intermediaries. Four applications to production in four months: an administrative panel, a dispatcher workspace, a driver mobile application and the landing page.

    • ReactJS
    • React Native
    • NestJS
  • Clinic platform

    QMed

    A SaaS platform for small private clinics in Uzbekistan, where scheduling still runs on Excel, WhatsApp and paper. Three products over one API and one database: a keyboard-first desktop workspace for reception, a mobile application doctors use during the visit, and a public site for each clinic. Seven repositories sharing one documentation layer, with thirty-three decisions recorded as ADRs.

    • NestJS
    • PostgreSQL
    • React
    • React Native
  • Test assignment

    GREEN-API Telegram client

    A test assignment for GREEN-API: a web chat that sends and receives Telegram messages over their HTTP API, modelled on web.telegram.org so there is nothing to learn. The provider gives raw stateless calls and nothing else — no session, no chat list, no history — so everything a user thinks of as a messenger is built on the client over long polling and localStorage.

    • React
    • TypeScript
    • Integration

Methodology

The way I run agentic development: one documentation repository, mounted into every code repository as a git submodule, read-only everywhere.

Methodology·5 min read

Agents need context, not access

Agents read what is on disk, which is why agentic development keeps pushing teams into monorepos. It buys context by deleting the access boundary — an agent whose screen fails on a bad endpoint can go and change the endpoint. I keep one repository per surface and give every one of them the same documentation repository as a submodule: the whole product is readable, one repository is writable.

  • One repository per surface, plus shared-docs mounted at the same path in each — specifications, ADRs, task queue, progress and changelogs
  • The boundary is mechanical, not an instruction: the neighbouring service is simply not in the working copy
  • A submodule pins a commit, so detent refreshes it, records which revision the agent read, and refuses to commit a pointer nobody can reach
Read the write-up

Education

  1. Bachelor's degree, Software Engineering

    Tashkent University of Information Technologies (TUIT)2018Tashkent, Uzbekistan

Certificates

  • Developer qualification certificate

    GREEN-APIOctober 2026No. 2244565

    Verify

Skills

Frontend — core

  • Angular 2–17
  • TypeScript
  • RxJS
  • Angular Material
  • AntDesign

Frontend

  • ReactJS
  • Redux
  • JavaScript ES6+
  • HTML5
  • CSS3
  • SCSS
  • Bootstrap
  • Astro

Mobile

  • React Native (iOS / Android)
  • Android (Kotlin, Java)

Backend

  • NestJS
  • Node.js
  • Java Spring Boot

AI-assisted engineering

  • Agentic development tooling
  • Multi-agent workflows
  • RAG
  • Context management
  • Spec-driven delivery

Architecture

  • SOLID
  • OOP
  • Microservices
  • REST API design
  • WebSocket
  • Socket.IO
  • Modular SPA

Data & caching

  • PostgreSQL
  • MongoDB
  • Redis

Tooling

  • Git
  • Git Submodules
  • Docker
  • Nginx
  • PM2
  • Unix / Linux

Let's talk

Open to full-time remote work, available immediately. Based in Kokand, UTC+5 — three to four hours ahead of Central Europe, with substantial daily overlap with European working hours.