Enterprise Account Executive - API Solutions

We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. Must not include boilerplate like EEO, legal, etc. Must remove duplicated lines, navigation, cookie, etc. Must preserve all substantive info. We need to parse the posting. Key parts: - Intro: "The role We are looking to hire a Enterprise Account Executive - API Solutions to join our North America sales team in New York. This is an on-site role out of our New York office Base Salary: $120,000 - $150,000 with competitive OTC." - Then "Working at WGSN Together, we create tomorrow ..." This is description of company; maybe part of "About the role"? Actually there is a section "About The Role" later. - Then "About The Role We are seeking a high performing Enterprise Account Executive to drive new logo acquisition for the WGSN Intelligence API. ..." This is description. - Then "Key Accountabilities" bullet list? Actually they list items with headings: Pipeline Generation:, Technical & Consultative Selling:, Deal Ownership & Orchestration:, IP Protection & Commercial Discipline:, Pipeline & Forecast Management:. These are likely responsibilities. - Then "Skills, Experience & Qualifications" paragraph with bullet-like sentences. - Then "What We Offer" benefits list. - Then "More About WGSN" includes values, culture etc. Might be considered "About the company" but not required as a section unless we have content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We can include sections like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We have Pay (Base Salary). We have Benefits (What We Offer). We have Responsibilities (Key Accountabilities). We have Skills/Experience/Qualifications (Skills, Experience & Qualifications). Possibly "About the role" could be combined with responsibilities? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have headings: About the role, Responsibilities, Skills, Experience & Qualifications (maybe combine?), Benefits, Pay. We must not create sections like Schedule if not present. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive info; do not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

We are looking to hire a Enterprise Account Executive - API Solutions to join our North America sales team in New York. This is an on-site role out of our New York office. Base Salary: $120,000 - $150,000 with competitive OTC.

But note Pay section separate? Actually we have Base Salary info; we could put in Pay section. But we also have it in About the role paragraph. Might duplicate. Better to separate: About the role paragraph describing role, and Pay section for salary. But we must not repeat info? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication but better to keep each piece once. We can put salary in Pay section and not repeat in About the role. However the About the role paragraph currently includes salary; we could remove salary from there and put in Pay. But we must preserve all info; moving it is okay as long as not lost. So we can have About the role paragraph without salary, and Pay section with salary. Let's extract About the role description: "We are looking to hire a Enterprise Account Executive - API Solutions to join our North America sales team in New York. This is an on-site role out of our New York office." That's it. Then Pay: "Base Salary: $120,000 - $150,000 with competitive OTC." Now Responsibilities: The Key Accountabilities list. We need to turn each into

