• Full-stack engineer · Fintech & Blockchain
  • Vilnius, Lithuania — remote
  • Open to senior & lead roles

Five years building software where a bug costs real money. Banking cores, payment integrations, crypto custody, smart contracts and the high-load services between them — TypeScript on Node.js at the core, Rust where it counts, React when it needs a face.

Currently

Building a stock market analytics platform that checks whether analysts' predictions actually came true.

Scroll
  • CUSTODY.TPS5.00▲ +400%
  • BANKING.RPS2,500▲ sustained
  • PAYMENTS.UPTIME99.90%▲ money paths
  • GQL.CALLS/PAGE3▼ −97%
  • CHAINS.SHIPPED15+▲ BTC·EVM·SOL
  • TX.LIST.LOAD0.5s▼ −89%
  • KEYS.OUTSIDE.HSM0▼ FIPS 140-3
  • YEARS.IN.PROD5+▲ since 2021

01Capabilities

What I can build for you.

Each one backed by systems running in production today.

Built for
  • Banks & EMIs
  • Crypto custodians
  • Wallets & exchanges
  • DeFi protocols
  • Wealth management
  • iGaming & real-money apps

01 / 06

Core banking & FinTech backends

Accounts, balances and money movement for regulated businesses — with the unglamorous guarantees that keep auditors and customers calm.

  • Double-entry ledgers & balance models
  • KYC/AML onboarding flows
  • Settlement & daily reconciliation
  • Audit trails & role-based access

2–3k

RPS sustained on a licensed e-money institution, 99.9% uptime on money paths

02 / 06

Payment integrations

Wiring products into banks, PSPs and card rails so every payment lands exactly once, in exactly one state — retries and duplicate webhooks included.

  • Banking-partner & PSP APIs
  • Idempotent webhooks & retries
  • Payment state machines & sagas
  • Payouts, refunds, subscriptions

100k+

users moving money through payment flows I designed

03 / 06

Custody & key management

Key infrastructure a bank can trust: keys live in tamper-resistant hardware, every signature passes policy first, and no single person can move funds alone.

  • HSM-backed signing with non-extractable keys
  • Key hierarchies & envelope encryption
  • Policy engines & M-of-N approvals
  • Multi-tenant, multi-chain wallets

5×

sustained withdrawal throughput on a bank custody platform

04 / 06

Blockchain & DeFi

Everything between a user’s wallet and the trade: reading the chain, moving value across it and putting it to work — behind one API, whatever chain sits underneath.

  • Multi-chain wallets, indexers & reorg-safe deposits
  • Swaps, bridges & DEX integrations — Pump.fun, Raydium, Meteora
  • Trading tools on real-time streams, protected from MEV
  • Staking, liquidity positions & NFTs, incl. Bitcoin Ordinals

15+

chains in production — Bitcoin, EVM, Solana, Sui, Aptos, Tron, XRP and more

05 / 06

Smart contracts in Solidity & Rust

On-chain logic for EVM and Solana, written like the money is real — because it is. Tested, fuzzed and reviewed before it ever sees mainnet.

  • Solidity with Foundry: tests, fuzzing, gas
  • Solana programs in Rust / Anchor
  • Security review: reentrancy, access control
  • MEV-aware execution (Jito, private flow)

EVM + SVM

contracts and programs shipped on both virtual machines

06 / 06

High-load & real-time systems

Services that stay fast when traffic, chains and markets all spike at once — and tell you why before your users do.

  • Event-driven microservices (Kafka, NATS)
  • Load testing & bottleneck hunting
  • Real-time streams over gRPC & WebSocket
  • Observability, tracing, on-call

101 → 3

cross-service calls per page after killing an N+1 — list load 4.5 s → 0.5 s

02Guarantees

Money code that never double-spends.

