Head of Enterprise Sales
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". So we need to parse the posting.
We have sections: Who We Are (company description). The Way We Work (values). Head of Enterprise Sales Team: Revenue Location: [NYC] - Hybrid Reports to: VP, Sales or CRO (metadata). About Lightning AI (repeat of Who We Are?). About The Role (role description). What You'll Do (responsibilities). What We're Looking For (requirements/qualifications). Nice-to-Haves (nice-to-have skills). Why Lightning AI (motivation). Benefits And Perks (benefits). Also there is compensation: "The anticipated annual base salary range for this role is: $225,000 - $260,000 USD". Also mention discretionary bonus, equity, etc.
We need to produce sections: maybe About the role (could be About Lightning AI? Actually "About Lightning AI" is company overview; "About The Role" is role overview). We'll include sections: About the Company (maybe not required but we can include as "About Lightning AI" as a section heading? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those categories. However we can include "About the role" as heading for role overview. "Responsibilities" for What You'll Do. "Requirements" for What We're Looking For. "Nice-to-haves" maybe as Skills? Could be Skills. Benefits as Benefits. Pay as Pay. Schedule maybe not present (hybrid work). There's mention of hybrid work model; we could include Schedule section with hybrid info. But we need to only include if real specific content. There's "Location: [NYC] - Hybrid". Also "Flexible Work: Flexible schedules and a hybrid work model". So we can include Schedule.
We need to avoid boilerplate like EEO etc. Remove that.
We need to preserve all substantive info. So we need to include company description, values maybe? The Way We Work could be part of About the company? Might be considered "About Lightning AI" but we can include as a paragraph under About the role? Not sure. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine some.
Let's decide sections:
- About the role (company overview + role overview). Could be two paragraphs: company description and role summary.
- Responsibilities (What You'll Do) as ul.
- Requirements (What We're Looking For) as ul.
- Skills (Nice-to-Haves) as ul.
- Benefits (Benefits And Perks) as ul.
- Pay (compensation range + bonus/equity) as p.
- Schedule (hybrid/flexible work) as p.
We must not repeat job title as heading. The job title is "Head of Enterprise Sales Team"? Actually posting says "Head of Enterprise Sales Team: Revenue". But the role is Director of Sales? The title maybe "Head of Enterprise Sales Team". We'll not use as heading.
We need to output only HTML fragment.
Let's extract content.
Company description: "Who We Are Lightning AI is the company behind PyTorch Lightning. Founded in 2019, we build an end-to-end platform for developing, training, and deploying AI systems—designed to take ideas from research to production with less friction. Through our merger with Voltage Park, a neocloud and AI Factory, Lightning AI combines developer-first software with cost-efficient, large-scale compute. Teams get the tools they need for experimentation, training, and production inference, with security, observability, and control built in. We serve solo researchers, startups, and large enterprises. Lightning AI operates globally with offices in New York City, San Francisco, Seattle, and London, and is backed by Coatue, Index Ventures, Bain Capital Ventures, and Firstminute."
Values: "The Way We Work The People Who Thrive Here Are Builders Who Move Fast, Communicate Openly, Take Ownership, And Continuously Improve Themselves, Their Teams, And Our Company. Here's What That Looks Like In Practice Move with Urgency: We move quickly, make thoughtful decisions, and keep momentum. We value action over perfection and learn by shipping.Take Ownership: We own outcomes, not just our individual work. We make decisions that move the company forward and follow through.Communicate Openly: We communicate directly, seek to understand, and create clarity for others. Honest conversations help us move faster together.Build Great Teams: We lead by example, empower others, and create healthy teams where people can do their best work.Raise the Bar: We're always improving ourselves. We learn from feedback, consistently challenge ourselves to grow, and focus on the work that matters most.Think Long-Term: We design for what's next. We create scalable systems, simplify complexity, and use AI and automation to amplify our impact."
We could include this as part of About the role or separate section "About the company". But headings list doesn't include About the company. However we could still include a heading like "About the company" but not in list; maybe okay. But instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. So we can incorporate company description and values into About the role section (maybe as preamble). Or we could have a section "About the company" but not in list; risk of being considered extra heading. I'd rather include under About the role.
Thus About the role heading About the role
then paragraphs containing company description, values, and role overview.
Role overview: "About Lightning AI Lightning AI is building the platform and infrastructure that make it dramatically easier for teams to develop, train, deploy, and scale AI systems. As the company behind PyTorch Lightning, and following our merger with Voltage Park, we bring together developer-first AI tooling with high-performance compute infrastructure for researchers, startups, and enterprises building at the frontier of AI. We operate with a simple set of values: Move Fast, Focus, Balance, Craftsmanship, and Minimal. We care about people who can operate with urgency, solve hard problems directly, and build with high standards without creating unnecessary complexity." That's similar to earlier but okay.
Then "About The Role We are looking for a Director of Sales to lead a high-performing enterprise sales team and help scale Lightning AI’s revenue engine across technical, strategic, and high-value accounts. This is a hands-on leadership role for someone who can coach complex enterprise selling, build durable operating rhythms, and help the team win with technical buyers across AI, infrastructure, engineering, research, and data organizations."
We'll combine.
Responsibilities: list from "What You'll Do". Items:
- Lead, coach, and scale a team of enterprise Account Executives focused on strategic and high-growth customers.
- Own team pipeline generation, forecast accuracy, deal inspection, and quota attainment.
- Build a rigorous sales operating cadence around territory planning, account strategy, pipeline creation, MEDDIC/MEDDPICC discipline, and executive alignment.
- Coach sellers through complex technical sales cycles involving ML leaders, infrastructure leaders, engineering executives, procurement, finance, and C-level stakeholders.
- Partner closely with ML Solutions Engineering, Customer Success, Partnerships, Marketing, Product, and Revenue Operations to create a repeatable enterprise GTM motion.
- Help define Lightning AI’s sales playbook for AI infrastructure, model development, training, deployment, and compute-intensive enterprise workloads.
- Identify blockers in the sales motion and build practical systems, content, inspection points, and feedback loops to remove them.
- Represent the voice of the customer internally and help shape product, packaging, pricing, and market positioning.
- Recruit and develop exceptional sales talent while building a culture of high accountability, curiosity, urgency, and craftsmanship.
Requirements: "What We're Looking For":
- 8+ years of enterprise technology sales experience, including 3+ years managing quota-carrying sellers.
- A track record of leading teams that consistently exceed target in complex, technical sales environments.
- Experience selling to technical buyers such as ML leaders, infrastructure leaders, CTOs, engineering executives, platform teams, or data organizations.
- Strong command of enterprise sales methodology, forecasting, deal inspection, pipeline generation, and multi-threaded account strategy.
- Ability to coach sellers on both strategic account planning and the practical details of running a deal well.
- Comfort operating in a fast-moving startup environment where the playbook is still being built.
- Clear communication, high judgment, and the ability to build trust quickly with executive customers and internal leaders.
Nice-to-Haves:
- Experience selling AI, cloud infrastructure, developer platforms, data platforms, MLOps, GPUs, or high-performance compute.
- Prior experience building a sales team or segment through a period of rapid growth.
- Deep familiarity with MEDDIC/MEDDPICC, command-of-the-message style positioning, or similar enterprise sales frameworks.
- Experience partnering closely with technical pre-sales or field engineering teams.
Why Lightning AI: maybe not needed as separate section; could be omitted or included under About the role. But we could include as a short paragraph under About the role? The instruction says prefer few substantive sections. Could omit Why Lightning AI as it's motivational but still substantive. Could include as a paragraph under About the role.
Benefits: list from Benefits And Perks:
- Comprehensive Health Coverage: Medical, dental, and vision coverage for employees and eligible dependents.
- Meaningful Equity: RSUs that give employees a stake in the company's long-term success.
- Retirement Savings: 401(k) matching (U.S.) and pension contributions (U.K.).
- Flexible Time Off: Unlimited PTO, company holidays, and floating holidays to support work-life balance.
- Company-Wide Winter Break: Two weeks of company closure each winter to disconnect and recharge.
- Paid Parental & Family Leave: Paid leave to support you and your family through life's important moments.
- Professional Development: Annual learning and development allowance to support your professional growth.
- Wellness Benefits: Wellness and work-from-home stipends to support your physical and mental well-being.
- Sabbatical Program: Four weeks of paid sabbatical leave after four years of service.
- Flexible Work: Flexible schedules and a hybrid work model for our office-based teams.
- In-Office Meals: Complimentary meals at our office hubs.
- Benefits may vary by location, team, and role.
We should keep the bullet points as - .
Pay: "The anticipated annual base salary range for this role is: $225,000 - $260,000 USD" plus "In addition to base salary, our total rewards package for eligible roles includes a discretionary bonus, a meaningful equity component, and comprehensive benefits." Also "Final offers are based on factors such as experience, skills, geographic location, and role expectations."
We'll put in a
.
Schedule: hybrid info: "Location: [NYC] - Hybrid" and "Flexible Work: Flexible schedules and a hybrid work model for our office-based teams." Also "Flexible Time Off" etc but that's benefits. So schedule: hybrid work model.
We'll output as
Schedule
Hybrid work model based in New York City with flexible schedules.
Now ensure we don
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". So we need to parse the posting. We have sections: Who We Are (company description). The Way We Work (values). Head of Enterprise Sales Team: Revenue Location: [NYC] - Hybrid Reports to: VP, Sales or CRO (metadata). About Lightning AI (repeat of Who We Are?). About The Role (role description). What You'll Do (responsibilities). What We're Looking For (requirements/qualifications). Nice-to-Haves (nice-to-have skills). Why Lightning AI (motivation). Benefits And Perks (benefits). Also there is compensation: "The anticipated annual base salary range for this role is: $225,000 - $260,000 USD". Also mention discretionary bonus, equity, etc. We need to produce sections: maybe About the role (could be About Lightning AI? Actually "About Lightning AI" is company overview; "About The Role" is role overview). We'll include sections: About the Company (maybe not required but we can include as "About Lightning AI" as a section heading? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those categories. However we can include "About the role" as heading for role overview. "Responsibilities" for What You'll Do. "Requirements" for What We're Looking For. "Nice-to-haves" maybe as Skills? Could be Skills. Benefits as Benefits. Pay as Pay. Schedule maybe not present (hybrid work). There's mention of hybrid work model; we could include Schedule section with hybrid info. But we need to only include if real specific content. There's "Location: [NYC] - Hybrid". Also "Flexible Work: Flexible schedules and a hybrid work model". So we can include Schedule. We need to avoid boilerplate like EEO etc. Remove that. We need to preserve all substantive info. So we need to include company description, values maybe? The Way We Work could be part of About the company? Might be considered "About Lightning AI" but we can include as a paragraph under About the role? Not sure. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine some. Let's decide sections: - About the role (company overview + role overview). Could be two paragraphs: company description and role summary. - Responsibilities (What You'll Do) as ul. - Requirements (What We're Looking For) as ul. - Skills (Nice-to-Haves) as ul. - Benefits (Benefits And Perks) as ul. - Pay (compensation range + bonus/equity) as p. - Schedule (hybrid/flexible work) as p. We must not repeat job title as heading. The job title is "Head of Enterprise Sales Team"? Actually posting says "Head of Enterprise Sales Team: Revenue". But the role is Director of Sales? The title maybe "Head of Enterprise Sales Team". We'll not use as heading. We need to output only HTML fragment. Let's extract content. Company description: "Who We Are Lightning AI is the company behind PyTorch Lightning. Founded in 2019, we build an end-to-end platform for developing, training, and deploying AI systems—designed to take ideas from research to production with less friction. Through our merger with Voltage Park, a neocloud and AI Factory, Lightning AI combines developer-first software with cost-efficient, large-scale compute. Teams get the tools they need for experimentation, training, and production inference, with security, observability, and control built in. We serve solo researchers, startups, and large enterprises. Lightning AI operates globally with offices in New York City, San Francisco, Seattle, and London, and is backed by Coatue, Index Ventures, Bain Capital Ventures, and Firstminute." Values: "The Way We Work The People Who Thrive Here Are Builders Who Move Fast, Communicate Openly, Take Ownership, And Continuously Improve Themselves, Their Teams, And Our Company. Here's What That Looks Like In Practice Move with Urgency: We move quickly, make thoughtful decisions, and keep momentum. We value action over perfection and learn by shipping.Take Ownership: We own outcomes, not just our individual work. We make decisions that move the company forward and follow through.Communicate Openly: We communicate directly, seek to understand, and create clarity for others. Honest conversations help us move faster together.Build Great Teams: We lead by example, empower others, and create healthy teams where people can do their best work.Raise the Bar: We're always improving ourselves. We learn from feedback, consistently challenge ourselves to grow, and focus on the work that matters most.Think Long-Term: We design for what's next. We create scalable systems, simplify complexity, and use AI and automation to amplify our impact." We could include this as part of About the role or separate section "About the company". But headings list doesn't include About the company. However we could still include a heading like "About the company" but not in list; maybe okay. But instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. So we can incorporate company description and values into About the role section (maybe as preamble). Or we could have a section "About the company" but not in list; risk of being considered extra heading. I'd rather include under About the role.
Thus About the role heading About the role
then paragraphs containing company description, values, and role overview.
Role overview: "About Lightning AI Lightning AI is building the platform and infrastructure that make it dramatically easier for teams to develop, train, deploy, and scale AI systems. As the company behind PyTorch Lightning, and following our merger with Voltage Park, we bring together developer-first AI tooling with high-performance compute infrastructure for researchers, startups, and enterprises building at the frontier of AI. We operate with a simple set of values: Move Fast, Focus, Balance, Craftsmanship, and Minimal. We care about people who can operate with urgency, solve hard problems directly, and build with high standards without creating unnecessary complexity." That's similar to earlier but okay.
Then "About The Role We are looking for a Director of Sales to lead a high-performing enterprise sales team and help scale Lightning AI’s revenue engine across technical, strategic, and high-value accounts. This is a hands-on leadership role for someone who can coach complex enterprise selling, build durable operating rhythms, and help the team win with technical buyers across AI, infrastructure, engineering, research, and data organizations."
We'll combine.
Responsibilities: list from "What You'll Do". Items:
- Lead, coach, and scale a team of enterprise Account Executives focused on strategic and high-growth customers.
- Own team pipeline generation, forecast accuracy, deal inspection, and quota attainment.
- Build a rigorous sales operating cadence around territory planning, account strategy, pipeline creation, MEDDIC/MEDDPICC discipline, and executive alignment.
- Coach sellers through complex technical sales cycles involving ML leaders, infrastructure leaders, engineering executives, procurement, finance, and C-level stakeholders.
- Partner closely with ML Solutions Engineering, Customer Success, Partnerships, Marketing, Product, and Revenue Operations to create a repeatable enterprise GTM motion.
- Help define Lightning AI’s sales playbook for AI infrastructure, model development, training, deployment, and compute-intensive enterprise workloads.
- Identify blockers in the sales motion and build practical systems, content, inspection points, and feedback loops to remove them.
- Represent the voice of the customer internally and help shape product, packaging, pricing, and market positioning.
- Recruit and develop exceptional sales talent while building a culture of high accountability, curiosity, urgency, and craftsmanship.
Requirements: "What We're Looking For":
- 8+ years of enterprise technology sales experience, including 3+ years managing quota-carrying sellers.
- A track record of leading teams that consistently exceed target in complex, technical sales environments.
- Experience selling to technical buyers such as ML leaders, infrastructure leaders, CTOs, engineering executives, platform teams, or data organizations.
- Strong command of enterprise sales methodology, forecasting, deal inspection, pipeline generation, and multi-threaded account strategy.
- Ability to coach sellers on both strategic account planning and the practical details of running a deal well.
- Comfort operating in a fast-moving startup environment where the playbook is still being built.
- Clear communication, high judgment, and the ability to build trust quickly with executive customers and internal leaders.
Nice-to-Haves:
- Experience selling AI, cloud infrastructure, developer platforms, data platforms, MLOps, GPUs, or high-performance compute.
- Prior experience building a sales team or segment through a period of rapid growth.
- Deep familiarity with MEDDIC/MEDDPICC, command-of-the-message style positioning, or similar enterprise sales frameworks.
- Experience partnering closely with technical pre-sales or field engineering teams.
Why Lightning AI: maybe not needed as separate section; could be omitted or included under About the role. But we could include as a short paragraph under About the role? The instruction says prefer few substantive sections. Could omit Why Lightning AI as it's motivational but still substantive. Could include as a paragraph under About the role.
Benefits: list from Benefits And Perks:
- Comprehensive Health Coverage: Medical, dental, and vision coverage for employees and eligible dependents.
- Meaningful Equity: RSUs that give employees a stake in the company's long-term success.
- Retirement Savings: 401(k) matching (U.S.) and pension contributions (U.K.).
- Flexible Time Off: Unlimited PTO, company holidays, and floating holidays to support work-life balance.
- Company-Wide Winter Break: Two weeks of company closure each winter to disconnect and recharge.
- Paid Parental & Family Leave: Paid leave to support you and your family through life's important moments.
- Professional Development: Annual learning and development allowance to support your professional growth.
- Wellness Benefits: Wellness and work-from-home stipends to support your physical and mental well-being.
- Sabbatical Program: Four weeks of paid sabbatical leave after four years of service.
- Flexible Work: Flexible schedules and a hybrid work model for our office-based teams.
- In-Office Meals: Complimentary meals at our office hubs.
- Benefits may vary by location, team, and role.
We should keep the bullet points as - .
Pay: "The anticipated annual base salary range for this role is: $225,000 - $260,000 USD" plus "In addition to base salary, our total rewards package for eligible roles includes a discretionary bonus, a meaningful equity component, and comprehensive benefits." Also "Final offers are based on factors such as experience, skills, geographic location, and role expectations."
We'll put in a
.
Schedule: hybrid info: "Location: [NYC] - Hybrid" and "Flexible Work: Flexible schedules and a hybrid work model for our office-based teams." Also "Flexible Time Off" etc but that's benefits. So schedule: hybrid work model.
We'll output as
Schedule
Hybrid work model based in New York City with flexible schedules.
Now ensure we don
. Schedule: hybrid info: "Location: [NYC] - Hybrid" and "Flexible Work: Flexible schedules and a hybrid work model for our office-based teams." Also "Flexible Time Off" etc but that's benefits. So schedule: hybrid work model. We'll output as
Schedule
Hybrid work model based in New York City with flexible schedules.
Now ensure we don