Refactoring into reusable UI
Turning large forms, grids, and workflow screens into reusable components, typed models, predictable validation, and maintainable state flow.
No portfolio theater. Just facts and production UI.
Igor Živković / Frontend Developer
I build component-driven interfaces for enterprise teams: reusable UI systems, data-heavy workflows, real-time updates, role-based product flows, and maintainable TypeScript architecture.
What I'm good at
The strongest signal in my work is not landing pages. It is UI for real business workflows, constraints, state, and users.
Turning large forms, grids, and workflow screens into reusable components, typed models, predictable validation, and maintainable state flow.
Making dense tables and workflows easier to read, filter, edit, review, and use every day for internal business users.
Working across projects that used Angular Material, PrimeNG, Syncfusion, Ignite UI, DevExtreme, and custom components.
Handling SignalR/WebSocket updates, concurrent editing state, API errors, empty states, and cross-screen synchronization.
Selected work
These case studies are based on real production work, anonymized around client names, internal project details, and confidential context.
Case Study 01
A production-proven Angular module needed to move into the React stack used by the team expected to own and extend it long term.
Problem
The module handled complex grids, validation-heavy forms, shared state, and API flows, but it no longer matched the frontend stack used for future product development.
My role
Result
The module became easier for the target team to understand, extend, and maintain inside their React-based frontend ecosystem while preserving proven production workflows.
Migration map
Production workflows moved into typed React modules.
Angular module
React modules
Public demo
I primarily build frontend systems, but I can work across the API boundary when needed: contracts, validation, auth flows, persistence, and frontend state.
Public demo
Frontend-first, backend-aware.
A small full-stack demo showing how I connect product UI with a typed Node/NestJS API. Frontend remains my primary focus, but this project demonstrates practical backend literacy around API contracts, validation, authentication, persistence, and documentation.
View GitHub repoWhat it demonstrates
Frontend
Backend
API / Tooling
Experience
The through line is production frontend work: complex screens, real users, shared constraints, and maintainable delivery.
Jan 2026 - present
Kirey Group
Frontend Developer
Niš, Serbia / Full-time
Aug 2025 - Jan 2026
SharpDev Solutions
Frontend Developer
Niš, Serbia / Contract
Nov 2023 - July 2025
Naissus Technologies
Frontend Developer
Niš, Serbia / Full-time
Mar 2018 - Oct 2023
Prime Software
Frontend Developer
Niš, Serbia / Full-time
2002 - 2018
Previous Experience
Banking and Finance / Freelance Graphic Design
Serbia / Earlier career
Capabilities
My focus is building maintainable frontend systems for complex business workflows across Angular, React, and TypeScript.
Structuring complex UI around focused components, typed data flow, and maintainable state management.
Reusable components, predictable form behavior, and shared patterns across product screens.
Interfaces built around dense tables, filtering, concurrent editing state, pagination, and reliable saves.
UI that stays reliable around SignalR/WebSocket updates, API failures, optimistic flows, and sync states.
Enterprise workflows for operators, supervisors, admins, members, clients, and agencies.
Daily engineering practices and tooling used to keep frontend work maintainable.
Contact
I am interested in frontend roles where the UI has meaningful complexity: enterprise workflows, reusable systems, data-heavy screens, real users, and production constraints.
© 2026 Igor Živković.