About

I'm a frontend architect who cares about the problem underneath the code.

How I got here

I didn't start as a developer - I started as a business analyst, working as the bridge between business and engineering. Business understood the problem but not what it cost to build; developers could build almost anything but often had no visibility into why. I wrote both sides: the business brief and the technical spec.

When I moved into frontend development, that background came with me - I already understood why I was solving a problem before I had the technical skills to solve it. Seven years later, I'm still that bridge, now as a senior architect and lead: I take requirements directly from business, marketing, or the CEO, make the technical call myself, and either implement it or hand it to a teammate with the reasoning intact - while owning that it ships correctly and on time.

How I think about engineering

Code is a byproduct.

The primary deliverable is a solved business problem and a developer experience people don't have to fight.

I'd rather explain the why once than fix the same mistake twice.

Teaching the underlying constraint costs more upfront than just fixing it myself - but it's the only way people stop needing me to.

I'll try cutting-edge tech eagerly - but only ship what's proven.

Experimenting with something new and putting it in production are two different decisions. I'll reach for whatever's interesting to see how it works; what makes it into a real product still has to earn that by proving itself first.

Engineering impact

Frontend Lead, Dataddo

  • Led the migration from Vue 2 (Options API) to Vue 3 + Composition API and TypeScript across the core product.
  • Rebuilt the marketing site from Nuxt 2 to Astro, moving from SSR to SSG to hit sub-1s LCP, and cut the programmatically generated page count from 130k to 2k by removing thin pages with no unique content - fixing a crawl budget problem that was choking indexation.
  • Mentored two engineers from their first commit to shipping independently at medior/lead level, growing them from simple, well-scoped tasks to complex work with real impact on the core product.

Leadership & mentoring

I treat code review as a teaching surface, not a gate: every comment explains the why, not just the what. Mentoring works the same way I debug - find the actual constraint, not the symptom, and let people own the fix.

Currently exploring

Certified Senior Vue.js Developer - certificates.dev

ZigWebAssemblyWebGPU

Off the clock

When I'm not at the keyboard I'm usually pulling espresso shots, out for a run, or slowly losing an argument to my kid about bedtime. All three have taught me more about patience than any sprint retro.

Let's talk

Feel free to reach out.

v.hrouda@gmail.com