Account Executive - Greenfield

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate. We need to parse the posting. Key sections: - About The Role: description of role responsibilities. Could be considered "About the role" or "Responsibilities". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading then paragraphs. - Responsibilities: maybe we can extract bullet list of duties from "What You'll Do" and "About The Role". The posting includes bullet-like sentences but not actual bullet list. We need to convert to

• . We must preserve all substantive info. - Requirements: maybe "Who You Are" list of required experience. - Qualifications: maybe "Preferred Experience" is qualifications? Actually "Preferred Experience" could be qualifications or preferred. We'll treat as "Qualifications" maybe. - Skills: maybe not explicit; could be derived from required skills like technical discovery, PoV fluency, etc. Might be covered in Requirements. - Benefits: there is a section "Why CoreWeave?" includes benefits list: base salary range, discretionary bonus, equity awards, comprehensive benefits program, then "What We Offer" includes list of benefits: medical, dental, vision insurance, etc. Also "The base salary range for this role is $165,000 to $195,000." That's Pay. - Schedule: not mentioned; we should not include Schedule unless present. No schedule info. - Pay: we have base salary range. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to remove boilerplate: cookie/navigation/legal/EEO etc. At end there is California Applicants, EEO, Export Control Compliance. Those are boilerplate; we should drop them. Also drop "Wondering if you're a good fit?" maybe not boilerplate but could be considered fluff; but it's substantive? It's more like encouraging. Might be considered filler but not prohibited. Safer to keep? It's not a list; it's a paragraph encouraging. Might keep as part of About the role? But it's after "Why CoreWeave?" Actually after "Why CoreWeave?" there is a paragraph about culture then "Wondering if you're a good fit?" then list of qualities. That could be considered part of "About the role" or "Qualifications"? Might be considered "Preferred Experience"? It's more about cultural fit. Could be included under "Qualifications" or "Skills". But we can keep as a paragraph under "About the role" or "Qualifications". However instruction: Prefer a few substantive sections over many thin ones. We could combine cultural fit into "About the role" or "Qualifications". Let's decide: We'll have sections: - About the role (paragraph summarizing role purpose) - Responsibilities (ul list of duties) - Requirements (ul list of required experience) - Qualifications (ul list of preferred experience) - Benefits (ul list of benefits) - Pay (p with salary range) We must not repeat job title. No headings for Job ID. Now extract content. About the role: The posting says "About The Role This is a pure hunter role. You will own net-new logo acquisition across a greenfield Enterprise territory (5,000+ employee organizations), selling the full CoreWeave platform — GPU cloud infrastructure and AI developer tooling — as a unified solution. You will build pipeline from zero, run technical discovery across infrastructure and software buying centers, and close complex, multi-product enterprise contracts. You won't inherit a book. You build one." We can keep that as paragraph(s). Could also include "Own all net-new logo acquisition in a defined Enterprise territory" etc. Actually that repeats. We'll combine. Responsibilities: list from bullet-like sentences under "What You'll Do" and "About The Role". Let's extract: - Own all net-new logo acquisition in a defined Enterprise territory - Sell the full CoreWeave platform as a unified solution: GPU cloud infrastructure and AI developer tooling, independently and as a bundled offering - Build pipeline through cold outbound, PLG signal tracking, and account-based strategies — consistently booking 4–5 qualified meetings per week - Construct a focused target account list from a large, noisy territory — prioritize accounts with active AI infrastructure spend or free-tier platform adoption - Engage developers, ML engineers, infrastructure leads, and technical executives (CTOs, VPs of Eng/ML, Heads of AI Infrastructure) early — before formal buying motions exist - Run structured technical discovery across both compute and software buying centers to surface pain, map architecture, and build a case for change - Lead business justification readouts and executive presentations that connect CoreWeave's platform to measurable infrastructure and model development outcomes - Partner with Solution Architects to co-design and execute technical Proof of Values (PoVs) across compute provisioning, model training workflows, and AI developer tooling - Convert PLG free-tier usage into enterprise platform contracts — identify adoption signals and build multi-product expansion justification - Manage full sales cycles from cold outreach through close including MSA negotiation, procurement, security review, and legal - Maintain rigorous pipeline hygiene, forecasting, and activity tracking in CRM That seems comprehensive. Requirements: from "Who You Are": - 7+ years total in B2B sales with a consistent track record of quota attainment - 3+ years in enterprise sales (5,000+ employee organizations), navigating complex, multi-stakeholder, multi-product cycles - 3+ years selling developer tools, technical infrastructure, or AI/ML software — you can hold a meaningful conversation with an ML engineer, infrastructure architect, or CTO - Experience selling both infrastructure/cloud and SaaS products — you understand how compute and software buying motions differ and how to navigate both within the same account - Ranked #1 or #2 on your team in self-sourced pipeline generation — 4–5 qualified meetings per week is your baseline - Demonstrated record of cold-sourcing and closing enterprise logos with business justification readouts to VP/C-suite buyers - PLG motion expertise — you convert bottoms-up product adoption into top-down enterprise contracts - Technical discovery skills — you ask the right questions to surface infrastructure pain, map ML workflows, and identify multi-product opportunities - PoV fluency — you've co-designed and run technical proofs of value with Solution Architects and navigated procurement across the finish line - Effective with or without SDR support — you've built pipeline from scratch and know how to leverage SDRs when available Qualifications: from "Preferred Experience": - Experience selling GPU cloud, HPC, or AI infrastructure (compute, networking, storage) - Background selling AI/ML, MLOps, LLMOps, or adjacent developer tooling alongside infrastructure products - Familiarity with multi-product or platform sales — landing with one product and expanding into a second buying center - Experience at a company with a PLG motion and an enterprise sales overlay - Familiarity with MEDDPICC or Command of the Message sales frameworks Also maybe "Wondering if you're a good fit?" list could be considered qualifications but we can ignore or include under Qualifications as cultural fit. But we already have Qualifications; we could add those as extra bullet points under Qualifications. However they are more about personal traits. Could be considered "Skills". But we have no Skills section. Could create Skills section for those traits. But instruction: prefer few substantive sections over many thin ones. Might combine them into Qualifications or Requirements. I'd add them under Qualifications as additional bullets. List from "Wondering if you're a good fit?": - You love the hunt — pipeline creation and net-new logos energize you more than account management - You're curious about how AI infrastructure is being built and scaled — you understand the compute side as much as the software side - You're an expert at earning trust with technical buyers — developers, infrastructure leads, and CTOs take your calls because you add signal, not noise We can add those under Qualifications. Benefits: from "Why CoreWeave?" and "What We Offer". Let's extract: - Base salary range: $165,000 to $195,000 (but that's Pay) - Discretionary bonus - Equity awards - Comprehensive benefits program (all based on eligibility) - Medical, dental, and vision insurance - 100% paid for by CoreWeave - Company-paid Life Insurance - Voluntary supplemental life insurance - Short and long-term disability insurance - Flexible Spending Account - Health Savings Account - Tuition Reimbursement - Ability to Participate in Employee Stock Purchase Program (ESPP) - Mental Wellness Benefits through Spring Health - Family-Forming support provided by Carrot - Paid Parental Leave - Flexible, full-service childcare support with Kinside - 401(k) with a generous employer match - Flexible PTO - Catered lunch each day in our office and data center locations - A casual work environment - A work culture focused on innovative disruption Also note: "The base salary range for this role is $165,000 to $195,000." That's Pay. We should separate Pay and Benefits. Pay: paragraph with base salary range and note that starting salary determined based on job-related knowledge, skills, experience, market location. Also mention discretionary bonus, equity awards? Actually those are part of total rewards. But Pay section likely just base salary. We'll include base salary range and note that starting salary determined based on factors. Benefits: list of benefits as above (excluding base salary). Also mention discretionary bonus, equity awards, comprehensive benefits program. We'll create Benefits ul list. Now ensure we don't include boilerplate: California Applicants, EEO, Export Control Compliance. Remove. Now produce HTML fragment with headings

  and content. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  ...

  Qualifications

  ...

  Benefits

  ...

  Pay

  ...

  No Schedule. Make sure to preserve all substantive info. Not missing any. Let's craft paragraphs. About the role paragraph: Combine sentences. "This is a pure hunter role. You will own net-new logo acquisition across a greenfield Enterprise territory (5,000+ employee organizations), selling the full CoreWeave platform — GPU cloud infrastructure and AI developer tooling — as a unified solution. You will build pipeline from zero, run technical discovery across infrastructure and software buying centers, and close complex, multi-product enterprise contracts. You won't inherit a book; you build one." That's good. Now Responsibilities list as above. Requirements list as above. Qualifications list: combine Preferred Experience and cultural fit bullets. Let's list: - Experience selling GPU cloud, HPC, or AI infrastructure (compute, networking, storage) - Background selling AI/ML, MLOps, LLMOps, or adjacent developer tooling alongside infrastructure products - Familiarity with multi-product or platform sales — landing with one product and expanding into a second buying center - Experience at a company with a PLG motion and an enterprise sales overlay - Familiarity with MEDDPICC or Command of the Message sales frameworks - You love the hunt — pipeline creation and net-new logos energize you more than account management - You're curious about how AI infrastructure is being built and scaled — you understand the compute side as much as the software side - You're an expert at earning trust with technical buyers — developers