Zoltán Fekete

I’m an experienced Full-Stack Software Architect and developer with 15+ years of experience building web applications, backend systems, APIs, and distributed platforms. My strongest technical background is in PHP and Symfony, complemented by extensive experience with TypeScript, Vue.js, PostgreSQL, MySQL, MongoDB, Redis, Docker, Kubernetes, and cloud-based environments.

I have several years of experience as a Team Lead and Technical Lead, with responsibility for architectural decisions, technical direction, and key engineering decisions. At the same time, I have always remained hands-on and continue to be actively involved in development rather than moving entirely into management.

My responsibilities have also gone beyond application development itself. I care deeply about the correctness and reliability of the software I build and actively think about how to verify my own work. Most recently, for example, I developed a Python-based QA library to automatically verify pricing calculations and detect even the smallest unintended changes in application behaviour. I strongly believe that good engineering includes not only writing the solution, but also building reliable ways to prove that it continues to work as intended.

I also have a strong track record in technical leadership and mentoring. In one of my previous teams, I successfully transformed a group consisting largely of junior and mid-level developers into a highly effective, dynamic, and autonomous engineering team. By establishing clear coding standards and a well-structured, modular architecture, I was able to significantly improve both code quality and team throughput while minimizing unnecessary technical and interpersonal friction. I focused heavily on creating a strong technical foundation built from small, atomic, reusable components, which made the system highly composable and allowed features that would normally take weeks to implement to sometimes be delivered within 10–15 minutes. More importantly, I transferred the architectural vision and engineering principles to the team so effectively that developers increasingly made strong technical decisions themselves. They worked quickly, pragmatically, and responsibly, proactively created tickets when they discovered bugs, and continuously looked for ways to improve. For me, successful technical leadership means building a team that eventually no longer needs every technical decision to come from the lead.

I care strongly about clean, maintainable, and well-designed solutions, but I am equally pragmatic about engineering trade-offs. I understand that not every situation calls for the elegant or architecturally perfect solution. When a production issue or business-critical situation requires it, I can recognize when speed matters more and deliver a focused, pragmatic solution first, while keeping the longer-term implications in mind.