Arslan Agajanov logo

Enterprise ERP · Fintech · Full-Stack Product Engineering · React Native

Software Engineer

React · Next.js · NestJS · TypeScript

Software Engineer with 6+ years of experience building production applications across enterprise ERP, fintech and API-driven systems using React, Next.js, NestJS and TypeScript. Strongest in React/Next.js and TypeScript, with practical backend experience in NestJS, Node.js, PostgreSQL, authentication, RBAC and complex business workflows.

Open to remote
View my workContact
GitHubLinkedInDownload CV
  • 6+ years in software engineering
  • Enterprise ERP, fintech, and API-driven systems
  • Frontend + backend ownership across finance domains
  • Open to remote full-time and project work

Results

Engineering Impact

Measurable outcomes from a production ERP system migration, Finance API-contract audit, localization architecture, and regression gates.

135

legacy MUI importers at migration start

Plus 59 MUI icon importers and 31 DataGrid files before the ERP UI/API migration.

13/13

Finance domains audited

Full coverage of finance request/response contracts before production cutover.

46

incorrect API contracts identified

HTTP contracts that did not match the ERP Finance API.

22

missing Finance scenarios identified

Gaps found during the Finance API-contract audit.

8

P0 issues before production cutover

High-severity contract and scenario issues caught before go-live.

710

passing regression tests

Migration regression suite after later stages. An earlier controlled milestone passed 682 tests across 160 files, with typecheck, build, and API-contract checks.

951

centralized translation keys

Localization architecture: about 420 hardcoded UI strings moved into 22 namespaces; legacy i18next dependencies removed.

Systems view

Engineering Map

Tap a node to open its preview under the hub. Use View case to open a deep dive.

Map

ARSLAN

Enterprise

Web3 / Fintech

Product

Telegram

Systems

Scope

What I take ownership of

Application architecture for production React, Next.js, NestJS and TypeScript systems
Enterprise ERP across frontend and backend: Finance, Warehouse, HR, Projects, Users/Roles and permissions
REST API design and integration, HTTP contracts, PostgreSQL and Prisma-backed services
Fintech interfaces and workflows: invoices, payments, expenses, reports, and monetary operations
Production migrations, regression gates, and incident debugging without stopping the running application

Focus

Engineering focus

Frontend architecture

Production React and Next.js App Router systems in TypeScript: data models, URL state, server pagination, and maintainable feature ownership.

Enterprise ERP

Multi-module enterprise ERP across frontend and backend layers — Finance, Warehouse, HR, Projects, Tasks, office workflows, users, roles, permissions, and self-service.

Fintech workflows

Invoices, estimates, payments, expenses, recurring operations, reports, transactions, and permissioned monetary interfaces.

Backend & API contracts

NestJS and Node.js services, REST APIs, Prisma and PostgreSQL data models, plus request/response contract auditing across business domains.

Auth, sessions & RBAC

Authentication, sessions, role-based access control, file uploads, and complex CRUD workflows in business applications.

Production ownership

Gradual legacy removal, regression gates, configuration safeguards, and production debugging across routing, HTTP, and deployment.

Selected engineering

Engineering Cases

Deep engineering case studies with problem framing, architecture, key decisions, and measurable ownership — plus a compact registry of the rest.

01TypeScriptEnterpriseNDA / Internal

Enterprise ERP

Multi-module enterprise ERP developed across frontend and backend layers — Finance, Warehouse, HR, and operations.

Production · NDA

  • Software Engineering
  • ERP
  • Finance
  • HR
  • Warehouse

Interface preview

Animated loop of a dense ERP finance grid — filter, sort, open drawer.

Scan grid

erp.internal / finance / invoices
Status: Open
Columns
New invoice
IDCounterpartyAmountStatus
  • INV-1042Nordic Logistics€12,480Paid
  • INV-1043Atlas Warehousing€4,210Open
  • INV-1044Helix Retail€19,050Review
  • INV-1045Orbit HR Ops€2,860Open

