I build broadcast automation, media infrastructure, and real-time control systems.
Most of my current work lives in private repositories and is focused on a larger product ecosystem spanning:
- newsroom and rundown systems
- media asset management and workflow automation
- ingest, playout, CG, teleprompter, and video wall control
- site-to-site media transfer agents
- desktop operator tools
- native media and playback engine components
I’m interested in complete systems — software where architecture, runtime behavior, operator experience, and production reliability all matter.
- Newsroom and rundown workflows — story/item models, live production control, MOS-oriented integrations
- Media Asset Management — ingest, search, AI-assisted metadata, workflow execution, related assets
- Playout and live control — channel state, cue/take/preroll semantics, shared playlists, operator-first UI
- CG and graphics systems — template authoring, live preview, data-driven graphics workflows
- Teleprompter infrastructure — newsroom synchronization, live script control, SDI-oriented output agents
- Media transfer platforms — control-plane + agents for reliable site-to-site file delivery
- backend services and APIs
- desktop control applications
- real-time WebSocket/STOMP systems
- workflow engines and background orchestration
- native C++ media/playback components
- integration-heavy services that connect multiple products into one coherent system
Most of my current broadcast and media systems work is private.
The repositories below are public reference implementations and earlier product-oriented backend projects.
Multi-tenant attendance and leave management backend with RBAC/PBAC, JWT security, audit and workflow event logging, real-time notifications, GraphQL, and Docker-based local setup.
Spring Boot backend starter focused on modular architecture, multi-tenancy, security, audit logging, file handling, WebSocket support, and production-minded service foundations.
I like building software that is:
- clear to reason about
- reliable under real operational pressure
- structured around explicit system boundaries
- designed as a product, not a collection of isolated features
My strongest interest is in systems where backend architecture, real-time behavior, native runtimes, UI operations, and production workflows all have to fit together cleanly.