Senior platform engineer for products that have to work.

YPay is designed around tenant isolation, payout risk control, and infrastructure clarity. The product combines host-bound tenant routing, role-separated admin and driver surfaces, external provider integrations, and an auditable payout lifecycle.

Role

Product and systems engineer

Contribution

Designed and implemented the tenant model, product surfaces, payment integrations, and deployment topology.

Constraints

Financial operations require strict tenant isolation, auditable state changes, and resilient third-party boundaries.

Outcome

A live platform that gives fleets and drivers one traceable payout lifecycle from balance visibility to reconciliation.

• Built as a Next.js 16 monolith with typed integration modules, Drizzle ORM, PostgreSQL, and tenant-bound host parsing.
• Implements Yandex Fleet, Bird Verify, and Bank of Georgia integration layers for balances, OTP delivery, and payment submission.
• Supports driver-side payout requests, reconciliation visibility, and event history with clear admin oversight.
• Structured for production and development VPS targets behind a shared host-level proxy stack.

YDesk turns operational traffic into a clear working surface: tenant-specific domains, role-aware queues, durable records, integrations, and background notifications under one deployment model.

Role

Product and systems engineer

Contribution

Built the operational workspace, tenant-aware routing, durable case records, worker notifications, and production stack.

Constraints

Support work must remain fast under live traffic while preserving ownership, history, and tenant boundaries.

Outcome

A live multi-tenant operations surface with clearer queues, accountable case handling, and durable notification delivery.

• Combines a Next.js operations surface, PostgreSQL, support notification worker, and tenant-aware routing.
• Separates administrative and tenant workflows while keeping auditable operational records.
• Runs as a production multi-service stack behind the shared VPS proxy.

NeoPoints is built around a balanced, append-only ledger and strict park boundaries. Each park has its own hosts, membership, wallet and activation; identity and SMS codes come from YPay, Yandex Fleet data arrives through a shared Fleet service, and support stays in YDesk.

Role

Product and systems engineer

Contribution

Designed and built the points economy, ledger, tenant model, gift catalogue, gamification, admin workspaces, YPay and Fleet integrations, and release pipeline.

Constraints

Points carry real value, so every balance must reconcile to journal entries, parks must never see each other's data, and other systems' records stay behind signed APIs.

Outcome

A live loyalty program in two fleet parks where drivers earn points on real orders, climb ranks and redeem gifts, with every balance traceable to its ledger entries.

• Next.js 16 and React 19 app with web, worker, order-board and Fleet processes on PostgreSQL, with jobs and outbox kept in the database.
• Points from qualifying completed orders, recorded as immutable, balanced journal entries with audited admin adjustments.
• Gift catalogue with stock reservations and Telegram order notifications, plus ranks, missions, seasons, leaderboards, 2x campaigns and public order tournaments.
• HMAC-signed internal APIs to YPay for identity, SMS one-time codes and challenge rewards; installable PWA in Georgian, English and Russian.

A multi-service analytics system that turns raw match demos into durable, interactive evidence.

• Steam and FACEIT identity flows
• Go parser and replay pipeline
• Public and account analysis surfaces

Coordinates are encrypted on the publishing device; the public relay forwards opaque messages without position history. Source and release evidence are public on GitHub.

• Apache-2.0 original source code
• AES-256-GCM Internet rooms
• Immutable releases with checksum, SBOM and provenance

FlyGod Studios gives the game work a coherent release identity without hiding the engineering behind each title.

• Independent game releases
• Studio-level presentation
• A growing catalogue of playable systems

Alice Plays started from a simple thought: if a puzzle game lives on your phone, it should remember you, come back fast, and never make the quiet part of playing feel like work.

• Starts with Sudoku but is structured as a broader game platform rather than a one-off title.
• Supports social authentication, cloud saves, leaderboard patterns, and offline-friendly progressive web app behavior.
• Built with a modern React stack tuned for mobile-first interaction.
• Presented as a product where polish, retention, and future game extensibility matter equally.

The value here is not only the workshop release itself but the discipline of translating a weapon concept into readable in-game behavior, balancing, and presentation.

• Presented as a crafted content mod rather than a throwaway asset pack.
• Focuses on weapon fantasy, tactical readability, and the fit of a new firearm inside RimWorld combat loops.
• Shown here as part of the broader game-development section, alongside original game and systems work.
• Custom-designed card replaces default embed treatment for a cleaner portfolio presentation.

This entry highlights how small-scale game work can still carry strong authorship: a single weapon concept, a clear fantasy, and a better-than-default presentation layer.

• Built as a custom showcase card rather than a raw workshop embed.
• Centers on incendiary personality, weapon readability, and combat flavor inside RimWorld.
• Linked directly to Steam Workshop for the original release page.