The challenge

Legacy UI and API layers, several business domains, complex permissions, financial workflows, and a large volume of data-heavy CRUD — all while the production system had to keep running.

What I owned

  • Application architecture
  • Frontend & backend services
  • REST API contracts
  • Auth / RBAC
  • Finance migration
  • Production deployment

Architecture

Browser

Operators · RBAC UI

Next.js

App Router · forms · grids

NestJS API

REST · Auth · RBAC

PostgreSQL

Prisma · domains

Domain APIsFinanceWarehouseHRProjectsOffice

Key decisions

  1. 01ERP API became the source of truth

    UI models stopped mirroring transport DTOs. Adapters isolate evolving NestJS/PostgreSQL-backed contracts from domain models so Finance and other modules can migrate without rewriting every screen.

  2. 02Server state left global stores

    TanStack Query owns server cache, invalidation, and pagination. Zustand stays for UI/session concerns — no duplicated lists or manual sync between REST and client state.

  3. 03Data grids became reusable infrastructure

    TanStack Table powers dense enterprise layouts: column pinning, resizing, ordering, URL-persisted filters, and permission-aware actions shared across Finance, Warehouse, and HR.

  4. 04Finance migrated domain-by-domain

    Cutover ran module by module behind regression gates (MUI-zero / DataGrid-zero). Finance HTTP contracts were audited end-to-end before traffic left the legacy Nest path.

Impact

10+ domains

Operational scope

13/13

Finance audit

46

Contract issues found

710 tests

Regression suite

Stack

  • Next.js
  • React
  • TypeScript
  • NestJS
  • Node.js
  • PostgreSQL
  • Prisma
  • Tailwind CSS v4
  • shadcn/ui
  • TanStack Query
  • TanStack Table
  • React Hook Form
  • Zod
  • REST API

Where it stands

In production as the primary ERP system surface: gradual legacy removal, centralized localization, and ongoing domain migrations without stopping the live system.

Commercial NDA project: public demo is unavailable. The case describes architecture, stack, and ownership.

02TypeScriptWeb3NDA / Internal

Web3 / Fintech / AML Flows

Wallet and transaction frontend for finance-sensitive Web3 products with compliance checks.

Shipped · NDA

  • Web3
  • Fintech
  • Wallets
  • AML
  • Transaction UX

The challenge

Users must connect wallets, approve tokens, and complete transfers across chains while the UI stays clear about risk, AML checks, and failure modes — without leaking unsafe defaults.

What I owned

  • WalletConnect / TronLink
  • Balance & approve flows
  • Transaction UX
  • AML check integration
  • Multi-chain RPC handling

Architecture

User

Wallet intent

Next.js / React

Transaction UX

Wallets

WalletConnect · TronLink

RPC / Chain

ETH · Tron · BSC

Ops & checksBalancesApproveAML checksBackend

Key decisions

  1. 01Wallet adapters at the boundary

    WalletConnect and TronLink sit behind a thin adapter layer so screens talk to a stable frontend contract instead of vendor-specific APIs.

  2. 02Approve and send as explicit steps

    Token approve and transfer are separate, confirmable steps with clear status — reducing accidental double-submits and opaque wallet errors.

  3. 03AML checks inside the journey

    Compliance results are part of the flow, not a side panel after the fact — blocked or flagged states surface before irreversible chain actions.

  4. 04Chain differences stay in infrastructure

    Ethereum / Tron / BSC RPC details stay in shared helpers so product screens remain domain-focused (balances, transfers, compliance).

Impact

WC + TronLink

Wallets

ETH · Tron

Chains

AML-aware

Sensitive UX

NDA

Access

Stack

  • React
  • TypeScript
  • WalletConnect
  • TronLink
  • REST API

Where it stands

Shipped in commercial fintech/Web3 products under NDA — patterns reused across wallet connection, approve, transfer, and compliance UI.

Commercial NDA project: public demo is unavailable. The case describes architecture, stack, and ownership.

