Ramin Daqiqda·qiq (دقیق) — precise, exact

A nationwide system for the Ministry's Command & Control Center, tracking every major incident in Afghanistan — explosions, fires, road-traffic accidents, avalanches, drought — together with the list of people affected by each one. I built it at iMMAP for the World Health Organization, then joined WHO to maintain and extend it for the next three years: full-stack features in Angular, Node.js and Spring Boot, real-time dashboards for decision-makers, scripted automation, and training for health-facility staff.

Where technology helpedThis was the government's single source of truth for recognising the people affected: when an explosion or disaster struck, financial support to victims' families was decided from this system's records. It ran across all 34 provinces until the fall of the government in 2021.

INSO's incident-data platform: conflict and security incidents recorded, searched and analysed by humanitarian NGOs across 28 countries. I started on core incident features — advanced geospatial and narrative search on Apache Solr, CouchDB conflict resolution — and now serve as technical lead: owning the review-and-merge gate across two Angular apps and a seven-module Spring Boot backend, and running the production infrastructure on Kubernetes/Azure.

Where technology helpedSafety teams use it to understand the environment their staff operate in — what is happening around them, where, and how it is trending — and plan field operations accordingly. One searchable source instead of scattered reports, for NGOs in 28 countries.

INSO's real-time security alerts used to reach NGO staff by email and SMS. The app — which I built as primary developer from the first commit — extended that channel: push notifications, a map view, proximity-radius filters and polygon geofencing, offline support for low-connectivity areas, and OAuth2 sign-in. Part of the same service as app.ngosafety.org.

Where technology helpedAn aid worker's phone now buzzes with the alerts that matter for where they actually are — filtered by area and proximity on a map, instead of a one-size-fits-all email blast — and the app keeps working where connectivity is thin.