Skip to profile

Engineering systems. Growing engineers.

Software engineer and team lead working across production systems, team delivery, and applied AI.

Budapest, Hungary

portfolio assistant

Skip the CV.
Ask the source.

Ask about my engineering work, leadership, or how I use AI in production — answers are grounded in this portfolio.

ASK ME

I'm an AI grounded on Borbála's bio — ask anything about her work, leadership, or AI experience.

About

background · approach

I moved from engineering into leadership in 2024 without stepping away from the code — I still ship features on the products my team owns, which is the only way I know to stay useful in a technical argument. Three things shape how I work: building real teams where people are partners, not just coworkers; picking up new tools by making something with them; and figuring out where AI-assisted development actually earns its place in production code.

Most of my curiosity goes into that last one at the moment: building the harness that lets an agent do a whole piece of work, then checking whether it actually did.

I studied Computer Science and Engineering at BME, BSc through MSc, specialising in critical systems — the kind where you design for the failure case before the happy path. I taught Formal Methods there as a teaching assistant in 2022, then took an MBA at ELTE in Finance and Management, largely to understand the business decisions the software ends up serving. All three with highest honours.

Leadership

team-lead since 2024

Team lead at Prolan since 2024, running a cross-functional Scrum team of 4 engineers across 4 products in a safety-critical environment. Still hands-on with code review and shipping.

Beyond the delivery, what I care about is the atmosphere — a team people actually want to show up to. High trust, disagreements aired out loud, ownership on whoever is closest to the problem. Room for creativity, for new ideas, and for trying a technique that hasn't proved itself yet — that's where the best work comes from, and where new tools like AI-assisted development get an honest shot at production.

+30% delivery uplift from AI
~380 tickets resolved in 2025
0 attrition since 2024
<24h PR → merge cycle
4 products end-to-end
  • Owns the architectural calls across 4 products in active development — tech stack, integration boundaries, rewrite-vs-refactor decisions.
  • Rolled out AI tooling (Claude Code, ChatGPT/Codex) on the team in 2025.
  • Strengthening cross-team collaboration through recurring meetings with adjacent teams, shared working norms, and broader internal-tool adoption.
  • Supervised a Master's thesis. Mentoring interns.
Proactive, takes ownership, and can be counted on.
— Direct manager
Handles engineering and leadership work with responsibility and care.
— Direct manager
Always finds a good solution; nothing gets bounced back.
— Senior stakeholder
Thanks for your help and for the advice on my merge requests.
— Junior engineer

Engineering

full stack · jvm + web

4 active products across rail and manufacturing, spanning desktop and web. All are built with Java, with Spring and PostgreSQL powering the web backends and React with TypeScript on the frontend.

Titanium tracks components and inventory for manufacturing, and the production floor uses it daily. I inherited a modernisation that was already half-built — the new stack running in parallel with the system it was meant to replace, and neither one finished.

Running both was the real problem: every change had to land twice, and the longer it lasted the more the two drifted apart. Getting onto one stack meant migrating persistence off an in-house database layer onto Hibernate, fixing thread-pool limits that only showed up under production load, and replacing scattered admin rights with one scoped super-user role. The legacy path is retired now, with no pause in daily use.

  • Titanium Web

    End-to-end component and inventory management for manufacturing and production environments. Took over a half-finished modernization, retired the legacy alongside it, and reworked the permission model.

    Java · Spring · Postgres · Vaadin · Maven · Docker

  • WebDiag Web

    Real-time diagnostics, data collection, fault analysis, and reporting for safety-critical railway signalling stations. Runs in production. Leading the work to extend it to a new interlocking system family.

    Java · Spring · Postgres · Maven · Docker · React · TypeScript

  • DisCom Desktop + Web

    Cross-border railway communication that translates a fixed operational phrasebook between languages. Deployed as a desktop client; a web variant is in the works. Delivered to two stations against a fixed external deadline, with operational inputs arriving the night before deployment.

    Java · Swing · Node.js · Express.js · React · Postgres · Maven · Docker

  • ProrisCAD Desktop

    Model-driven designer for railway signalling systems. Engineers model the signalling logic graphically; the tool generates the deployable parameterisation. Main architect for years — feature direction, framework calls, and the day-to-day shape of the tool.

    Java · Eclipse Modeling Framework · Maven · Ecore/Xcore · Xtext/Xtend · Graphiti

Elsewhere

projects · writings

Side projects and recent writings — where I experiment with new tools and ideas on my own time. This site is one of them: Astro with React islands, a constellation puzzle, and a server-side AI chat, written end to end with Claude Code and Codex.

Real-time collaborative web editor for RAMS diagrams — Markov chains, fault trees, FMEA, and more. Multi-user editing via Yjs CRDTs, AI-assisted diagram generation, and LaTeX/TikZ export. Solvers run in a Web Worker: steady-state availability, MTTF, minimal cut sets, and importance measures.

  • TypeScript
  • React
  • Fastify
  • Postgres
  • Redis
  • Yjs
  • AWS

Document Q&A with full pipeline transparency — every chunk, similarity score, rerank, and citation exposed alongside the answer. Built-in evaluation lab with LLM-judged quality metrics, and multi-provider model support via litellm.

  • Python
  • Streamlit
  • LanceDB
  • DuckDB
  • SQLite
  • litellm
Building a Transparent RAG, Transparently “The dangerous part is that nothing looks broken. The numbers look scientific.” The AI Era Needs Smarter Failure “AI makes both learning and failure faster. Leadership decides which one scales.”