Changing the architecture without stopping the product
The platform had to keep running while its foundation was rebuilt. Feature boundaries and clear API contracts helped keep the change in deliverable steps instead of risking everything at once.
Incident management · 2024 – present
An incident management platform that connects its web UI and offline app on one shared domain.
Back to all projectsIntervento guides response teams through the entire process: from the initial call through resources and status to documentation. I reworked the architecture, selected the technologies and implemented a large part of the platform.
Intervento is the incident management platform for fire services: capturing incidents, assigning people and resources, tracking status, working through checklists and documenting the course of an operation.
Requirements for incident command, offline operation and integrations grew. Rather than adding more features to the existing foundation, the architecture was reassessed and reworked.
Web and mobile share the data model and API layer: GraphQL for the web, a dedicated REST API for delta sync and offline writes. The sync journal records what was applied from which device.
Scroll horizontally to see the full design.
The platform had to keep running while its foundation was rebuilt. Feature boundaries and clear API contracts helped keep the change in deliverable steps instead of risking everything at once.
Incident management is a stateful process with roles, resources, checklists and time. The data model had to represent those states — not just forms that happen to share the same fields.
Visibility and actions had to be enforced consistently across schema, resolvers and UI. A permission check in the frontend alone is not a check.
Contact
I am looking for a position where I can take responsibility for systems and teams as a lead engineer or software architect. Ideally where reliability, data and real-world workflows meet.