Frontend & product UI
- Angular
- React 19
- TypeScript / JavaScript
- Stencil.js
- Design systems
- Component libraries
- HTML & SCSS
- Tailwind CSS
- Angular Material
Software Engineer & Consultant
Darko Vulicevic
Software that ships - and stays healthy
Design, build, stabilize, and operate software - from greenfield to mid-project rescue. Hands-on engineering with clear technical leadership.
Services
What I do for clients
Seven clear offers - consulting, development, audit, ops, and AI. Expand any one for details.
Skills
Stack and craft
Tools and domains used on real production systems - not a keyword dump.
Architecture & delivery
- Frontend architecture
- Multi-app architecture
- Real-time applications
- Migration & refactoring
- System design
- Technical decision making
- API design
- Code standards
- Performance optimization
Platform & operations
- CI/CD
- Drone
- Nginx
- Squid / proxy
- Linux
- SSL & domains
- Node.js
- Shell
- Code signing & notarization
Tooling & quality
- Vite
- pnpm / npm
- WebSocket
- Storybook
- Git / Bitbucket
- Cross-platform (web & desktop)
- Data protection / GDPR
- Privacy & security
- Jira / Confluence
Work
Nearly 6 years in application development
Hands-on production work across product teams - applications, shared UI, and the delivery infrastructure around them. Not demos.
Web & desktop application development
Feature ownership on Angular and React codebases - TypeScript, modern UI patterns, and code that stays maintainable after handover.
Shared frontend systems
Design systems and component libraries shared across product surfaces - consistency without duplicated UI work.
Realtime & multi-user products
Live multi-user clients where reliability and ongoing maintenance matter as much as the first release.
Servers, CI/CD & traffic layer
Linux, Nginx, SSL/domains, proxy routing, and CI/CD so releases stay predictable.
Architecture & delivery guidance
Stack choices, system shape, and standards when a team needs a clear technical path.
Long-running product care
Ongoing features, migrations, fixes, and stabilization on systems that already have users and deadlines.
Proof
Selected outcomes
Production patterns, anonymized - pressure in, clear move, lasting result.
Shared UI system
Context
Several product surfaces shipping in parallel - UI drift, duplicated components, no single source of truth.
Move
Shipped a shared design system and component library the teams could own and extend.
Result
One visual language, faster feature UI, and far less copy-paste frontend work.
Mid-flight recovery
Context
Project already moving - fuzzy architecture calls, slipping quality, no honest path to green.
Move
Diagnosed root causes, contained risk, and replaced chaos with a prioritized recovery sequence.
Result
A stable decision path - recover, redesign, or rewrite - instead of a panic rewrite.
Release hardening
Context
App was live, but deploys and the traffic layer depended on habit - SSL, proxies, pipelines.
Move
Hardened Linux, Nginx, SSL, routing, and CI/CD until release was routine.
Result
Predictable deploys and an ops layer the team could run without tribal knowledge.
Live product care
Context
Multi-user product where reliability and day-two maintenance mattered as much as launch.
Move
Owned client UX and integrations with production discipline - not a demo spike left behind.
Result
A live surface that stayed maintainable under real users and continuous change.
Why DVision
Why choose DVision
Senior delivery without the agency fog - proven across 5+ clients and 20+ projects in production.
0+Clients
0+Projects
0yProduction work
0Services offered
You talk to the person who ships
No account managers, no relay chain. Architecture calls and implementation come from the same hands.
Greenfield to rescue, same standard
New builds, stuck mid-flight projects, audits, and ops - one senior bar instead of handing you between specialists.
Work your team can keep
Clear decisions, documented handover, and code shaped for the people who maintain it after I leave.
Production over theater
Client and project work taught the same lesson: demos don’t matter. Reliable software in the wild does.
Process
How an engagement runs
Same spine for greenfield builds, audits, infrastructure, and rescue work.
- 01
Discover
Goals, constraints, stakeholders, and what “done” means. Enough clarity to act - no theater.
- 02
Diagnose / plan
Risks, architecture options, and a delivery plan. On rescue work, this is where chaos becomes a sequence.
- 03
Build / stabilize
Execute with visible checkpoints and honest status - features, sites, pipelines, audits, or architecture changes.
- 04
Hand over
Documentation and knowledge transfer so your team owns the outcome after the engagement.
About
Darko Vulicevic
Consultant and engineer focused on production software - hands-on build, architecture judgment, and direct communication with the people who own the product.
Clarity over theater
Trade-offs in plain language. You always know what I recommend and why.
Ship, then keep it healthy
Launch matters - so does day two. I build for the team that maintains the work next.
Stabilize before you rewrite
Chaos rarely needs a full rewrite on day one. Diagnose, contain risk, then modernize with intent.
Senior hands, not black boxes
Direct engineering and advice - transparent progress, no agency fog.
What clients can expect
- Honest scope and timeline framing up front
- Modern TypeScript engineering (Angular / React when it fits)
- Documented handover your team can own
- Direct access - founders, CTOs, and product owners talk to me, not a relay
FAQ
Common questions
Angular is a core strength and often my default. I also ship React when it fits. Stack follows your constraints - not dogma.
Contact
Tell me what you’re building - or repairing
Share the project stage and the service lane that fits. I usually reply within one to two business days.
Channel open--:--
- AvailabilityAvailable remotely · Europe timezone
- LanguagesEnglish · Serbian
For a useful first reply, include
- Goal and where the project stands now
- Stack, constraints, and who decides
- Timeline and how urgent it is