01
Editorial systems
A lot of my work has lived near publishing and CMS workflows, where clarity, trust, and workflow speed matter as much as feature count.
Split, Croatia / Senior Software Engineer / RemoteCurrently building at BuzzFeed
I turn products with history into interfaces that feel calm under pressure.
My best work lives where product complexity is real: editorial systems, internal tools, mature frontends, and teams trying to modernize without making the whole thing feel rewritten by committee.
years shipping
13+
Across agency work, publishing systems, internal tools, and large product environments.
first production code
2012
Enough mileage to know when a codebase needs ambition and when it needs editing.
comfortable overlap
EU / US
Used to working across distributed teams where product, design, and engineering move together.
Current chapter
BuzzFeed
Internal tools, editor-facing flows, accessibility improvements, and product work that needs to function well under the daily load of real teams.
What I optimize for
Clearer systems
Better rhythm, cleaner interfaces, fewer sharp edges, less product fatigue.
Working vocabulary
Editorial productsInternal toolsFrontend systemsAccessibilityRefactors with historyDesign-aware delivery
Good fit for products that already matter and now need more shape, more confidence, and a better experience for the people using them every day.
The throughline
Low-drama deliveryA lot of engineering work gets framed as raw capability. I care more about whether the product starts making more sense after the work is done.
BuzzFeedRefinery29CodeBOX via ToptalBig Room StudiosStaticMIDPublishing systemsModern ReactProduct engineeringInterfaces with tasteBuzzFeedRefinery29CodeBOX via ToptalBig Room StudiosStaticMIDPublishing systemsModern ReactProduct engineeringInterfaces with taste
The point of view
Make the complicated feel authored, not merely assembled.
The strongest product work is technical, visual, and editorial at the same time. It solves the system underneath while also improving the feeling people get from using it.
Clarity is a feature
The interface, the codebase, and the team conversation should all feel easier after the work lands.
Modernize without cosplay
I like new tools, but I care more about whether the product gets cleaner, faster, and easier to ship.
Polish belongs in delivery
Accessibility, interaction quality, and visual discipline should be part of the build, not a postscript.
Approach
Technical depth with a stronger sense of composition.
My career started with WordPress themes, PHP applications, and hands-on delivery, then moved through publishing platforms, CMS migrations, internal tooling, and modern frontend systems. That path gave me a bias for systems that explain themselves and work that feels more intentional than noisy.
Good product engineering is part architecture, part editing.
The goal is not just to make software function. It is to make the product feel more legible, more confident, and easier for people to move through.
Publishing platformsInternal toolsNext.js and ReactMigration workAccessibilityInteraction polish
02
Mature frontends
I am comfortable improving products that already have history, edge cases, politics, and more than one generation of decisions inside them.
03
Design-aware engineering
The build should feel deliberate. I care about spacing, pacing, motion, typography, and the tiny things that make software feel authored.
04
Refactors with judgment
Not every system needs a heroic rewrite. Often the real move is to create better shape, better seams, and a better path forward.
01
Read the actual product
Understand the workflow, the people, and the friction before jumping to architecture theatre.
02
Recompose the system
Simplify structure, reveal priorities, and make the UI and codebase easier to move inside.
03
Ship with better edges
Accessibility, interaction quality, and calmer defaults should show up in the actual release.
Selected experience
A career built in systems that already had something at stake.
The common thread is not a single stack. It is the kind of work: products with real complexity, real users, and enough history that engineering decisions need judgment as much as skill.
Started shipping
2012
Recent focus
Internal tools + modern frontends
Thread through all of it
Useful product judgment
Current chapter2019 - PresentRemote
BuzzFeed
Full-stack Developer
Worked across internal tooling and product surfaces, helping move mature systems onto a newer stack while improving usability and accessibility.
- Contributed to platform upgrades that improved performance and day-to-day workflow quality.
- Built new functionality across editor-facing and user-facing applications.
- Pushed accessibility improvements into multiple parts of the product surface.
What this sharpened
- How to improve old systems without losing product rhythm
- How to make internal tools feel less like chores and more like instruments
- How to bring accessibility into the release, not the roadmap backlog
Stack snapshot
ReactNext.jsJavaScriptNode.jsGoPythonJest
Previous chapters
Everything before the current act.
Before the current chapter came agency work, product teams, CMS migrations, backend systems, and the kind of early-career breadth that teaches you what shipping really costs.
2017 - 2019
Refinery29
Software Engineer
Worked on both backend and frontend initiatives for a large media platform, including CMS migration support and new product functionality.
SQSRedisMySQLReactNode.jsPHPSCSSJest
2016
CodeBOX via Toptal
Senior PHP Engineer
Delivered WordPress plugin and theme work for client projects, balancing new feature work with debugging and direct support.
WordPressPHPJavaScriptGitHub
2015 - 2016
Big Room Studios
Software Engineer
Moved between frontend, backend, component work, and light infrastructure responsibilities across a varied project mix.
Symfony 2WordPressJavaScriptSassGruntPHP
2013 - 2015
Refinery29
Software Engineer
Contributed to platform re-architecture and shipped custom user experiences across registration, shopping, SEO, and partner-facing work.
RedisKohanaJavaScriptPHPSassGrunt
2013
Static
Software Engineer
Built business-oriented applications and handled deployment details for smaller, hands-on product work.
LaravelJavaScriptPHPSassGrunt
2012 - 2013
MID
Software Engineer
Started on the practical side of shipping: themes, maintenance, hosting, and keeping many small sites healthy.
WordPressPHPJavaScriptHTML5
Start a conversation
The best work usually starts when the product already matters.
If the product has momentum, history, rough edges, or a team trying to modernize without setting everything on fire, we are probably in the right territory.
Good messages usually mention
- What already works and should definitely survive
- What feels brittle, slow, or politically difficult
- Where clarity, polish, or better workflow would matter most
A mature frontend that needs a stronger second actInternal tools that work but still feel heavier than they shouldA product team that wants better UX without a lot of theatre around it
Write to me