Daniyal Asylbekov / Product Engineer

Portfolio / 2026

I build products across interfaces, systems, and delivery.

Product engineer building TypeScript products across web, mobile, backend, and delivery. Currently shipping AI-powered workflows at chataibot.ru and building RollbackKit, an open-source framework for reversible product actions.

See selected work Start a conversation

Scroll to explore

Production software since 2023TypeScript / Next.js / Node.jsWeb / Capacitor / Backend

Selected work · 2025—2026

The work—and what you can verify.

Public code and documentation where the work is open source. Shipped product surfaces and clearly scoped contribution context where the implementation is private.

Scroll to move through the work

01 / Production AI productCurrent role

Product Engineer · 2025 — Present

A feature is shipped only when the whole path holds.

One AI product across every surface.

At chataibot.ru, I work across the web app, Capacitor-based iOS and Android clients, Node.js services, and the delivery systems around them.

Public links verify the shipped surfaces. Source and telemetry are private; contribution details describe my role, not inspectable implementation.

Next.js
TypeScript
Capacitor
Node.js

Cross-surface product flows

Assistant, document, cloud-file, and media flows needed the same behavior across web and mobile. I carried the work through client surfaces and Node.js services.

Reliable async delivery

Long-running generation can outlive a request or lose its stream. I worked on job state, interrupted-chat recovery, notifications, and delivery tracking so results still reach the user.

Mobile observability

Mobile startup crossed client, auth, and server boundaries without one timing view. I connected Firebase Performance, Server-Timing, and AppMetrica to trace each phase.

02 / Open-source frameworkEarly v0 / active development

Creator · 2026

Preview the impact. Execute safely. Keep the undo path honest.

Ctrl+Z for dangerous product actions.

RollbackKit turns destructive SaaS and internal-tool mutations into explicit product actions with preview, audit history, conflict checks, and modeled undo.

The repository, architecture notes, lifecycle documentation, and working demo source are public and can be inspected directly.

01Preview
02Execute
03Audit
04Undo
05Expire

TypeScript
PostgreSQL
CLI
Next.js

Safety as an API contract

Each action defines its input, preview, execution, snapshots, reversibility, undo window, and failure boundaries.

Durable state and operations

A storage-agnostic core is paired with a PostgreSQL adapter, migration runner, action history, and checksum tracking.

A usable developer path

The monorepo includes a CLI, a working Next.js demo, recipes, architecture notes, and explicit non-goals.

Experience · 2023—Present

The production timeline.

From a focused frontend role to owning product work across web interfaces, Capacitor applications, backend services, and delivery.

Location

Volgograd / Remote

Education

Software Development Diploma — CATEC, Almaty · 2025

Languages

Russian — Native / English — B2

Continue through the timeline

Sep 2025 — Present

Product Engineer

chataibot.ru

Visit company

Shipping AI product work across the web application, Capacitor-based iOS and Android applications, backend services, and production delivery.

Built cross-platform assistant, document, cloud-file, and media-generation flows.
Worked on async processing, streaming recovery, notifications, mobile startup, and attribution.
Added instrumentation that connects client experience to server processing paths.

Sep 2023 — Aug 2025

Frontend Developer

gosu

Built and maintained a client portal for submitting and tracking service requests for 1C-based systems.

Centralized the service-request flow in one client-facing product.
Improved heavy screens with refactoring, lazy loading, and dynamic imports.
Set up delivery with GitHub Actions and Docker and worked with backend engineers from REST API design through UI integration.

Operating principles

How the work gets made.

Not a list of self-assigned skill levels. Three rules that show up in the systems I ship and the failure modes I choose to solve.

Capability map

Product interfaces
AI systems
Cross-platform mobile
APIs & data
Delivery & observability

Three operating rules

Own the whole path.

A product decision changes the interface, API, state, failure modes, and delivery. I follow the work across those boundaries instead of handing the hard parts away.

Seen in: chataibot.ru across web, Capacitor mobile, backend, and delivery.

Instrument before guessing.

When a production path feels slow or unreliable, I make each phase observable first. Timings and correlation points turn opinions into a fixable sequence.

Seen in: Firebase Performance, Server-Timing, and attribution diagnostics.

Design failure and recovery.

Long-running and destructive actions need explicit failure states, recovery paths, and honest limits. The happy path is only one part of the product.

Seen in: generation recovery and RollbackKit’s modeled undo lifecycle.

Start a conversation

Have a product problem that crosses UI, backend, and delivery?

Open to product engineering and frontend-focused roles, as well as selected product collaborations.

I am most useful when one product problem spans several technical boundaries and still needs one coherent owner.

Start a conversation

Send an email

@makkenz0

GitHub

makkenzo

Daniyal Asylbekov

Product Engineer