Architecture with consequences
Technology decisions, system boundaries and data models that account for operations and the next releases.
About
The demo is not what decides — daily use is: data quality, connection drops, permissions and the moment someone depends on the software.
About
I am Alessio Englert, a tech lead and software architect at EvoSys AG in Switzerland. Since 2022 I have worked on a product family for fire services and public organisations: incident management, emergency dispatch, planning and identity.
Over that time I have helped build seven products — as a full-stack engineer, architect and technical point of contact. Today I am the most senior engineer in the team: I own architectural decisions, select technologies and support other engineers through code reviews. In 2026 the IAM modernisation across four products was added to that scope.
My focus is on systems where reliability is not optional. I designed Intervento's offline synchronisation from the ground up and rebuilt Heimdall's authentication architecture. Before that, I reassessed and reworked Intervento's architecture for growing requirements.
On the platform side, I have co-owned 2,033 migration files, 79 CI pipeline commits and Docker/Compose, PM2, backup and blue-green deployment scripts across five products. Architecture knowledge lives in the repository as 18 agent skills with around 3,700 lines. Localisation is part of daily work — 3,741 German web translation keys, 349 Flutter ARB keys and products in DE/EN/FR/IT, with the FloriPlan app additionally in RO.
Over four years and nine months, 8,700+ commits have accumulated across seven repositories and 103 branches — with only two reverts. That is not a productivity promise, but a signal of continuity and little rework.
02 — Responsibility
I think systems from the data model to the interface, and from the first migration to operations. That responsibility has not been limited to individual features.
03 — What I focus on
Technology decisions, system boundaries and data models that account for operations and the next releases.
From the Vue interface through GraphQL and PostgreSQL to migrations and deployment.
Offline-first, local persistence and synchronisation that stays consistent through conflicts and connection drops.
04 — How I work
I start with workflows, data and failure modes — not with frameworks. Technology follows from requirements; it is not the starting point.
Architecture is documented, interfaces are described and context remains traceable. The documentation lives in the repository — as 18 agent skills with around 3,700 lines that people and coding agents can read.
Offline sync, retries, conflicts and authentication boundaries are considered from the start — not added afterwards.
From the first migration to the code review: I take responsibility for the result, not only for my own part.
05 — Education
A solid vocational foundation, a targeted route into university and a part-time computer science degree.
Three-year IT programme for career changers, following an existing EFZ as a painter; focus on software development, databases and project work.
One semester at Berufsmatura level in mathematics, German and economics; followed by admission to the bachelor’s programme.
Part-time computer science degree focused on software engineering, architecture and information systems.
06 — Daily setup
My working environment is keyboard-first and terminal-centric. I invest in tools that shorten feedback loops, provide context and remove repeated work — not in the longest possible list.
Agentic coding with custom review, commit and refactor agents, MCP context and Postman integration.
Primary editor with LSP, linting, formatting and Git workflow directly in the terminal.
Ghostty as a fast terminal; TUIOS for project-specific sessions and working directly with coding agents.
Keyboard-first macOS: project-specific workspaces, hyper-key launchers and custom key layers.
Reproducible local services and fast container inspection.
Postgres.app, pgAdmin and pgModeler for schema design, migrations and query debugging.
API exploration, collections and contract checks, integrated into the OpenCode workflow.
Mobile builds and releases for iOS and Android; DB Browser for SQLite for offline data.
Contact
If you are looking for a tech lead or software architect who connects architecture and delivery, I would be glad to hear from you.
Location: Switzerland