László Kovács

Twenty years is a long time to write software. Long enough to have seen every architectural fad come and go, and to have a fairly clear sense of what actually matters — systems that stay up, code that the next engineer can read, and technical decisions that don't paint a company into a corner three years later.

My background is primarily enterprise Java — Spring Boot, distributed messaging with IBM MQ and Kafka, WebLogic deployments, Oracle databases. I spent a decade at ING Bank working on mission-critical banking systems, then moved through consulting at NESS and Accenture before stepping into architecture roles. For the last few years I've been working as a Solution Architect, which in practice means splitting time between hands-on engineering and helping organisations make sense of their technical direction.

I'm not a specialist who works in one lane. I can lead an architecture review in the morning and spend the afternoon debugging a threading issue in a message listener. That range is deliberate — architects who stop writing code lose touch with reality fairly quickly.

I work remotely from Spain. The time zone works fine for European teams and I've operated this way long enough that it's not an experiment — it's just how I work. I'm available for senior engineering, principal, or architect roles where there's real technical depth to the problem.