Staff MLE - Supply Chain

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting and extract relevant content. Let's identify sections: - About the role: there is a paragraph after "About the role:" describing building AI/ML team, etc. Also "What makes this unique:" bullet list, "Why this role matters:", "Unique technical challenges:", "A data playground unlike any other:", "You should apply if:" bullet list, "In this role you will:" bullet list. Those could be considered responsibilities or details. We need to decide which sections to create. We have sections: About the role (intro), Responsibilities (list of duties), Requirements (minimum requirements), Qualifications (maybe education?), Skills (technical skills), Benefits, Pay, Schedule. We have Pay info: Annual Base Salary $178,640—$319,000 USD. Also mention RSU grant, performance-based bonus/variable pay, equity, etc. So we can include Pay section with that salary range and mention bonus/equity. Benefits: There's a "Total Rewards" section describing compensation program, flexible working, professional development stipend, health and parental leave plans, etc. Also "Flexible Working" and "Belonging at Samsara" (EEO) but we should remove EEO boilerplate. Benefits: we can include health, parental leave, professional development stipend, flexible working model, etc. Schedule: Not explicitly mentioned besides remote role open to US/Canada, flexible working model. No specific schedule like full-time, etc. Could infer full-time but not stated. We should not create Schedule unless posting actually states it. It mentions "This is a remote role open to candidates residing in the US or Canada." That's location, not schedule. No explicit schedule like full-time/part-time. So we should omit Schedule. Qualifications: Could be education: Master's or PhD in CS, Statistics, Data Science, EE, OR, or related technical field. Also 8+ years experience. That's more requirements. We could combine Requirements and Qualifications but guidelines: Use headings only if real specific content. We could have Requirements (experience & education) and Qualifications (maybe advanced degree?). But we might just have Requirements covering experience & education, and Skills covering technical skills. Qualifications maybe not needed if overlapping. However we have "Minimum requirements for the role:" which includes Experience & Education, Core ML & Technical Skills, Mindset & Collaboration. Then "An ideal candidate also has:" list. That could be split into Requirements (minimum) and Qualifications (ideal). But we need to decide. We have "Minimum requirements for the role:" with sub-bullets: Experience & Education, Core ML & Technical Skills, Mindset & Collaboration. Then "An ideal candidate also has:" with Deep Statistical Expertise, Time-Series Mastery, Cost Optimization Mindset, Cross-Region Scaling, Vendor & Open-Source Savvy, Domain Expertise. Thus we can create: - About the role: intro paragraph. - Responsibilities: maybe combine "What makes this unique:", "Why this role matters:", "Unique technical challenges:", "A data playground unlike any other:", "You should apply if:", "In this role you will:" but that's a lot. Could restructure: Responsibilities: list of duties from "In this role you will:" plus maybe "Design, develop, and deploy advanced machine learning and statistical models..." from earlier. We'll extract responsibilities. - Requirements: Minimum requirements: Experience & Education, Core ML & Technical Skills, Mindset & Collaboration. - Qualifications: Ideal candidate also has: list. - Skills: maybe core ML & technical skills already covered; but we could put technical skills under Skills. However we already have Core ML & Technical Skills in Requirements. To avoid duplication, maybe we put Skills separate: list of technical skills (Python, SQL, MLOps, GPU/TPU, Tableau/Power BI, AWS/GCP/Azure). But those are already in Core ML & Technical Skills. Could move them to Skills and keep Requirements as experience/education/mindset. Let's see. We need to preserve all substantive info; not invent or summarize away detail. So we must include all details. If we split, we must ensure we don't lose any. Let's extract each piece. First, "About the role:" paragraph: "Samsara is building an AI/ML team inside its Operations team to make our supply chain AI native. You would be one of its first AI/ML engineers. We design connected hardware (cameras, vehicle gateways, sensors), build it with joint development manufacturing partners, and deliver it to tens of thousands of customers in industries that keep the economy running. Every link in that chain often runs on emails, flat files and manual reconciliations. We are moving our internal operations into the future with modern AI capabilities. We expect you to work across the supply chain including fulfillment, inventory, returns, cash, planning, components, suppliers and cost management. You will partner directly with Planning, Procurement, Fulfillment, Finance, Sales, and the hardware, firmware and quality engineering teams. You'll design, develop, and deploy advanced machine learning and statistical models that optimize our global supply chain. From forecasting demand to modeling supply risk using real-time IoT signals, you'll apply cutting-edge techniques to solve complex problems with direct business impact." That's the About the role content. Next, "What makes this unique:" bullet list (11 years of untapped operational data..., Own the full stack..., Real hardware supply chain..., Direct executive partnership..., You'll shape the team's roadmap...). We'll need to include that as part of responsibilities or maybe as a separate section? Could be part of About the role but we already used that heading. Could incorporate into Responsibilities. Next, "Why this role matters:" bullet list (Real-world impact..., Optimize inventory..., Drive sustainability..., Unique technical challenges...). Actually "Unique technical challenges:" is separate heading after that. Let's capture: Why this role matters: - Real-world impact at massive scale: Your models will help prevent supply shortages for customers in construction, utilities, transportation, and public safety—industries that literally keep the world running. - Optimize inventory for hardware deployed across 98% of US roads and 70+ billion miles driven annually. - Drive sustainability initiatives by reducing waste and improving supply chain efficiency across global operations. Then "Unique technical challenges:" bullet list: - Build demand, inventory and cost forecasting systems for highly variable, seasonal SKUs with intermittent patterns and long lead times. - Model supplier risk using real-time IoT telemetry, geopolitical signals, and market data—not just historical sales. - Design cost optimization algorithms balancing inventory carrying costs, expedite fees, and revenue risk across multiple regions. - Create anomaly detection systems for cellular connectivity spend and supply chain disruptions using multimodal data. Then "A data playground unlike any other:" bullet list: - Access to 10+ trillion data points annually from connected operations. - Work with ERP data, IoT sensor streams, third-party market intelligence, and operational metrics. - Build features from unique real-world signals—vehicle diagnostics, utilization patterns, failure modes. Then "You should apply if:" bullet list: - You are motivated by impact: Your work will drive smarter, faster, more sustainable supply chain decisions across Samsara's operations. - You combine scientific rigor with real-world pragmatism: You're skilled at navigating trade-offs between model complexity, performance, and maintainability. - You want to work on hard problems: You'll tackle forecasting volatility, cost optimization, anomaly detection, and more using large, noisy, high-dimensional datasets. - You are a self-directed leader: You identify analytical white space, set multi-quarter plans, and mentor others through influence. - You enjoy building models that matter: Your solutions will be deployed in production, drive decisions, and be regularly evaluated against business KPIs. - You seed AI/ML capabilities and enable the broader organization: You establish foundations, set standards, and empower cross-functional teams to adopt data-driven decision making. Then "In this role you will:" bullet list (long): - Define the end-to-end AI transformation roadmap for supply chain alongside the Senior Director of Supply Chain AI Transformation, aligning with company OKRs and executive stakeholders - Design, train, validate, and deploy ML models to production (demand forecasting, inventory optimization, supplier risk scoring, cellular spend prediction, HW cash flow), ensuring robust MLOps practices and measurable ROI - Build predictive models to forecast demand, inventory, lead times, and spend across Samsara's global supply network - Create novel features using large-scale ERP, IoT, and third-party datasets; build pipelines and ETL jobs to serve models and stakeholders - Deliver production-grade code that supports both batch and real-time inference with MLOps best practices - Act as the AI liaison to Product, Engineering, Procurement, and Finance—ensuring alignment on data requirements, integration, and change management - Drive enhancements to our data infrastructure and analytics platform to support real-time model training, monitoring, and inference at scale - Mentor junior scientists through code reviews and collaborative project work - Act as a key scientific voice in roadmap planning, experimentation frameworks, and modeling strategy discussions - Identify gaps in data, tools, and processes—and lead initiatives to close them - Establish governance frameworks, documentation standards, and quality controls for model development, validation, and lifecycle management - Partner with Ops management to drive adoption of AI tools, define new processes, and train supply chain teams on insights-driven workflows - Champion Samsara's cultural principles (Focus on Customer Success, Build for the Long Term, Adopt a Growth Mindset, Be Inclusive, Win as a Team) as we scale globally Now Minimum requirements: Experience & Education: 8+ years in applied data science or ML, ideally in supply chain, operations research, logistics, or manufacturing; Master's or PhD in Computer Science, Statistics, Data Science, EE, OR, or related technical field Core ML & Technical Skills: - Expert in statistical modeling and ML: time series forecasting, optimization, anomaly detection, causal inference - Strong Python coding skills and fluency in SQL; proven experience developing and deploying production ML systems - Proficiency in MLOps practices: automated testing, CI/CD, model versioning, monitoring, performance tracking - Experience building real-time inference pipelines and managing GPU/TPU resources for training at scale - Familiar with data visualization tools (Tableau, Power BI) and cloud platforms (AWS, GCP, Azure) Mindset & Collaboration: - Passion for operational excellence, cost efficiency, and scalable solutions - Builder mindset, with a track record of taking products or systems from 0 to 1. - Exceptional problem-solving, critical thinking, and communication skills—able to explain complex technical concepts to non-technical stakeholders - Track record of collaborating cross-functionally and driving adoption of data-driven solutions Ideal candidate also has (An ideal candidate also has:): - Deep Statistical Expertise: Able to design and validate experiments (A/B, multi-armed bandits) and apply Bayesian methods for uncertainty quantification. - Time-Series Mastery: Proven track record building advanced forecasting models (e.g., Prophet, LSTMs, Transformer-based) for intermittent demand and seasonal patterns. - Cost Optimization Mindset: Skilled in profiling ML workloads and driving down cloud/GPU spend through model compression (quantization, pruning) and serverless architectures. - Cross-Region Scaling: Demonstrated ability to deploy low-latency inference across multiple geographic regions with fail-over and disaster-recovery strategies. - Vendor & Open-Source Savvy: Experience evaluating and integrating third-party ML platforms and contributing to or leveraging relevant open-source projects. - Domain Expertise: Deep understanding of supply chain concepts (S&OP, IBP, safety stock, EOQ), ERP systems (SAP, NetSuite, E2DP, Propel), and inventory optimization theory. Ideal background in consumer electronics or B2B hardware manufacturing. Pay: Annual Base Salary $178,640—