Senior Manager, Digital Finance & Supply Chain Transformation
ChargePoint · Campbell, CA · 1 mo ago
Business Development$155k–$209k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us" but we should not repeat job title as heading. We need sections for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each section heading only if there is real specific content. We need to preserve all substantive info, remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. The posting includes "About Us" which is about company; we could treat that as "About the role"? Actually "About Us" is company description; we could put under a section maybe "About the Company" but not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly.
We have:
- About Us: company description. Could go under "About the role"? Not exactly. Perhaps we can treat as "About the role" includes description of role and company? The instructions: "use
.
Then Requirements: maybe combine experience and education.
Then Qualifications: maybe list of skills? But we already have Skills section. Let's follow: Requirements = experience, education; Qualifications = maybe "Finance Technology Depth", "Finance Process Fluency", "AI & Automation Mindset", "Supply Chain Literacy", "Team Leadership", "Bias for Action". Skills = maybe specific tools: NetSuite, Workday Financials, Oracle Hyperion/EPM, Anaplan, AI/ML automation tools, EPM platforms.
But we can also merge Qualifications and Skills; but better to have separate sections if content distinct.
Let's extract:
From "What You Will Bring to ChargePoint": bullet list:
- Finance Technology Depth: Strong command of enterprise finance systems — NetSuite is essential; exposure to Workday Financials, Oracle Hyperion/EPM, or Anaplan is a plus
- Finance Process Fluency: Hands-on knowledge of FP&A, monthly/quarterly/annual close, AP/AR, procurement, expense management, sales commission processing, and revenue reporting
- AI & Automation Mindset: Practical experience shipping AI or automation within a finance context — not just planned it
- Supply Chain Literacy: Enough supply chain knowledge to connect operations decisions to financial outcomes — inventory, procurement, and COGS visibility
- Team Leadership: Experience managing and growing functional and technical teams — setting direction, building capability, delivering results
- Bias for Action: Comfortable making decisions with imperfect information in a fast-moving environment and course-correcting quickly
That could be Qualifications.
Then Requirements section later:
- Experience: 6–8 years in finance technology, ERP transformation, or enterprise systems — with measurable outcomes across finance and/or supply chain.
- Finance Processes: Direct experience across FP&A, financial close, AP/AR, procurement, expense management, and sales commissions.
- NetSuite: Hands-on NetSuite experience required — functional ownership, implementation, or systems management.
- AI & Automation: Demonstrated use of AI, ML, or automation tools in a finance or operations setting.
- EPM & Reporting: Familiarity with EPM platforms — Oracle Hyperion, Anaplan, Workday Adaptive, or equivalent.
- People Management: Prior experience managing functional and/or technical teams.
- Education: Bachelor's degree in Finance, Accounting, or Information Systems required. MBA preferred but not mandatory.
We could treat Requirements as experience + education; Qualifications as the skill areas; Skills as specific tools (NetSuite, Workday, etc). But there is overlap.
Maybe better: Requirements = experience + education; Qualifications = the bullet list from "What You Will Bring"; Skills = specific tools (NetSuite, Workday Financials, Oracle Hyperion/EPM, Anaplan, AI/ML automation, EPM platforms). However the bullet list already includes tools.
Given instruction to prefer few substantive sections over many thin ones, we could combine Qualifications and Skills into one section called "Qualifications & Skills". But we have to use allowed headings; we could use "Qualifications" and put both bullet lists there. Or we could use "Skills" for tools and "Qualifications" for the bullet list. But that may be thin.
Let's decide: We'll have sections:
- About the role (company + role overview)
- Responsibilities (What You Will Be Doing)
- Requirements (Experience, Education, Finance Processes, NetSuite, AI & Automation, EPM & Reporting, People Management)
- Qualifications (Finance Technology Depth, Finance Process Fluency, AI & Automation Mindset, Supply Chain Literacy, Team Leadership, Bias for Action)
- Benefits
- Pay
- Schedule
That seems reasonable.
Now we need to strip boilerplate: remove "About Us" heading? We'll incorporate content into About the role.
We need to preserve all substantive info: include company description, role description, responsibilities, requirements, qualifications, benefits, pay, schedule.
We must not include EEO etc.
Let's craft HTML.
We'll use
for each section heading only if there is real specific content. We need to preserve all substantive info, remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. The posting includes "About Us" which is about company; we could treat that as "About the role"? Actually "About Us" is company description; we could put under a section maybe "About the Company" but not in allowed headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly.
We have:
- About Us: company description. Could go under "About the role"? Not exactly. Perhaps we can treat as "About the role" includes description of role and company? The instructions: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those headings if we have content. We need to decide which sections have content.
We have:
Responsibilities: "What You Will Be Doing" section includes many bullet-like paragraphs. We can extract responsibilities.
Requirements: "What You Will Bring to ChargePoint" includes bullet-like list of qualifications/skills. Also "Requirements" section later includes experience, finance processes, NetSuite, AI & Automation, EPM & Reporting, People Management, Education.
Qualifications: maybe overlapping with Requirements. But we can separate: Requirements = experience, education; Qualifications = skills? However we can combine.
Skills: maybe list of skills like NetSuite, AI/Automation, EPM, supply chain literacy, team leadership, bias for action.
Benefits: described: "The company offers a comprehensive benefits package including health, dental, and vision insurance; 401(k); paid time off; parental leave; life and disability insurance; and wellness resources."
Pay: "The base salary range for this role is $155K – $209K per year. In addition, this position is eligible for annual merit-based RSU grants."
Schedule: "Location Campbell, CA (Hybrid — minimum 3 days per week on-site)" maybe schedule? Could be location/hybrid. Not exactly schedule but we can treat as Schedule? The instruction says include Schedule section only if posting actually states them. It does mention hybrid schedule: minimum 3 days per week on-site. So we can include Schedule.
We also have "Reports To Director Business Transformation" maybe metadata; we can fold into a short p or drop.
We need to remove boilerplate: EEO, equal opportunity, accommodation, recruiting agencies note, etc.
We need to preserve all substantive info: company description, role description, responsibilities, qualifications, requirements, benefits, pay, schedule.
We must not repeat job title as heading (the page already shows it). So we don't add a heading for job title.
We must not put Job ID/requisition numbers as headings (none present).
We must output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
About the role
...
But we need to decide content for About the role: maybe combine About Us and role description? Could be a brief overview: "ChargePoint is at the center of the EV revolution..." plus description of role: high-impact transformation role at intersection of finance, technology, supply chain, reporting to Director Business Transformation, etc. We'll include that. Then Responsibilities: list from "What You Will Be Doing". We'll convert each bullet-ish sentence intofor each section heading. Inside each section, use
for prose,
- for lists. For About the role: we can have a paragraph describing company and role. Let's write: About the role: ChargePoint is at the center of the EV revolution, powering one of the world’s leading EV charging networks and a comprehensive set of hardware, software and mobile solutions across North America and Europe. Since 2007, ChargePoint has focused on making the transition to electric easy for businesses, fleets and drivers. This high-impact transformation role sits within the CIO organisation, reporting to the Director Business Transformation, and works in close partnership with the CFO, CAO, and Chief Manufacturing & Supply Chain Officer. You will own the strategy and execution for modernising ChargePoint's financial and supply chain systems, embedding AI-driven automation, and driving data‑informed decision making. That captures. Responsibilities: list from "What You Will Be Doing". We'll break into items: - Own the Finance Technology Roadmap: define and drive multi-year strategy for ChargePoint's financial systems landscape (NetSuite core), aligning technology investment with CFO and CAO priorities. - Embed AI & Automation: identify and implement AI/ML-driven automation across financial close, reconciliation, AP/AR, and reporting — reducing manual effort, improving accuracy, accelerating close cycle. - Intelligent Close & Reconciliation: lead transformation of financial close process — designing workflows that leverage automation, exception‑based review, and real‑time data to drive speed and confidence. - AP/AR Process Innovation: modernise accounts payable and receivable processes through automation and integration — improving cash flow visibility, reducing processing time, strengthening controls. - Enterprise Performance Management: evolve EPM capabilities to give finance leadership timely, accurate, actionable insight into business performance — integrating planning, forecasting, reporting. - Evaluate & Integrate New Tools: continuously assess emerging finance technology — from AI‑native close tools to advanced analytics platforms — and make build‑vs‑buy recommendations with clear ROI. - Bridge Finance & Supply Chain: partner with Chief Manufacturing & Supply Chain Officer to connect supply chain decisions to financial outcomes — inventory valuation, cost of goods, procurement analytics, working capital visibility. - Demand & Inventory Intelligence: work with supply chain and finance teams to improve demand forecasting accuracy and inventory planning through better data, integration, analytical tooling. - Procurement & Vendor Analytics: drive visibility into procurement spend, supplier performance, contract compliance — surfacing insights for faster, better‑informed sourcing decisions. - Integrated Reporting: build reporting and dashboards that give CFO and CMSO a unified view of supply chain financial health — bridging operational and financial data. - Manage a small, high‑caliber team — including NetSuite functional and technical administrators and Business Analysts — with mandate to grow and evolve the team as transformation programme matures. We'll put each as
- .
Requirements: list items:
- 6–8 years of experience in finance technology, ERP transformation, or enterprise systems — with measurable outcomes across finance and/or supply chain.
- Direct experience across FP&A, financial close, AP/AR, procurement, expense management, and sales commissions.
- Hands‑on NetSuite experience required — functional ownership, implementation, or systems management.
- Demonstrated use of AI, ML, or automation tools in a finance or operations setting.
- Familiarity with EPM platforms — Oracle Hyperion, Anaplan, Workday Adaptive, or equivalent.
- Prior experience managing functional and/or technical teams.
- Bachelor’s degree in Finance, Accounting, or Information Systems required; MBA preferred but not mandatory.
We'll put as
- . Qualifications (the bullet list from "What You Will Bring"): - Finance Technology Depth: Strong command of enterprise finance systems — NetSuite is essential; exposure to Workday Financials, Oracle Hyperion/EPM, or Anaplan is a plus. - Finance Process Fluency: Hands‑on knowledge of FP&A, monthly/quarterly/annual close, AP/AR, procurement, expense management, sales commission processing, and revenue reporting. - AI & Automation Mindset: Practical experience shipping AI or automation within a finance context — not just planned it. - Supply Chain Literacy: Enough supply chain knowledge to connect operations decisions to financial outcomes — inventory, procurement, and COGS visibility. - Team Leadership: Experience managing and growing functional and technical teams — setting direction, building capability, delivering results. -