Backend / AI Product Engineer focused on operational platforms, Telegram products, CRM/ERP workflows, 1C/Bitrix24 integrations, SEO marketplaces, automation systems, and data-heavy business tools.
I build systems where backend is not just endpoints: roles, statuses, workflows, payments, queues, admin panels, integrations, AI tools, logs, tests, and production support all matter.
Remote / Worldwide
Email: vitalivo@gmail.com
Telegram: @vitalivo
| Area | What I usually work on |
|---|---|
| Backend / API platforms | FastAPI, Django/DRF, NestJS/Fastify, REST APIs, auth, webhooks, background jobs, admin workflows |
| Operational systems | CRM/ERP-style tools, roles, statuses, finance flows, audit events, dashboards, internal business processes |
| 1C / Bitrix24 / CRM integrations | 1C data exchange, Bitrix24 CRM setup, REST/webhooks, business processes, leads/deals/contacts, catalog/order/payment sync, CommerceML/XML/JSON exchange, logs, retries, error handling |
| Telegram products | Telegram bots, Mini Apps, operational bots, notification systems, admin/control layers |
| AI workflow systems | LLM APIs, structured output, tool/function calling, RAG-ready workflows, human review, AI assistants inside business processes |
| SEO marketplaces | Job boards, directory platforms, SEO URL structure, sitemap/indexation logic, content lifecycle, structured data |
| Data and automation | PostgreSQL, Redis, Supabase, queues, parsers, monitoring pipelines, reporting-oriented data flows |
| Product recovery | Refactoring, architecture cleanup, integration stabilization, phased MVP delivery, production support |
| Layer | Stack |
|---|---|
| Languages | Python, TypeScript, JavaScript, SQL, Shell, Kotlin |
| Backend | FastAPI, Django, Django REST Framework, Sanic, NestJS, Fastify, Express, REST APIs, WebSockets |
| Frontend | React, Next.js, Vite, TypeScript, Tailwind CSS, TanStack Query/Router, Zustand, React Hook Form |
| AI / automation | OpenAI API, Claude/Anthropic API, Gemini API, structured outputs, tool/function calling, agent workflows, n8n, Make.com |
| Telegram | Telegram Bot API, Telegram Mini Apps, aiogram, Pyrogram, Telegraf, Telethon, realtime notifications |
| Business automation / CRM | 1C, 1C-Bitrix, Bitrix24, Bitrix24 REST API, webhooks, business processes, CRM entities, catalogs, orders, payments, CommerceML/XML/JSON exchange, integration logs |
| Data | PostgreSQL, Redis, Supabase, SQLAlchemy, Alembic, Drizzle ORM, Prisma, Zod contracts, BullMQ |
| Background jobs | Celery, Redis Streams, queues, schedulers, retries, worker-based pipelines |
| QA | pytest, Jest, Vitest, Playwright, Testcontainers, Ruff, mypy, manual scenario checklists |
| DevOps | Docker, Docker Compose, GitHub Actions, Linux, Nginx, VPS/self-hosted deployment, staging runbooks |
Some projects are public. Some are private, client-restricted, or team/internal work. For private projects I describe the architecture and scope without exposing client code, credentials, or business data.
Private/internal operations and CRM platform connecting clients, projects, developers, finance, conversations, sales deals, tasks, documents, assets, audit events, and AI workspace logic.
Stack: TypeScript, React, Vite, Tailwind CSS, TanStack, Zustand, Node.js, NestJS, Fastify, PostgreSQL, Drizzle ORM, Zod contracts, Docker, GitHub Actions.
Highlights: role-based workflows, finance tracking, conversation scanning, structured AI summaries, native tool/function calls, operation history, rollback for safe write actions, regression-oriented tests.
Private/GitLab work around 1C-based business automation, Bitrix24 CRM setup, and data exchange between operational systems.
Stack: 1C, Bitrix24, Bitrix24 REST API, 1C-Bitrix, XML/JSON exchange, CommerceML, webhooks, PostgreSQL/MySQL where needed, background jobs, logs, Linux/Docker for supporting services.
Highlights: CRM pipelines, leads/deals/contacts flow, order/catalog/payment exchange, scheduled synchronization, manual retry flows, integration error logs, admin/operator visibility, phased delivery for legacy systems.
Private/internal SEO-first job board for the trucking/CDL vertical with clean URL structure, vacancy/company taxonomy, SEO whitelist combinations, lifecycle handling, and admin/content tooling.
Stack: Python, FastAPI, PostgreSQL, Redis, SQLAlchemy, Alembic, React, Next.js, TypeScript, Tailwind CSS, shared contracts.
Highlights: SSR/ISR-oriented SEO surface, city/state/profession pages, index/noindex logic, sitemap/indexation flows, vacancy lifecycle, company pages, reviews, admin operations.
Private/team Telegram Mini App MVP for planned group rides with passenger, driver, and admin workflows, trip matching, assignments, live location, route previews, and admin dashboard.
Stack: React, Vite, TypeScript, TanStack, Zustand, React Hook Form, NestJS, Fastify, PostgreSQL, Redis, Telegraf, WebSocket, MapLibre, Docker.
Highlights: passenger trip creation, driver profiles, admin assignment flow, realtime gateway, self-hosted map stack, health endpoints, CI and Playwright lanes.
Private/internal OpenWrt router-control system where parents manage a child's internet access policy through Telegram commands and natural-language AI parsing.
Stack: Python, PostgreSQL, Supabase, OpenAI API, n8n, Telegram API, MQTT, paho-mqtt, Docker, pytest, Ruff, mypy.
Highlights: Telegram to n8n to structured AI output to MQTT to router-agent to nftables firewall, schedule windows, daily limits, instant block/unblock, exceptions, status/statistics, contract validation.
Accepted client sprint for an AI/retail audit MVP with Telegram/Supabase flow and manager dashboard.
Stack: React, Tremor, Supabase, Edge Functions, RLS policies, Storage, Telegram session flow.
Highlights: KPI dashboard, roles, tenant access, audit list/detail views, filters by period/store/SKU/auditor/status, shelf photos, GPS, planograms, Lost Sales, Share of Shelf, Out-of-Stock analytics.
Private automation project for an order/event business: Make to n8n migration, GoHighLevel CRM, email/order intake, Stripe payment flow, Supabase tracking, Telegram control layer, and AI/RAG-ready workflow architecture.
Focus: controlled automation instead of fragile scripts, Dev/Prod separation, testing, cutover/rollback, logs, human approval, and safe AI draft generation.
Public Telegram/backend operations platform with FastAPI, PostgreSQL, Redis, Celery workers, Telethon, Docker, React, and WebSocket UI.
Repository: vitalivo/Telegram-management-system
Public marketplace-style backend proof with auth, catalog/order/payment logic, PostgreSQL/PostGIS, Redis, Docker, and payment-service flow.
Repository: vitalivo/my-marketplace
| Repository | What it demonstrates |
|---|---|
| Telegram Management System | FastAPI, PostgreSQL, Redis, Celery, Telethon, Docker, React, operational Telegram workflows |
| my-marketplace | Marketplace/backend/payment flow, auth, PostgreSQL/PostGIS, Redis, Docker |
| TON Testnet Wallet | TypeScript wallet UI, TON SDK, transaction flow, address validation, tests |
| table_detector | Python CV prototype, YOLOv8, state-machine tracking, Docker, tests |
| video_analytics_bot | Telegram bot, PostgreSQL analytics, natural language to controlled SQL flow |
| testovoe-zadanie | Async Python API, PostgreSQL, SQLAlchemy, Alembic, JWT/RBAC, Docker, webhook endpoint |
| Pattern | Why it matters |
|---|---|
| Explicit status lifecycles | Avoids hidden business logic and makes operations visible |
| Role-based access and policy checks | Keeps admin/operator/client flows safe and maintainable |
| Shared contracts and schemas | Reduces frontend/backend drift and makes AI/tool calls safer |
| Background workers and retries | Keeps long-running tasks, integrations, and AI calls stable |
| Audit events and operation logs | Makes production behavior explainable after launch |
| Human approval for risky AI actions | Lets AI assist without silently changing critical data |
| Phased delivery | Keeps MVP scope measurable before expanding the roadmap |
I prefer to start with the real workflow, not the technology list.
Before writing code, I usually clarify:
- who uses the system;
- what the core entity is;
- which statuses matter;
- which actions need approval;
- which integrations can fail;
- what must be logged;
- what should be in the first MVP and what should wait.
This keeps development practical: first a working core, then automation, analytics, AI, and scale.
Before software engineering, I spent 20+ years managing real-world operations: teams, budgets, suppliers, schedules, quality, P&L, and daily execution. That background is useful in backend/product work because many software systems fail not in the code, but in unclear responsibility, missing statuses, poor handoff, and lack of operational visibility.
- Backend-heavy SaaS and product platforms
- Telegram bots, Mini Apps, and backend-connected Telegram products
- AI workflow systems and AI assistants inside business processes
- 1C, Bitrix24, 1C-Bitrix, CRM setup, and data exchange projects
- CRM/ERP, internal tools, admin panels, and dashboards
- SEO marketplaces, job boards, directories, and catalog platforms
- Data pipelines, parsers, monitoring, and reporting systems
- Architecture cleanup, stabilization, and phased MVP delivery
Contact: vitalivo@gmail.com
Telegram: @vitalivo