Milan Maksimovic / Software Engineer & Founder

Engineering the systems behind modern telecom.

I build telecom products, developer APIs, and resilient infrastructure across connectivity, messaging, voice, and security. CEO at OmaxTelecom. Laravel, Go, and React engineer.

Telecom systems · Network engineering · Cybersecurity · Full-stack development

Where I focus

I work across the layers that make communication products possible: APIs, applications, networks, and the operational systems behind them.

Building software where telecom, networks, and security meet. I design and build telecom platforms, developer APIs, and the infrastructure behind reliable connectivity. My work spans eSIM, messaging, voice, network systems, and full-stack products built with Laravel, Go, and React.

At OmaxTelecom, I work on connectivity and communications products, from eSIM and data services to messaging and developer-facing integrations.

Expertise

I care about clear interfaces, secure defaults, observable systems, and infrastructure that behaves predictably under real operating conditions.

Telecom and connectivity

eSIM and roaming data flows, wholesale SMS and SMPP, SIP and VoIP integrations, and numbering workflows that partners can actually operate.

Software engineering

PHP and Laravel backends, Go services, React dashboards, API design, and full-stack product work where admin UX and developer UX both matter.

Networks and infrastructure

Linux hosting, DNS, Nginx, VPN and firewall segmentation, virtualization, and monitoring stacks I architect around for predictable operations.

Security and reliability

Authentication, 2FA, scoped access, audit-friendly controls, secure routing, and resilience patterns for services that cannot fail quietly.

Product and systems design

Multi-tenant platforms, white-label workflows, provider abstractions, and usage plus billing models that match how telecom products are sold.

Systems engineering

I treat product requirements and operational reality as one problem: design APIs and control planes that partners can integrate, then back them with monitoring, access control, and network patterns that survive incidents.

That means explicit auth scopes, idempotent provisioning flows, adapter layers for heterogeneous providers, and dashboards that reflect ground truth instead of wishful metrics.