Staff Product Manager - Applied AI Workflow at AiDASH

<div class="content-intro"><p><strong>About AiDASH</strong><br><br>AiDASH is an enterprise AI company and the leading provider of vegetation risk intelligence for electric utilities. Powered by proprietary VegetationAI™ technology, AiDASH delivers a unified remote grid inspection and monitoring platform that uses a SatelliteFirst approach to identify and address vegetation and other threats to the grid. With a prevention-first strategy to mitigate wildfire risk and minimize storm impacts, AiDASH helps more than 140 utilities reduce costs, improve reliability, and lower liability across their networks. AiDASH exists to safeguard critical utility infrastructure and secure the future of humanAIty™. Learn more at <a href="https://www.aidash.com." target="_blank">www.aidash.com.</a></p> <p>We are a Series C growth company backed by leading investors, including Shell Ventures, National Grid Partners, G2 Venture Partners, Duke Energy, Edison International, Lightrock, Marubeni, among others.&nbsp; We have been recognized by Forbes two years in a row as one of “America’s Best Startup Employers.”&nbsp; We are also proud to be one of the few &nbsp;software companies in Time Magazine’s “America’s Top GreenTech Companies 2024”.&nbsp;<a href="https://www2.deloitte.com/us/en/pages/technology-media-and-telecommunications/topics/north-america-technology-fast-500.html?utm_source=bngaiwebsite&amp;utm_medium=referral&amp;utm_campaign=evolve-banner" target="_blank"><u>Deloitte Technology Fast 500</u></a>™ recently ranked us at No. 12 among San Francisco Bay Area companies, and No. 59 overall in their selection of the top 500 for 2024. &nbsp;</p> <p>Join us in Securing Tomorrow!</p></div><h4>The Role</h4> <p><span data-contrast="auto">Reporting to the VP of Product Management &amp; 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.</span></p> <p class="font-claude-response-body break-words whitespace-normal leading-[1.7]">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 &amp; Monitoring (AIMS) and Climate Risk Intelligence (CRIS).</p> <p class="font-claude-response-body break-words whitespace-normal leading-[1.7]">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.</p> <h4>How you'll make an impact:</h4> <ul> <li><strong><span data-contrast="auto">Workflow design across products: </span></strong><span data-contrast="auto">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</span></li> <li><strong><span data-contrast="auto">Step-level frameworks: </span></strong><span data-contrast="auto">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</span></li> <li><strong><span data-contrast="auto">Autonomy and human-in-the-loop policy: </span></strong><span data-contrast="auto">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</span></li> <li><strong><span data-contrast="auto">Cohort logic and CS alignment: </span></strong><span data-contrast="auto">Decide which customers get which workflow flavor. CS and leadership are key stakeholders you'll bring along</span></li> <li><strong><span data-contrast="auto">Requirements to Platform PM: </span></strong><span data-contrast="auto">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</span></li> <li><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}"><span class="TextRun MacChromeBold SCXW101554705 BCX0" lang="EN-US" data-contrast="auto"><strong><span class="NormalTextRun SCXW101554705 BCX0">KPIs</span></strong><span class="NormalTextRun SCXW101554705 BCX0"><strong>:</strong> Own the operating metrics — cost per insight, cycle time, % auto-resolved, manual touches per job, quality against SLA. Track and move them</span></span></span></li> </ul> <h4>What Success looks like in 12 months,</h4> <ul> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]">A significant IVMS workflow transformation is shipped, stable in production, and delivering its promised cost and automation impact</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]">A clear, sequenced plan exists for moving IVMS toward an autonomous-by-default workflow, with human intervention narrowed to a well-defined slice</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]">Manual-touch volume on IVMS is materially down vs. baseline; the cost-per-insight curve bends</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]">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</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]">DS, Platform, CS, and GIS Ops consistently align to your decisions without escalation</li> </ul> <p><strong><span data-contrast="none">How You Operate:</span></strong></p> <ul> <li><strong>Shape the question before deciding the answer:</strong> When handed an ambiguous problem, you don't just solve it as posed — you reframe it, sharpen the metric, and tell us when we're optimizing for the wrong thing</li> <li><strong>First-principles process thinker:</strong> You can look at a 20-step workflow, ask why step 7 exists, and not lose nuance in the process</li> <li><strong>Metric-native: </strong>You reach for a measurement before a meeting. You don't ship a workflow without a way to tell whether it's working</li> <li><strong>Comfortable being the decider</strong>: When cohort logic or automation policy is contested, you make the call and defend it. You don't outsource hard calls upward by default</li> <li><strong>Credible with technical peers:</strong> DS, Platform PM, and engineering find you a strong partner. You can hold a substantive conversation about model performance, confidence thresholds, and system constraints</li> <li><strong>Write well, think in writing: </strong>Your primary artifacts are documents — workflow charters, frameworks, decision logs</li> <li><strong>Influence without authority:</strong> CS, GIS Ops, the applied AI pod, and Platform don't report to you. You move them through clarity, credibility, and shared metrics</li> <li><strong>Owner mentality: </strong>When the workflow underperforms, you don't say "the model was off" or "execution slipped." You own the outcome and find where the design failed</li> </ul> <h4><span data-contrast="auto">What we're looking for:</span></h4> <ul> <li><span data-contrast="auto">9-13 years of total experience, with at least 4-6 years as a Product Manager</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}">&nbsp;</span></li> <li><span data-contrast="auto">At least one tour owning an internal, operational, or platform-style product — not exclusively customer-facing feature PM</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}">&nbsp;</span></li> <li>A track record of cross-functional ownership at scale — not just shipping, but changing how the org made decisions in a domain</li> <li><span data-contrast="auto">Demonstrated ownership of operating KPIs (cost, cycle time, throughput,&nbsp;automation %,&nbsp;quality) under real accountability</span><span data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:100,&quot;335559740&quot;:300}">&nbsp;</span></li> </ul> <h4>Nice to have:</h4> <ul> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]">Experience working on workflows or products that combine model output with human review, and comfort making decisions that depend on model performance</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]">Background in geospatial / remote sensing / satellite imagery, utilities, climate-tech, or labeling pipelines</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]">Experience scaling a function from zero at a Series B–D company in a resource-constrained environment</li> </ul> <h4>What this role is not:</h4> <ul> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><strong>Not a feature PM role: </strong>You won't be designing what utilities see in the AiDASH product. That's owned by our IVMS / AIMS / CRIS PMs</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><strong>Not a platform or internal-tools PM role: </strong>You won't be writing PRDs for the labeling tool, QC dashboard, or routing engine. That's owned by our Platform PM — your peer, not your scope.</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><strong>Not an operations role: </strong>You won't run the workflow at scale. CS is the operating muscle that runs the workflow you design; GIS Ops is a separate execution function</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><strong>Not a process consultant or Op Excellence role: </strong>You don't map AS-IS / TO-BE flows and hand them over. You own the workflow as a product — its design, metrics, and evolution — and you're accountable to outcomes</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><strong>Not a data science role: </strong>You don't build models or design technical model evaluation strategies. You partner with the applied AI pod that does, and you make the policy calls their work informs</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><strong>Not customer-facing: </strong>You won't be in front of customers directly. The customer voice reaches you through CS and feature PMs</li> <li class="font-claude-response-body break-words whitespace-normal leading-[1.7]"><strong>Not a pure strategy or architect role:</strong> You'll be hands-on with frameworks, specs, and decisions — and driving adoption of the workflow</li> </ul> <p><br>We are proud to be an equal-opportunity employer. We are committed to embracing diversity and inclusion in our hiring practices, and we promote a work environment where everyone, from any race, color, religion, sex, sexual orientation, gender identity, or national origin, can do their best work.&nbsp;</p><div class="content-conclusion"><div>We are committed to providing an inclusive and accessible interview experience for all candidates. Please let us know if you require any accommodation during the interview process, and we will make every effort to meet your needs.<br><br>Read our Privacy Policy here:&nbsp;<a id="menur8uvg" class="fui-Link ___1q1shib f2hkw1w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1s184ao f1mk8lai fnbmjn9 f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" href="https://www.aidash.com/policy/privacy-policy/" target="_blank">https://www.aidash.com/policy/privacy-policy/</a> <p>&nbsp;</p> </div></div>