Senior Manager, Backend; Platform Interoperability

At HEN Technologies, we’re building Physical AI for the real world—intelligent systems that sense, understand, and act in high-stakes physical environments. Our first application is transforming fire response: combining advanced fluid dynamics, IoT-enabled hardware, real-world operational data, and AI-powered decision support to help firefighters suppress fires faster, use less water, reduce fatigue, and improve safety. By connecting the physical layer of emergency response with predictive intelligence, HEN is building the infrastructure for a safer, more adaptive future.

HEN builds the connected systems fire departments use to run incidents from intelligent hardware at the hydrant, FDC, and pump panel through to the command tablet on scene and the chief's strategic dashboard. STAR-IQ is our incident command platform: an iOS/web app that gives Incident Commanders and Battalion Chiefs live unit assignments, comms channels, org structure, building preplans, and progress tracking during active incidents.

It runs alongside CAD, building/preplan databases, mapping services, and our broader ecosystem (CRUX, TITAN, FLUID-IQ, the ARES agentic co-pilot).You will help define HEN’s interoperability architecture across CAD, GIS, identity, telemetry, and incident-command systems.

• Build and mentor the core platform interoperability team
• Define the long-term scalable architecture working with the core development team, and manage the entire production integration strategy with Fire Departments (FD), with a critical focus on ensuring a zero-downtime rollout of the STAR-IQ system.
• CAD integration. Work with Fire Departments (FD) and Computer-Aided Dispatch(CAD) vendors to design and maintain the integration service that ingests incident data from CAD systems, transforms the CAD data to a unified schema, and exposes it to the STAR-IQ backend system.
• Building and preplan data. Build integrations and ingest FD preplan and building data to the STAR-IQ backend, normalizing wildly different source schemas into a reliable application format.
• Mapping and GIS. Integrating Mapbox, ESRI, and department-custom GIS layers behind the Map and Dashboard surfaces - hydrants, FD assets, weather, exposures, district boundaries.
• Identity and device management. Wiring up SSO, AuthN/AuthZ (GCP), and MDM flows so a department can provision users and iPads at scale without HEN being in the loop for every change.
• Audit and incident data. Making sure every integration writes through the append-only audit log and respects the data model that separates production, training, and simulated data.
• Field reliability and partner enablement. Writing the integration docs, sample payloads, and conformance tests that a CAD vendor or FD IT team can actually use. Running joint technical integration sessions with departments during rollout.
• Compliance-aware design. Building integrations that respect CJIS Security
• Policy, agency-specific data handling rules, and the separation between production CJI and our training/simulated environments.

• A Bachelor’s or higher degree in Computer Science, Software Engineering, or a related field.
• 12+ years managing teams and building production integrations between backend services and third-party systems - ideally messy, legacy, or vendor-controlled ones.
• Public-safety, healthcare, fintech, telecom, or industrial backgrounds all translate well.
• Background in or around the fire service, EMS, or emergency management.
• You can sit in a room (physical or virtual) with a fire department's IT lead and a CAD vendor's engineer and move a conversation forward.
• Past work with CAD, RMS, or other public-safety systems (Tyler, Hexagon, Central Square, Mark
  43, RapidSOS, First Net).
• GIS work - Mapbox, ESRI, PostGIS, GeoJSON pipelines.
• Prior experience working under CJIS, FedRAMP, or similar regulated frameworks.
• Strong backend engineering experience in Python and Type Script/Node.js, with working familiarity across both ecosystems.
• Production experience with event-driven systems: MQTT, Web Sockets, Kafka, or equivalents.
• Comfortable with REST and gRPC API design, schema evolution, and writing…