Frontend engineering · Budapest

Complex frontends.Clear decisions.

I’m a senior frontend engineer and technical lead working on business-critical applications. I try to use my experience to make existing systems clearer and help teams reach better-informed technical decisions.

Recurring difficulties

I believe speed and quality can coexist.

01 / Delivery pressure

The cost behind the deadline

Shipping quickly matters, but it is easy to save time now by moving the cost into the future. When performance and maintainability repeatedly fall out of scope, even a small change eventually becomes harder than it should be.

02 / Technical debt

The refactor at the bottom of the backlog

Many people shape a codebase, while the necessary cleanup enters the backlog and often stays there. Refactoring is not time lost. It is part of what allows a team to keep moving at a healthy pace.

What I try to practise

The details matter over the long term.

01 / Performance

Fast software using fewer resources

I like fast software that uses resources carefully. When something appears able to run on far less hardware, I’m happy to investigate. I try to consider performance during design, rather than only in a final round of polish.

02 / Consistency

Order in the code and the interface

Design tokens, thoughtful components, a consistent design system and useful documentation. Not for the sake of rules, but to reduce guesswork and make collaboration easier.

03 / Automation

I’m lazy—and glad of it

I do not like doing something twice when it can be automated. That is why I build pipelines, simplify workflows and look for reusable solutions. When I find a reliable shortcut, I’m happy to use it.

Where I can contribute

It helps to look
beyond the code.

Over the years, I’ve gained experience in both hands-on implementation and technical leadership. It has taught me to consider what a decision means for the product, the team’s day-to-day work and the system’s ability to change.

01 / Architecture

Frontend architecture

I help establish clearer boundaries and a structure in which the next feature is easier to build with confidence.

Angular · Vue · Astro across generations
02 / Leadership

Technical leadership

Shared guidelines, useful feedback and support with decisions that affect the whole team.

~10 person development team leadership
03 / Delivery

Reliable delivery

API integrations, automated pipelines and a more predictable path from specification to production.

Fintech · energy business-critical products
From my previous work

Selected projects

From digital banking journeys and internal business applications to content management systems and high-traffic online publications.

01

Gránit Bank

Online account opening, insurance applications, loan applications, a customer portal and administration interfaces.

02

MAVIR

Internal business applications.

03

Petra Vita

Website, CMS and CRM system.

04

Sanoma

Online publications—including SzRTV, Exit24 and Cosmopolitan—and their associated CMS platforms.

05

SeeMe

Online bulk SMS platform.

06

MachoPoker

Website, CMS, external integrations and partner portal.

07

Kiskerárak.hu

Price comparison portal.

No longer active
08

Hirorigo.hu

News aggregation portal.

No longer active
AI workflow

AI makes the work faster. Engineers remain accountable.

I use agent workflows, MCP integrations and structured review—not to skip engineering judgement, but to leave more time for it.

Method / 04

Faster work, with the same engineering accountability.

AI becomes useful to a team when it has clear context, produces reviewable results and goes through the same scrutiny as any other work.

CodexMCPContextReview
Latest writing

Questions worth considering
while we build.