• . The headings like "Pipeline Generation:" etc could be either as
• with bold? But we can just make each as
• containing the sentence. Thus:

  Responsibilities

  • Pipeline Generation: Proactively source and build a net-new enterprise pipeline targeting C suite and VP level buyers (Chief Digital, Data, Innovation, and Product Officers).
  • Technical & Consultative Selling: Lead end-to-end sales cycles for complex, high-value API integrations. Conduct deep consultative discovery to map WGSN API capabilities directly to client technical architectures and business cases.
  • Deal Ownership & Orchestration: Direct the complete sales process from origination to signature. Strategically pull in internal technical specialists only when needed for deep scoping.
  • IP Protection & Commercial Discipline: Structure deals within established pricing and legal guardrails, ensuring strict protection of WGSN’s intellectual property, training-data exclusions, and brand attribution.
  • Pipeline & Forecast Management: Maintain accurate forecasting, deal stage hygiene, and pipeline coverage metrics.
  Now Skills, Experience & Qualifications: The paragraph includes multiple sentences. Could be turned into
  • each? The instruction: Use
    • for any list of duties/requirements/benefits. This is a list of qualifications/skills; we can treat as list. Thus:

      Skills, Experience & Qualifications

      • Background in trend intelligence, syndicated consumer data, SaaS, or enterprise AI/ML platforms is preferred.
      • Consistent history of exceeding quotas in an individual contributor, net-new enterprise hunting role closing $1M+ multi-year deals.
      • Ability to independently lead technical discussions with senior data and technology buyers.
      • Solid working knowledge of enterprise integration models, including REST/streaming APIs, authentication, and enterprise AI/ML architectures (e.g., RAG, embedded copilots, AI agents).
      • Expert at navigating complex, multi-stakeholder enterprise environments across technical, product, and commercial business units.
      • Strong qualification discipline; ability to identify non-viable deals early and protect IP standards without compromising revenue goals.
      • Existing network of senior digital, data, and innovation leaders within Tier-1 retail and consumer brands preferred.
      • Familiarity with AI content licensing models, including training-data protections and brand attribution terms is preferred.
      Now Benefits: "What We Offer" list. We need to capture each benefit item. Paragraph: "Our benefits and wellbeing package offers flexible benefits you can tailor to your own personal needs, including:" then list: - Paid Time Off – 15 days of vacation per year with an additional day for each year of service up to 20 days. WGSN also observes the 12 Federal holidays. - We also offer 6 weeks of paid Parental Leave - 401(k) Retirement Savings Plan – allows employees to save and invest for their own retirement on a tax deferred basis. WGSN matches 50% of the first 6% contributed by employees - Dental and Vision plans with MetLife - Health Care with Anthem & Blue Cross Blue Shield - Life Insurance, AD&D, Short and Long-Term Disability - all eligible employees receive coverage at no cost through Metlife - Mental Health – WGSN provides many ways for employees to access mental health care including an Employee Assistance Program and inpatient, outpatient and virtual care if enrolled in an Anthem medical plan. Our EAP is available to all permanent staff, regardless of if you elect benefits We should keep as list items. Thus:

      Benefits

      • Paid Time Off – 15 days of vacation per year with an additional day for each year of service up to 20 days. WGSN also observes the 12 Federal holidays.
      • We also offer 6 weeks of paid Parental Leave.
      • 401(k) Retirement Savings Plan – allows employees to save and invest for their own retirement on a tax deferred basis. WGSN matches 50% of the first 6% contributed by employees.
      • Dental and Vision plans with MetLife.
      • Health Care with Anthem & Blue Cross Blue Shield.
      • Life Insurance, AD&D, Short and Long-Term Disability - all eligible employees receive coverage at no cost through Metlife.
      • Mental Health – WGSN provides many ways for employees to access mental health care including an Employee Assistance Program and inpatient, outpatient and virtual care if enrolled in an Anthem medical plan. Our EAP is available to all permanent staff, regardless of if you elect benefits.
      Now we might also have "More About WGSN" which includes values, culture etc. Could be considered "About the company" but not in the list of headings. The instruction only mentions those example headings; we could add a section like "About WGSN" if we want, but not required. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to. But we should prefer few substantive sections over many thin ones. The "More About WGSN" is substantive but could be considered "About the company". However we already have "About the role". Might be okay to add another section "About WGSN". But we need to see if it's necessary. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The "More About WGSN" has real content. So we could include a section like "About WGSN". However the list of example headings didn't include "About the company". But we could still use

      for any heading; they gave examples. It's probably okay to add a section like "About WGSN". But to keep few sections, maybe we can incorporate that into "About the role"? Not really. The "About the role" is about the role; the company description is separate. Could be considered "About the company". But not in the list; but we can still use heading. Given the instruction to prefer few substantive sections over many thin ones, we have About the role, Responsibilities, Skills, Experience & Qualifications, Benefits, Pay. That's 6 sections. Adding About WGSN would be 7. Might be okay but maybe we can omit because it's not essential to the job posting? However the instruction says preserve ALL substantive information. So we must keep that info somewhere. If we omit a section, we lose that info. So we need to include it. Thus add a section "About WGSN" with the content. We need to extract the substantive content from "More About WGSN" and following paragraphs: "WGSN is the global authority on consumer trend forecasting. We help brands around the world create the right products at the right time for tomorrow’s consumer. Our values ..." then sections: We Are Everywhere, We Are Future Focused, We Are Rigorous, Our culture, Inclusive workforce, Recognising great performance, flexible working environment, A Note for Applicants, A Note for Recruiters. We must remove boilerplate like EEO, legal, etc. The "A Note for Applicants" and "A Note for Recruiters" might be considered boilerplate? They are about hiring process; maybe we should keep as they are substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.