03TypeScriptInteractive Apps

Bunker — realtime multiplayer

Realtime product frontend — host/player rooms, private cards, and synchronized game state.

Live · public demo

  • Realtime UI
  • Game FSM
  • Private state
  • Firebase

The challenge

A multiplayer game needs a host controlling rounds and scenarios while players keep private card fields hidden until reveal — with reliable sync, not a fragile custom websocket stack.

What I owned

  • Room model
  • Host / player UX
  • Game FSM
  • Private vs public state
  • AI scenario import

Architecture

Host UI

Scenario · rounds

Player UI

Private cards

Game FSM

Rounds · votes · reveal

Firestore

Realtime room state

State layersPublic statePrivate fieldsAI scenario import

Key decisions

  1. 01Firestore as the realtime bus

    Room subscriptions keep public game state in sync across devices. No bespoke websocket server — focus stayed on product rules and UX.

  2. 02Private fields never leave the owner

    Card data that must stay secret is modeled as private until an explicit reveal step. Other players only receive public room state.

  3. 03Explicit game FSM

    Rounds, events, voting, and finale are state-machine transitions — not ad-hoc flags — so host actions and UI stay consistent under racey multiplayer updates.

  4. 04AI scenarios as a validated pipeline

    Prompt → scenario JSON → parser → validation → play. Invalid imports fail early instead of corrupting a live room.

Impact

Host + player

Roles

Realtime

Sync model

FSM

State design

Public

Demo

Stack

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Firebase Firestore
  • Firebase Auth
  • Game FSM
  • Vercel

Where it stands

Public demo live on Vercel with open source: rooms, host controls, private cards, and AI-friendly scenario import.

Open demoCode

More work

Project Registry

Additional shipped work — public demos, commercial products, and NDA projects kept compact so the case studies stay readable.

  • Spy Game — offline-first app

    Interactive Apps

    Full-stack frontend

    Next.jsReactTypeScriptTailwind CSS
    LiveOpen →

  • T-Whale

    Telegram

    Frontend

    ReactTypeScriptTelegram Web AppsTelegram Bot API
    NDA / Internal

  • Nova Engineering ERP

    Enterprise

    Frontend architecture

    Next.js 16ReactTypeScriptMUI X DataGrid
    LiveOpen →

  • ITDEAL — company website

    Landing

    Frontend

    ReactTypeScriptVitei18n
    LiveOpen →

  • TrustPay

    Fintech

    Frontend

    ReactTypeScriptREST APIVercel
    Demo offline

  • WorkDez — disinfection field app

    Web app

    Frontend

    ReactTypeScriptViteReact Router
    LiveOpen →

  • Bitex — OTC USDT exchange

    Fintech

    Frontend

    ReactTypeScriptViteMUI
    LiveOpen →

  • avia-landing.vercel.app

    Landing

    Frontend

    HTMLCSSJavaScriptResponsive UI
    Demo offline

  • Telegram Bot References

    Bot

    Bot workflows

    Telegram Bot APIPython
    LiveOpen →

Experience

Experience

Enterprise ERP, fintech, and product engineering with international and distributed teams.

Software Engineer

Multi-module Enterprise ERP

NDA / production system · Remote · International team

Domain: Enterprise software · ERP · Fintech · SaaS

Technologies

  • Next.js
  • React
  • TypeScript
  • NestJS
  • Node.js
  • PostgreSQL
  • Prisma
  • Tailwind CSS v4
  • shadcn/ui
  • TanStack Query
  • TanStack Table
  • React Hook Form
  • Zod
  • REST API

Scope: Designed and developed a multi-module enterprise ERP across frontend and backend layers — application architecture, NestJS/Node.js services, PostgreSQL/Prisma data models, REST API contracts, and production UI — without stopping the running application.

