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 lead engineer and software architect at EvoSys AG in Thun. 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 carry technical responsibility in the four-person EvoSys engineering team: I own architectural decisions, select technologies and conduct code reviews — without disciplinary responsibility. In 2026 the IAM modernisation of the whole product ecosystem was added to that scope — ongoing.
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 migrations, CI/CD and Docker/Compose, PM2, backup and blue-green deployment scripts across five products. Architecture knowledge lives in the repository and is readable by people and tools. Localisation is part of daily work: products in DE/EN/FR/IT, with the FloriPlan app additionally in RO.
Since 2022 the product family has grown across seven products and several repositories. What matters to me is that changes remain traceable and systems hold up across releases.
02 — Responsibility
I design data models, interfaces and the path between them. That responsibility covers the whole system: architecture, delivery and operations.
03 — What I focus on
Technology decisions, system boundaries and data models that account for operations and the next releases.
Vue interfaces, GraphQL, PostgreSQL, migrations and deployment all connect in my work.
Offline-first, local persistence and synchronisation that stays consistent through conflicts and connection drops.
04 — How I work
05 — Education
A solid vocational foundation, a targeted route into university and a part-time computer science degree.
Basic vocational training as a painter and decorator at Kilchherr in Thun.
After basic training, several years working in the painting trade.
Three-year IT programme for career changers, completed in summer 2024. Includes an integrated practical component: internship at EvoSys from January 2022 to December 2023.
One semester at vocational baccalaureate (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.
Local coding assistance with custom review, commit and refactor workflows, project context and API 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 direct work with coding assistance.
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 lead engineer or software architect who connects architecture and delivery, I would be glad to hear from you.
Location: Switzerland