Jobs · Business Development · New York

Enterprise Account Executive - API Solutions

WGSN · New York, United States · 1 mo ago
On-siteBusiness Development$120k–$150k/yrFull-time
We need to output HTML fragment with headings

for 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 as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO etc). Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes Base Salary: $120,000 - $150,000 with competitive OTC. So Pay section can be included with that info. Benefits: they list benefits in "What We Offer". So Benefits section can be included. Schedule: they mention "This is an on-site role out of our New York office." That's schedule info (on-site). So Schedule section can be included. Also we have "About The Role" section content. Responsibilities: there is "Key Accountabilities" bullet list. That can be Responsibilities. Skills, Experience & Qualifications: that can be Skills (or Qualifications). They also have "Background in trend intelligence..." etc. That's qualifications/skills. We can combine into Skills section. Requirements maybe not separate; but we have "Skills, Experience & Qualifications". Could treat as Skills. Could also have Qualifications section but we might avoid duplication. The instruction: prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Skills, Benefits, Pay, Schedule. Possibly also Qualifications but maybe combine with Skills. Let's decide sections: - About the role (the paragraph after "About The Role") - Responsibilities (the "Key Accountabilities" list) - Skills (the "Skills, Experience & Qualifications" list) - Benefits (the "What We Offer" list) - Pay (Base Salary line) - Schedule (on-site role) We must not include headings with empty content. Ensure we use
  • for any list of duties/requirements/benefits. For prose use

    . We need to preserve all substantive information. Let's extract. Job posting text: "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. Working at WGSNTogether, we create tomorrow A career with WGSN is fast-paced, exciting and full of opportunities to grow and develop. We're a team of consumer and design trend forecasters, content creators, designers, data analysts, advisory consultants and much more, united by a common goal: to create tomorrow. WGSN's trusted consumer and design forecasts power outstanding product design, enabling our customers to create a better future. Our services cover consumer insights, beauty, consumer tech, fashion, interiors, lifestyle, food and drink forecasting, data analytics and expert advisory. If you are an expert in your field, we want to hear from you." Then "About The Role We are seeking a high performing Enterprise Account Executive to drive new logo acquisition for the WGSN Intelligence API. For 28 years, WGSN has provided category-leading trend intelligence to the world’s top consumer brands. As enterprise clients rebuild their systems around AI, this role is responsible for selling high-value, direct API integrations that embed WGSN’s proprietary intelligence into client design tools, merchandising platforms, e-commerce environments, and AI agents. This is a pure hunting role focused on closing complex, enterprise integration deals across fashion, beauty, retail, consumer goods, and fintech." Then "Key Accountabilities 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." Then "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." Then "What We Offer Our benefits and wellbeing package offers flexible benefits you can tailor to your own personal needs, including: - 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." Then more about WGSN etc (boilerplate). We should remove boilerplate like "More About WGSN", values, culture, etc. Also remove "A Note for Applicants", "A Note for Recruiters". Also remove any EEO etc. Not present. We need to keep all substantive info: the description about WGSN (the mission) maybe considered substantive? It's part of "Working at WGSN..." paragraph. That is substantive about company. Should we keep? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "More About WGSN" etc might be considered boilerplate? It's describing company values etc. Might be considered substantive? The instruction says remove boilerplate, but not exactly define. The "More About WGSN" seems like generic company description; could be considered boilerplate but also part of job posting. However earlier they had "Working at WGSNTogether, we create tomorrow..." which is also company description. Might be okay to keep that as part of About the role? But we already have About the role section; we could incorporate that paragraph into About the role as prose. However the instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So About the role heading should contain the role description. The initial paragraph about WGSN could be part of About the role. Let's include it. Thus About the role section will combine: - The initial paragraph: "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." Wait Base Salary is separate; we will put in Pay section. So maybe we keep the location and on-site info in About the role or Schedule? The schedule section will have on-site. So we can move location and on-site to Schedule. The About the role should focus on role description: "We are seeking a high performing Enterprise Account Executive to drive new logo acquisition for the WGSN Intelligence API. For 28 years, WGSN has provided category-leading trend intelligence to the world’s top consumer brands. As enterprise clients rebuild their systems around AI, this role is responsible for selling high-value, direct API integrations that embed WGSN’s proprietary intelligence into client design tools, merchandising platforms, e-commerce environments, and AI agents. This is a pure hunting role focused on closing complex, enterprise integration deals across fashion, beauty, retail, consumer goods, and fintech." Also we could include the earlier sentence about "We are looking to hire..." but that's more generic. Might be okay to include as part of About the role. However we already have location and on-site elsewhere. Let's keep About the role as the description after "About The Role". We'll also include the initial sentence "We are looking to hire a Enterprise Account Executive - API Solutions to join our North America sales team in New York." as part of About the role? Might be redundant. But we can include it. Better to follow the posting: after "The role" they have that paragraph. Then "Working at WGSN..." then "About The Role". So we could treat "The role" as About the role. Let's just put About the role content as: "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 then we duplicate Base Salary and on-site. Better to separate. Given the instruction to avoid duplication, we should not repeat same info in multiple sections. So we should split: location and on-site go to Schedule; Base Salary goes to Pay; the rest about role goes to About the role. Thus About the role: "We are seeking a high performing Enterprise Account Executive to drive new logo acquisition for the WGSN Intelligence API. For 28 years, WGSN has provided category-leading trend intelligence to the world’s top consumer brands. As enterprise clients rebuild their systems around AI, this role is responsible for selling high-value, direct API integrations that embed WGSN’s proprietary intelligence into client design tools, merchandising platforms, e-commerce environments, and AI agents. This is a pure hunting role focused on closing complex, enterprise integration deals across fashion, beauty, retail, consumer goods, and fintech." Also maybe include the earlier "We are looking to hire a Enterprise Account Executive - API Solutions to join our North America sales team in New York." as part of About the role? But that mentions location; we already have location in Schedule. Could keep it but then location duplicated. Better to keep only the role description. Now Responsibilities: the Key Accountabilities list. We'll turn each bullet into
  • . The text includes colon after each heading. We'll keep as is. Responsibilities content: - 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

Similar jobs