The non-negotiables behind every system above. Boring on purpose.

  • 01

    Idempotency

    Every money-moving request carries an idempotency key. Retries, timeouts and duplicate webhooks produce exactly one effect — a replay just returns the original result.

    POST /transfers  Idempotency-Key: 7f3a…c1  → 201POST /transfers  Idempotency-Key: 7f3a…c1  → 201 (replay)
  • 02

    ACID transactions

    A balance change and its ledger entries commit together or not at all. The isolation level is a deliberate choice per flow, not whatever the ORM defaults to.

    BEGIN;  INSERT INTO entries …;  UPDATE balances …;COMMIT;  -- both or neither
  • 03

    Race conditions

    Two withdrawals hitting one account in the same millisecond cannot both win. Conditional updates, row locks or optimistic versions — then proven under parallel load.

    UPDATE accounts SET balance = balance - $1 WHERE id = $2 AND balance >= $1;-- 0 rows updated → reject, never overdraw
  • 04

    Sagas & outbox

    Flows that span services and partners — debit, payout, confirm — run as sagas with compensating steps. Events leave through a transactional outbox, so a rollback never gets announced.

    debit ✓ → payout ✗ partner timeoutrefund ✓ → state: compensated
  • 05

    Reconciliation

    The internal ledger is checked against bank statements and on-chain state every day. A mismatch is flagged and investigated — never silently patched.

    ledger 1,204,551.20 EUR = bank ✓ledger 41.92710553 BTC = on-chain ✓
  • 06

    Integer minor units

    Amounts are stored and calculated as integers in the smallest unit — cents, satoshis, wei, lamports — with BigInt or decimal types. Never floating point.

    0.1 + 0.2 = 0.30000000000000004 ✗10n + 20n = 30n cents ✓1 BTC = 10⁸ sat · 1 ETH = 10¹⁸ wei · 1 SOL = 10⁹ lamports

03Approach

How I build systems that hold money.

Shift-left by default: quality and security are designed in from the first commit, not inspected in before release.

  1. 01

    Start with how money moves

    Before any code: which accounts exist, how money moves between them, and which rules must never break. Get that right and most bugs never happen.

  2. 02

    Design for failure

    Retries, duplicate webhooks, reorgs, partner outages — assumed from day one, not discovered in production.

  3. 03

    Shift left on quality & security

    Tests, threat modelling and security review start at design time, not the week before release — fuzzing for money math, audits before mainnet, keys in an HSM from day one.

  4. 04

    Measure, then optimise

    Load tests and traces before rewrites. Opinions are cheap; flame graphs are not.

  5. 05

    Own it in production

    Terraform, CI/CD, dashboards, on-call. Merged is not done — running reliably for real users is.

04Toolbox

What I ship with.

Node.jsTypeScriptNestJSReactRust

Backend

  • Express
  • GraphQL
  • REST
  • gRPC
  • WebSockets
  • Microservices
  • Jest

On-chain

  • Bitcoin (UTXO, PSBT, descriptors)
  • EVM
  • Solana
  • Anchor
  • Solidity
  • Foundry
  • Tokio

Frontend

  • React
  • Redux Toolkit
  • Vite
  • Wallet adapters
  • WalletConnect

Data & messaging

  • PostgreSQL
  • Redis
  • MongoDB
  • InfluxDB
  • Kafka
  • RabbitMQ
  • NATS

Cloud & ops

  • AWS
  • Terraform
  • Docker
  • GitLab CI
  • GitHub Actions
  • Datadog
  • Linux

Fintech & security

  • Payments
  • KYC/AML
  • Banking APIs
  • CloudHSM · PKCS#11
  • FIPS 140-3
  • Contract audits
Education
Bachelor's degree in Computer EngineeringNational University “Zaporizhzhia Polytechnic”, 2020 — 2024
Programme
Computer Engineering
Graduated
June 2024
Accreditation
Ministry of Education and Science of Ukraine
Diploma
State-registered (Diia) · verified copy on request
Languages
English ProfessionalUkrainian NativeRussian NativeLithuanian Learning

05Contact

Building something that moves money? Let’s talk.

I’m open to senior and lead engineering roles, and to focused contract work on banking, payments, custody and smart contracts.

Roles
FinTech · Blockchain · Payment systems
Format
Remote · Hybrid · Open to relocation
Engagement
Full-time · Part-time · Contract