Design Engineer: Ship What Was Actually Designed by Goran BabarogicDesign Engineer: Ship What Was Actually Designed by Goran Babarogic
Design Engineer: Ship What Was Actually DesignedGoran Babarogic
Cover image for Design Engineer: Ship What Was Actually Designed
The design was approved. The build came back at seventy percent of it. Spacing is off, half the states were invented during implementation, the animation is gone, and nobody wants to spend a sprint filing forty tickets about padding.
That gap is not a discipline problem, it is a translation problem. Design hands over a picture, engineering rebuilds it from interpretation, and the difference is whatever the two sides did not talk about.
I work in the middle. I build the prototypes that settle interaction questions before they reach a ticket, hand over components in a form engineers can implement without guessing, and review what shipped against what was designed. I read and write front-end code, so the conversation with your engineers is about implementation rather than translation.
Sixteen years across product design and front end. I have designed and built production sites end to end, and most recently worked directly against an Ember and Tailwind codebase defining how Figma components map to code component APIs.
Best fit if you ship continuously and keep losing fidelity between design and production.
Not a fit if the root cause is that your design system does not exist or cannot be read correctly. Fix the source first, then put me in the loop.
FAQs

Starting at$150 /hr
Tags
Claude
Cursor
Figma
Design Engineer
Design Systems Specialist
Product Designer
UI Designer
Service provided by
Goran Babarogic maxSerbia
$100k+
Earned
55
Paid projects
4.76
Rating
332
Followers
Design Engineer: Ship What Was Actually DesignedGoran Babarogic
Starting at$150 /hr
Tags
Claude
Cursor
Figma
Design Engineer
Design Systems Specialist
Product Designer
UI Designer
Cover image for Design Engineer: Ship What Was Actually Designed
The design was approved. The build came back at seventy percent of it. Spacing is off, half the states were invented during implementation, the animation is gone, and nobody wants to spend a sprint filing forty tickets about padding.
That gap is not a discipline problem, it is a translation problem. Design hands over a picture, engineering rebuilds it from interpretation, and the difference is whatever the two sides did not talk about.
I work in the middle. I build the prototypes that settle interaction questions before they reach a ticket, hand over components in a form engineers can implement without guessing, and review what shipped against what was designed. I read and write front-end code, so the conversation with your engineers is about implementation rather than translation.
Sixteen years across product design and front end. I have designed and built production sites end to end, and most recently worked directly against an Ember and Tailwind codebase defining how Figma components map to code component APIs.
Best fit if you ship continuously and keep losing fidelity between design and production.
Not a fit if the root cause is that your design system does not exist or cannot be read correctly. Fix the source first, then put me in the loop.
FAQs

$150 /hr