Interview people close to the work and listen for exceptions, repeated decisions, and phrases like “normally” or “unless.”
Software engineer · requirements · workflow-first systems
Building software by first understanding the people using it.
I’m Dejan, a software engineer from Banja Luka. I like working close to clients and customers: interviewing them, defining features with them, and turning their everyday workflow into requirements a team can actually build from.
Working note
I’m interested in the space where a client says “it usually works like this,” and the real software requirements start appearing in the exceptions.
Start here
A quieter shape for the work.
Each page has a job: public projects from GitHub, a requirements-focused thought process, engineering notes, and a more personal about page.
Projects
Public GitHub projects with short project pages, workflow diagrams, and links back to the repositories.
02Thought process
The part closest to how I work: client interviews, feature definition, requirements, and the useful mess before implementation.
03Engineering blog
A place for field notes on requirements, system boundaries, product decisions, and lessons from building.
04About me
A short professional introduction, background, interests, and links to CV, GitHub, and LinkedIn.
How I work
Before the system, there is usually a customer conversation that needs structure.
Turn feature ideas into requirements, scenarios, rules, tradeoffs, and questions the team can answer together.
Design the smallest useful structure, then let feedback from real use sharpen the next version.
Dejan Vukadinovic