This is one of the strongest examples of how I work: a staff and performance platform used across a government-linked institution in Germany, built inside a multi-team engineering organization where I led the frontend surface and owned the entire end-to-end test layer.
The context. The product ran on Symfony on the backend and Vue.js on the frontend. It supported institution-wide personnel and performance workflows, with thousands of employees represented in the system and a technical organization of roughly 14 engineers. Version 1 is already in active use across the institution.
Accessibility as a core requirement. When I joined, the system needed a full rethink across API usage, styling, page behavior and accessibility. I rebuilt the frontend around keyboard-first usage with proper tab navigation, focus handling, screen-reader-aware interactions and layouts that remain usable up to 250% zoom. The goal was not compliance theater; it was making real staff workflows reliably usable for visually impaired users.
My ownership. I standardized the frontend architecture so every page followed the same mental model: store files handled backend communication, controllers coordinated page-level behavior, and page-level modules separated tables and forms cleanly. I also built reusable table patterns with shared prop structures, which made new pages and revisions easier to implement and much more predictable across the codebase.
The test surface. I treated the Nightwatch E2E suite as a first-class product surface. The tests cover both positive and negative user flows for the actions a real user can perform, so regressions are found by the suite rather than by manual trial and error after release.
I also refactored the test suite itself. Even after adding nearly 20 pages and close to 100 additional tests, I brought runtime down from roughly 20-25 minutes to around 8 minutes through better test isolation, shared helpers, less repetitive browser setup, and replacing brittle pauses with explicit waits such as waitForElement. In a CI-heavy workflow, that speedup matters every day.
Leadership and delivery. Beyond writing the code, I set frontend standards, guided the technical direction of the frontend work, and used both E2E automation and manual testing to push accessibility quality as high as possible. The project also forced me to get comfortable in a strict Git flow and conflict-heavy CI/CD process where multiple parallel tickets could easily collide, so a large part of the job was staying precise under release pressure.