Available for backend & integration work

Roman Melnikov
builds the backend.

>

I design and ship Python/Django systems that run unattended: workforce time & attendance platforms, biometric terminal integrations, asynchronous pipelines and reporting engines where a rounding error becomes somebody's payslip.

10+years in production
Django 5primary framework
24/7systems maintained
RU / ENworking languages
01

About

I'm a backend engineer working mostly on enterprise systems that touch physical reality — access-control terminals on a wall, a camera at a gate, a shift that started at 07:58 instead of 08:00. That domain is unforgiving: the data arrives late, out of order, duplicated, or not at all, and the report still has to be right.

My default toolkit is Django for the domain model, Celery and Redis for everything that must not block a request, Channels for live device traffic, and PostgreSQL for the truth. Around that I put Docker, structured logging and the smallest amount of cleverness a problem will tolerate.

I care about the parts nobody demos: idempotent event ingestion, timezone-correct schedules, migrations that survive a live database, and code a colleague can read at 2 a.m. during an incident.

  • FocusBackend architecture, device & API integrations
  • DomainTime & attendance, access control, HR automation
  • AlsoComputer vision (face detection), report engines, bots
  • StyleSmall commits, explicit contracts, boring reliability
  • Emailr.melnikov@cybercode.pro
02

Stack

Core

day-to-day

Python 3.12Django 5DRFASGIUvicornPydantic

Async & realtime

jobs, queues, sockets

Celerycelery-beatRedisRabbitMQChannelsWebSockets

Data

storage & reporting

PostgreSQLSQL tuningS3 / boto3NumPyXlsxWriter

Integrations

the messy edge

ZKTeco / iClockRESTWebhooksTelegram Bot APIGoogle APIOAuth 2.0

Vision & ML

applied, not academic

OpenCVMTCNNTensorFlowFace pipelines

Ops

shipping & keeping alive

DockerComposeNginxLinuxGitCI pipelines
03

Selected work

Hronos — workforce time & attendance platform

Lead backend

A Django platform that turns raw punches from biometric terminals into schedules, timesheets and payroll-grade reports for distributed organisations.

  • Device layer: a long-running iClock/ZKTeco protocol handler ingesting terminal events over unreliable links, with idempotent replay and per-device state.
  • Rules engine: shifts, rotations, overtime, absences and exceptions computed per employee across timezones.
  • Reports: a unified report layer (timesheet, extended, attendance) exporting to Excel with consistent totals.
  • Async core: Celery + Redis for imports, recalculation and scheduled jobs; Channels for live terminal status.
DjangoCeleryRedisChannelsPostgreSQLDocker

Face enrolment & photo pipeline

Computer vision

Automated preparation of employee biometrics: detect, validate and crop faces to the exact geometry terminals accept, so enrolment stops being a manual Photoshop job.

  • Detection: MTCNN + OpenCV pipeline with quality gates (size, angle, sharpness, single-face check).
  • Delivery: normalised images pushed to devices and archived to S3-compatible storage.
OpenCVMTCNNTensorFlowboto3

Integration & notification services

Automation

Glue that removes humans from routine loops: partner APIs, catalogue synchronisation, scheduled data exchange and a Telegram bot for alerts and on-call reporting.

  • Reliability: retries with backoff, dead-letter handling, structured logs and health endpoints.
  • Scheduling: crontab-driven periodic tasks managed from the admin instead of the server.
python-telegram-botdjango-celery-beatRESTWebhooks
04

Path

Present

Backend Engineer

CyberCode

Owning the backend of a time & attendance product line: architecture, device integrations, async processing, reporting and production support.

Earlier

Full-stack / Python Developer

Product & contract work

Built web services, admin systems and internal tooling on Django; handled deployment, database design and third-party API integration end to end.

Background

From scripts to systems

Self-directed engineering

Started with automation scripts that saved someone an afternoon, then kept going until they became services other people depend on. Still the same instinct.

Open to interesting problems

Let's build something reliable.

Integration that keeps failing, a report nobody trusts, or a Django codebase that needs an owner — send the details.

copied to clipboard