Full Stack Web Developer

OleksandrHal.

I build dependable business software — CRMs, integrations and data pipelines — from data model to the last pixel.

Currently at VORTEX, shipping production features for a CRM the auto business runs on.

Contact me Download CV View case studies

3+ yrscommercial full stack

20+custom parsers built

~80Mvehicle-to-part links parsed

(01)

About

I work on software that businesses run on every day: a production CRM for the auto trade, and an internal operations system I own end to end.

At VORTEX I work across the whole stack — custom modules, data-import pipelines for automotive catalogs, Ringostat, Viber, Telegram, Diia and Ukrposhta integrations, and performance fixes in complex legacy code.

Clean data models, predictable workflows and features that survive real use are what I optimize for. Right now I’m adding Laravel to my React work.

Work: VORTEXFull stack, since Jun 2023
Education: BSc System AnalysisUzhNU, 2026
Languages: Ukrainian — native, English — C1Slovak — beginner, learning
Based in: Košice, SlovakiaRemote or on-site

(02)

Skills

What I build with: in production at VORTEX, in my own projects, and the tools I’m learning now.

Frontend 06

Vue.js, production
JavaScript, production
HTML / CSS, production
React, projects
Next.js, projects
TypeScript, projects

Backend 05

PHP, production
Python, production
Node.js, projects
Express.js, projects
Laravel, learning

Databases 05

MySQL / MariaDB, production
SQL, production
Redis, production
MongoDB, projects
PostgreSQL, learning

Tools 08

Git, production
APIs & integrations (REST, Webhooks, JSON-RPC), production
Web scraping & Selenium, production
Cron jobs & queues, production
Socket.IO, projects
Claude Code, projects
Codex, projects
Docker, learning

(03)

Experience

VORTEX

Full Stack Web Developer · CRM platform

Jun 2023 — Present
Uzhhorod, Ukraine

300+

businesses — auto parts stores, service stations and salvage yards — run on the production CRM I co-maintain. Features, refactoring and critical fixes across the full stack (PHP, Vue): I fixed a crashing export (23 s → 12 s) and shipped Ringostat and Viber integrations for 10–15 clients.

1000+

tickets through the internal operations platform I’ve developed and run alone since 2023. 700+ leads too. I’ve rewritten its legacy modules to current standards, and in a 4-month overhaul moved the old client-instance data model to a leads-based one.

~80M

vehicle-to-part links collected by 20+ custom parsers I built. Queue-driven jobs: plain HTTP requests where that’s enough, Selenium with a custom captcha solver where it isn’t. The data lands in MariaDB; some sources grew into full CRM modules, like the lubricants catalog in Case Studies.

+QR attendance module for 300+ employees
+Official Ringostat integration partner
+Automatic charges from client balances for licenses and completed tickets
+Technical SEO for moparonly.parts

(04)

Case Studies

Production work at VORTEX first, then my own builds. Open a gallery to see the screens.

FeatureCS—01Built at VORTEX

Catalog for a major lubricants brand

A CRM module that finds the right oil for a car by make, model and specification, or by engine code — or straight from a car in our TecDoc catalog, in one click.

Problem

Shops needed the right oils and fluids for a specific car without leaving the CRM.

Approach

Parsed the maker’s full catalog — 600 articles — with a queue-driven parser into MariaDB.
Linked every article to the vehicles it fits: 12M+ article-to-vehicle links.
Cached frequently requested cars in Redis: lookups dropped from ~1.5–2 s to ~0.2 s.
Tied it to TecDoc: the M button on a vehicle opens its fluids; an unlinked car is matched once and remembered.

Result

600 articles, 12M+ vehicle links
~1.5–2 s → ~0.2 s for cached cars

PHP
Vue.js
Redis
Python

FeatureCS—02Built at VORTEX

Ticket Tracking

The ticket module of the internal operations platform I develop alone: bugs, features, integrations and consultations move from backlog to done, and clients follow their tickets from inside the CRM.

Problem

Client requests — bugs, features, integrations and consultations — needed one place to be tracked, priced and reported back to the client.

Approach

Kanban board from backlog to done; every card carries type, points, priority, cost and resolution.
Reusable templates for type, cost and points; one click shares a ticket with the client.
Full change history: every status change and comment, with who and when.
Client self-service inside the CRM, with automated Telegram alerts.
Completed tickets are charged automatically from the client’s balance.

Result

1000+ tickets so far

PHP
Vue.js
Telegram
Redis

ProjectCS—03Built at VORTEX

Custom modules for a Mopar parts store

A storefront for a Mopar parts store, built solo on our site template and the client’s own parts database.

Problem

The client came with their own Mopar parts database and needed it running as a full store on our platform.

Approach

Integrated the client’s database into our platform and site template.
Built 6+ custom modules: a Mopar catalog by vehicle, custom part groups, a custom menu, custom page blocks, VIN search through the client’s API, and saved cars that remember the shopper’s last vehicle.
Technical SEO for the storefront.
3 months of development, then 2 months of iterations.

Result

Orders up ~9% in the first 3 months (1,700 → 1,850 units)

Observed after launch, not an isolated effect of the new modules.

PHP
Vue.js
Redis

Client site

ProjectCS—04Bachelor thesis · 2026

Food Ordering Platform

Online ordering for a restaurant: menu, cart, pickup or delivery priced by real road distance, and an admin panel that updates live over WebSocket.

Result

Delivery-fee endpoint ~90 ms → ~8 ms avg with Redis (p95 166 → 19 ms)
100 concurrent users: <50 ms avg, 0% errors
WebSocket vs polling: ~89% less CPU, ~23% less RAM

k6, ramping 20 → 100 virtual users, on two machines in one local network.

Express.js
React
MySQL
Redis
Socket.IO

ProjectCS—05In development

Restaurant POS

A restaurant point-of-sale, with a real-time kitchen display system on the way.

What works now

The core POS flow with order handoff: staff sign in to a terminal with a PIN, see every table’s live total, fire orders in batches and close the bill with a discount and a printed receipt. The kitchen display is in progress.

Laravel 12
React
Sanctum

(05)

Education & certifications

2022 — 2026

Bachelor’s in System Analysis

Uzhhorod National University

Graduated

2024

2nd Place — UzhNU Startup Competition

“Startup – UzhNU: Forward to Innovation!”

With friends, we built a marketplace for student dorms to get listings out of Telegram chats; it grew into dorm management with washing-machine booking.

Award

2021