I build software products across backend services, desktop applications, real-time systems, and media infrastructure.
My work spans multiple layers of the stack: backend APIs, operator-facing desktop tools, workflow engines, background agents, native runtime components, and integration-heavy services. I’m most interested in building complete systems — products that require clear architecture, predictable runtime behavior, and reliability in production.
Over time, my focus has moved beyond isolated backend development toward building complete product ecosystems where multiple applications and services need to work together cleanly.
My work typically includes:
- backend platforms and business-critical services
- desktop software for control, operations, and monitoring
- workflow orchestration and automation systems
- media ingest and processing pipelines
- integration and control-plane services
- performance-sensitive native components
- end-to-end product architecture across multiple applications
I care about strong system boundaries, maintainable code, operational clarity, and practical production-ready engineering.
I choose technologies based on the product, not the other way around.
-
timesheet-attendance-platform
Production-grade multi-tenant attendance and leave management backend with RBAC/PBAC, JWT, audit/event logging, real-time notifications, GraphQL, and a full Docker-based setup. -
saas-backend-starter
Enterprise-ready Spring Boot backend starter focused on modular architecture, multi-tenancy, security, audit logging, file handling, WebSocket support, and production-minded foundations.
See more: github.com/urosengineer
I like building software that is clear to reason about, reliable in production, and designed as a real product rather than a collection of isolated features.
My strongest interest is in systems that combine architecture, runtime behavior, tooling, automation, and operations into one coherent whole.