Engineering impact

  • - Implemented Warehouse, HR, Projects, Tasks, Users, roles and permissions, office/document workflows, Finance, and Self-service across UI and API layers. Warehouse covers 16+ operational areas; HR includes 20+ sections of the employee dossier.
  • - Eliminated a large legacy UI surface: started at 135 MUI importers, 59 MUI icon importers, and 31 DataGrid files; migration gates reached MUI-zero and DataGrid-zero.
  • - Audited 13/13 Finance domains (invoices, estimates, payments, expenses, recurring operations, reports, transactions): identified 46 incorrect API contracts, 22 missing scenarios, and 8 P0 issues before production cutover.
  • - Built and integrated NestJS REST APIs backed by Prisma and PostgreSQL — data models, validation, business logic, RBAC, authentication, sessions, file uploads, server pagination, filtering, sorting, and URL state.
  • - Reworked localization as architecture: moved about 420 hardcoded UI strings into 22 namespaces and 951 translation keys, and removed legacy i18next dependencies.
  • - Resolved a production routing regression where ERP requests could fall back to the legacy Nest backend when ERP URL configuration was invalid, and added configuration safeguards.
  • - Migration stages passed regression gates: a controlled milestone at 682 tests across 160 files with typecheck, build, and API-contract checks; later the suite reached 710 passing tests.

Frontend Developer (Middle+)

Itdeal

Jul 2024 - Mar 2026 · Chisinau, Moldova / Remote / Distributed team

Domain: Fintech · Web3 · Telegram products

Technologies

  • React
  • TypeScript
  • REST API
  • Telegram Web Apps
  • WalletConnect
  • TronLink

Scope: Client-side React/TypeScript delivery for fintech, Telegram, and Web3 products in an international distributed team.

Engineering impact

  • - Developed and maintained React/TypeScript applications with REST API integrations, including authentication and transactional flows.
  • - Built Telegram WebApp interfaces tied to Bot API and backend product flows.
  • - Implemented Web3 wallet UX with WalletConnect and TronLink: balances, transactions, and token approvals on Tron/Ethereum.
  • - Integrated AML and blockchain checks into frontend journeys with backend data transfer.
  • - Refactored legacy frontend modules to reduce technical debt and stabilize architecture.

Junior Frontend Developer / React Developer

Milli San

Feb 2020 - Dec 2021 · Kayseri, Türkiye

Domain: Web applications

Technologies

  • React
  • TypeScript
  • GraphQL
  • Hasura
  • Docker
  • - Fixed and built web pages with responsive UI adaptations.
  • - Worked with React and participated in migration from class components to functional patterns.
  • - Contributed to integrations involving Hasura, Docker, basic TypeScript, and GraphQL.

Capabilities

Capability matrix

Frontend

Proven
  • React
  • Next.js
  • TypeScript
  • TanStack Query
  • TanStack Table
  • Zustand
  • Redux

Backend

Proven
  • NestJS
  • Node.js
  • Prisma
  • PostgreSQL
  • REST APIs
  • Authentication
  • RBAC

UI & Forms

Proven
  • Tailwind CSS v4
  • shadcn/ui
  • React Hook Form
  • Zod
  • Framer Motion

Mobile

Active
  • React Native

Additional

Proven
  • GraphQL
  • Hasura
  • Firebase
  • Web3
  • WalletConnect
  • Telegram Web Apps

Infrastructure

Active
  • Docker
  • Linux
  • Nginx
  • Git
  • Vercel
  • Vitest
  • Cypress

Contact

Contact

Available for Software Engineer opportunities across React, Next.js, NestJS and TypeScript. Remote full-time and project work.

Open to workCurrent focus

Remote Software Engineer roles

Available for remote full-time and project work on enterprise React/Next.js/NestJS products, ERP systems, and fintech/Web3 platforms.

  • Remote
  • Full-time
  • Project-based
  • Enterprise ERP
Download CV
Emailagajanov0arslan@gmail.com
Telegram@darc_nv
Phone+99363337949
GitHubgithub.com/4rchi-nv
LinkedInlinkedin.com/in/arslan-agajanov
ResumePDF · English