About AiDASH
AiDASH is leading the PreventionFirst™movement for electric utilities and transforming grid resilience through its pioneering platform that unifies vegetation, asset, storm, and wildfire intelligence. Powered by SatelliteFirst™ Inspection & Monitoring, AiDASH delivers comprehensive visibility across the entire grid at the right frequency and budget, using the right data modality. More than 200 customers trust AiDASH to keep the lights on, spend where it counts, and defend every decision, Securing Tomorrow across every mile of the grid. Learn more at www.aidash.com.
The PreventionFirst movement is growing, and so is the recognition behind it. In 2026, Forbes named AiDASH one of America's Best Startup Employers for the 4th consecutive year, and TIME included AiDASH among America's Top GreenTech Companies for the 3rd year in a row. Deloitte Technology Fast 500™ ranked AiDASH No. 12 in the San Francisco Bay Area, and No. 59 overall in their selection of the top 500 for 2024.
Join us in Securing Tomorrow Together!
The Role
Reporting to the VP of Product Management & Process Excellence, you'll own the production workflows that transform raw satellite imagery into customer-grade insights — designing, automating, and continuously improving the pipelines that sit at the heart of how AiDASH delivers value.
You'll start by going deep on our Vegetation Management Workflow (IVMS) — where complexity is highest and the automation upside is largest. From there, the scope grows to cover Asset Inspection & Monitoring (AIMS) and Climate Risk Intelligence (CRIS).
You won't be designing customer-facing product features. You won't be building the internal platform (that's our Platform PM, your closest peer). You'll be designing the operating model that connects them — the steps, frameworks, and policies that govern how an insight gets produced, who or what handles each step, and where humans stay in the loop.
How you'll make an impact:
- Workflow design across products: Define what the production workflow looks like end-to-end for each product: the sequence of steps, the cohort logic (which customers / geographies / products take which path), the handoffs, and the SLAs
- Step-level frameworks: Author the operating frameworks for individual steps — e.g., the image acquisition framework (when do we re-order? from which vendor? what freshness threshold?), the model QC framework (what's the sampling strategy by model age, terrain, sensor?), and similar for every critical step
- Autonomy and human-in-the-loop policy: Decide where the workflow runs autonomously and where humans intervene. Set and own the confidence thresholds at which model output is trusted enough to drop QC. The technical specifics — sampling strategies, model evaluation methods, HITL mechanics — are owned by a pod of applied AI data scientists and analysts you'll partner closely with. You own the policy decision; they own the underlying technical work that informs it
- Cohort logic and CS alignment: Decide which customers get which workflow flavor. CS and leadership are key stakeholders you'll bring along
- Requirements to Platform PM: Translate workflow design into clear system requirements (e.g., "at step X, capture labels with confidence scores and reviewer ID"). Platform PM owns the system spec; you own that the workflow as designed produces the data and outcomes you need
- KPIs: Own the operating metrics — cost per insight, cycle time, % auto-resolved, manual touches per job, quality against SLA. Track and move them
What Success looks like in 12 months,
- A significant IVMS workflow transformation is shipped, stable in production, and delivering its promised cost and automation impact
- A clear, sequenced plan exists for moving IVMS toward an autonomous-by-default workflow, with human intervention narrowed to a well-defined slice
- Manual-touch volume on IVMS is materially down vs. baseline; the cost-per-insight curve bends
- Every critical workflow step has a metric, a target, and a dashboard. The org can answer "how is the workflow performing this week?" without a Slack thread
- DS, Platform, CS, and GIS Ops consistently align to your decisions without escalation
How You Operate: