Manager, AP
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to extract substantive content: The posting includes:
- Intro about CoreWeave (company description) – maybe not needed? It's not a section heading but could be part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Manager, Accounts Payable". Not needed.
We need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (from "What You’ll Do" and details). Requirements/Qualifications (from "Who You Are" and "Preferred Experience"). Skills (maybe from "Hands-on experience with ERP systems", "Advanced Excel skills", etc). Benefits (from "What We Offer" list). Pay (from "The base salary range for this role is $115,000 to $153,000." plus note about starting salary). Schedule? Not mentioned; no schedule info, so we should NOT create Schedule section.
We must not include filler like "commensurate with experience". The Pay section we have actual numbers, so we can include.
We must remove boilerplate: California Applicants, EEO, Export Control Compliance, etc. Also remove "Wondering if you’re a good fit?" maybe keep as part of "Who You Are"? It's somewhat fluff but maybe we can keep as part of "About the role"? The instruction: remove duplicated lines, application instructions. The "Wondering if you’re a good fit?" is not boilerplate but maybe considered fluff; but we can keep if it's substantive? It's more like motivational. Could be omitted. Safer to keep only concrete info.
We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all details from sections.
Let's parse:
Company description: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com."
Is this substantive? It's about company, not role. Might be considered background but not required. The instruction: "Prefer a few substantive sections over many thin ones." Could include as part of "About the role"? But "About the role" heading is for role description. The company description could be omitted as not directly about role. However, we must preserve ALL substantive information; does that include company description? It's substantive about the employer. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it, maybe as a
before sections, not as a heading. Since we cannot add arbitrary headings not listed, we can just put it as a paragraph.
Then "What You’ll Do" is responsibilities.
Then "About The Role" is more details.
Then "Who You Are" is requirements/qualifications.
Then "Preferred Experience" is preferred qualifications.
Then "Wondering if you’re a good fit?" maybe we can ignore as fluff.
Then "Why CoreWeave? About At CoreWeave, we work hard, have fun, and move fast! ..." This is culture description; could be considered substantive but maybe fluff. It's about company values. Could keep as paragraph.
Then compensation and benefits.
Then "What We Offer" list of benefits.
Then California Applicants etc - remove.
Thus sections:
- About the role (maybe combine "What You’ll Do" and "About The Role").
But we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can decide to use:
About the role
- includes company description and role overview? Might be redundant.
Better: Use About the role
for the paragraph describing the role (from "About The Role").
Use Responsibilities
for the duties list (from "What You’ll Do" and details).
Use Requirements
for mandatory qualifications (from "Who You Are").
Use Preferred Qualifications
maybe but not in allowed headings; we have Qualifications and Skills. Could put preferred under Qualifications or Skills. The instruction: Use headings from list; we can use Qualifications for required, Skills for preferred/experience.
But we need to preserve all info; we can split: Requirements (mandatory) and Qualifications (preferred) or Skills.
Let's map:
Mandatory: 8+ years experience in AP or Accounting, including 3+ years leading teams within shared services, GBS, or corporate accounting environment across both Indirect and Direct spend types; Proven strong experience in Direct spend type, understanding inventory, 3-way match, and GRIR process; Have thrived in high-growth, scaling environments, balancing long-term process designs with hands-on execution; Demonstrated experience supporting Procure-to-Pay (P2P) processes end-to-end; Maintain a strong controls mindset aligned to SOX, and can confidently partner with Accounting, Procurement, FP&A, and IT.; Hands-on experience managing high-volume invoice processing, payment batch runs, and related banking functions; Proven ability to support month-end close activities, including AP accruals and reconciliations; Hands-on experience with ERP systems (e.g., NetSuite, SAP, Coupa); Advanced Excel skills for reporting, reconciliations, and data analysis.
Preferred: Experience working within a Global Business Services or Shared Services model; Exposure to AP automation, workflow tools, or process transformation initiatives; Experience supporting a publicly traded company or pre-IPO environment; Familiarity with sales/use tax, VAT, or international vendor payments; Experience partnering cross-functionally with Procurement and Finance stakeholders; Experience with payment runs and bank functions.
Skills: maybe we can list ERP systems, Advanced Excel, etc as skills.
But we already have those in mandatory. Could treat them as skills.
Better: Use Requirements for mandatory experience/years, Qualifications for preferred, Skills for technical skills (ERP, Excel). But we have overlapping.
Given instruction to prefer few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section "Requirements" that includes both mandatory and preferred, but we need to differentiate? Not required.
We could have:
About the role
(paragraph describing role)
Responsibilities
(list of duties)
Requirements
(list of mandatory + preferred qualifications)
Benefits
(list)
Pay
(paragraph with salary range)
We can omit Skills if we incorporate into Requirements.
We must not create Schedule.
Now we need to extract responsibilities list from "What You’ll Do" and details.
"What You’ll Do": The Global Business Services (GBS) team at CoreWeave is responsible for centralizing, standardizing, and scaling foundational business processes across Finance, Procurement, and HR. As part of GBS, the Accounts Payable function plays a critical role in CoreWeave’s Procure-to-Pay (P2P) process, ensuring operational excellence, strong controls, and high-quality service delivery as the company scales globally in a public-company environment.
Then "About The Role": The Manager, Accounts Payable is a critical member of CoreWeave’s GBS organization, responsible for leading day-to-day Accounts Payable operations while supporting the end-to-end Procure-to-Pay (P2P) process. This role combines hands-on operational execution with strategic leadership in process standardization, automation, and continuous improvement to build scalable infrastructure aligned with CoreWeave’s hyper-growth and SOX-compliant framework. This role will primarily oversee AP operations across Direct spend, including 2- and 3-way matching, exception management, disbursements, vendor inquiries, and close activities, while also serving as an escalation point for complex payment holds and blockers. Focused on operational excellence, the AP Manager drives improvements in cycle time, first-pass yield, and on-time payment performance, strengthens PO and receiving discipline, and reduces root-cause drivers of recurring exceptions. The role also maintains strong internal controls, ensures segregation of duties, supports internal and external audits, and leads remediation efforts. In partnership with Procurement, Treasury, Tax, Finance, and Accounting, the AP Manager designs and enhances ERP and AP workflows—including OCR, approvals, and system integrations—to reduce manual touchpoints and improve data integrity. Additionally, this role elevates vendor experience and assists in oversight of BPO/offshore partners through clear SLAs and KPIs.
We can combine these into a responsibilities list.
Let's create bullet list:
- Lead day-to-day Accounts Payable operations and support end-to-end Procure-to-Pay (P2P) process.
- Oversee AP operations across Direct spend, including 2- and 3-way matching, exception management, disbursements, vendor inquiries, and close activities.
- Serve as escalation point for complex payment holds and blockers.
- Drive improvements in cycle time, first-pass yield, and on-time payment performance.
- Strengthen PO and receiving discipline; reduce root-cause drivers of recurring exceptions.
- Maintain strong internal controls, ensure segregation of duties, support internal and external audits, lead remediation efforts.
- Partner with Procurement, Treasury, Tax, Finance, and Accounting to design and enhance ERP and AP workflows (OCR, approvals, system integrations) to reduce manual touchpoints and improve data integrity.
- Elevate vendor experience and assist in oversight of BPO/offshore partners through clear SLAs and KPIs.
- Centralize, standardize, and scale foundational business processes across Finance, Procurement, and HR (as part of GBS).
Now requirements list:
Mandatory:
- 8+ years of experience in Accounts Payable or Accounting, including 3+ years leading teams within a shared services, GBS, or corporate accounting environment across both Indirect and Direct spend types.
- Proven strong experience in the Direct spend type, understanding inventory, 3-way match, and GRIR process.
- Have thrived in high-growth, scaling environments, balancing long-term process designs with hands-on execution.
- Demonstrated experience supporting Procure-to-Pay (P2P) processes end-to-end.
- Maintain a strong controls mindset aligned to SOX, and can confidently partner with Accounting, Procurement, FP&A, and IT.
- Hands-on experience managing high-volume invoice processing, payment batch runs, and related banking functions.
- Proven ability to support month-end close activities, including AP accruals and reconciliations.
- Hands-on experience with ERP systems (e.g., NetSuite, SAP, Coupa).
- Advanced Excel skills for reporting, reconciliations, and data analysis.
Preferred:
- Experience working within a Global Business Services or Shared Services model.
- Exposure to AP automation, workflow tools, or process transformation initiatives.
- Experience supporting a publicly traded company or pre-IPO environment.
- Familiarity with sales/use tax, VAT, or international vendor payments.
- Experience partnering cross-functionally with Procurement and Finance stakeholders.
- Experience with payment runs and bank functions
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to extract substantive content: The posting includes: - Intro about CoreWeave (company description) – maybe not needed? It's not a section heading but could be part of About the role? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Manager, Accounts Payable". Not needed. We need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (from "What You’ll Do" and details). Requirements/Qualifications (from "Who You Are" and "Preferred Experience"). Skills (maybe from "Hands-on experience with ERP systems", "Advanced Excel skills", etc). Benefits (from "What We Offer" list). Pay (from "The base salary range for this role is $115,000 to $153,000." plus note about starting salary). Schedule? Not mentioned; no schedule info, so we should NOT create Schedule section. We must not include filler like "commensurate with experience". The Pay section we have actual numbers, so we can include. We must remove boilerplate: California Applicants, EEO, Export Control Compliance, etc. Also remove "Wondering if you’re a good fit?" maybe keep as part of "Who You Are"? It's somewhat fluff but maybe we can keep as part of "About the role"? The instruction: remove duplicated lines, application instructions. The "Wondering if you’re a good fit?" is not boilerplate but maybe considered fluff; but we can keep if it's substantive? It's more like motivational. Could be omitted. Safer to keep only concrete info. We need to preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all details from sections. Let's parse: Company description: "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com." Is this substantive? It's about company, not role. Might be considered background but not required. The instruction: "Prefer a few substantive sections over many thin ones." Could include as part of "About the role"? But "About the role" heading is for role description. The company description could be omitted as not directly about role. However, we must preserve ALL substantive information; does that include company description? It's substantive about the employer. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep it, maybe as a
before sections, not as a heading. Since we cannot add arbitrary headings not listed, we can just put it as a paragraph. Then "What You’ll Do" is responsibilities. Then "About The Role" is more details. Then "Who You Are" is requirements/qualifications. Then "Preferred Experience" is preferred qualifications. Then "Wondering if you’re a good fit?" maybe we can ignore as fluff. Then "Why CoreWeave? About At CoreWeave, we work hard, have fun, and move fast! ..." This is culture description; could be considered substantive but maybe fluff. It's about company values. Could keep as paragraph. Then compensation and benefits. Then "What We Offer" list of benefits. Then California Applicants etc - remove. Thus sections: - About the role (maybe combine "What You’ll Do" and "About The Role"). But we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to use: