I design and ship the systems a telecom operator runs on: 100K+ subscribers, 350+ devices, AI voice analytics. Lead a team of 4 engineers.
Subscribers served
Billing and customer-service architecture used by more than 100,000 subscribers of a regional telecom operator.
Bio
Technical Lead with 4+ years of experience in the telecom industry. Leading a team of 4 specialists, architected systems serving 100K+ subscribers. Reduced operational costs by 30% through automation.
Expertise: Java (Spring Boot), React, microservices, AI integrations, infrastructure.
Speech-analytics SaaS for call-center quality control: call transcription (GigaAM, 57× realtime), AI script-compliance and violation detection, automatic escalation to external systems. Peak up to 4000 calls/day. React 19 + Express 5 + MongoDB + Kubernetes.
Developed a full-stack monitoring system for 350+ OLT devices using Java/React. Saves 200+ man-hours per month.
Nginx reverse proxy, split-DNS, VLAN segmentation, 2FA via RADIUS.
Ansible + OpenSearch. Routine operations: hours → minutes.
· · ·
· ·
· ·
· ·
· ·
· ·
Four convictions I build teams and architecture around. They explain my decisions better than a list of technologies.
An increment in production with a metric beats a perfect design on paper. Small versions, real-user feedback, refactor where the bottleneck actually shows up.
If stability depends on one person being on call, that's an architecture bug. Documentation, monitoring, runbooks and automation matter more than late-night saves.
Clear ownership, 1:1 rituals, feedback, and growth into the role. A good tech lead raises the ceiling for engineers — doesn't do their work for them.
Boring technology in production, novel things in isolated experiments. Every dependency, queue and framework is future ops pain. Deleting code feels better than writing it.
