Enterprise Account Executive
for headings. Use - for lists. Use
for prose. Remove boilerplate. Include only sections with real specific content.
Let's parse the posting:
- Intro: "The Enterprise Account Executive will be responsible for driving sales efforts in North America (East). As our Enterprise Account Executive for the region, you will drive new customer acquisitions and will be hunting new logos by developing key growth sales strategies, tactics and action plans. This is an individual contributor role and will be responsible for hitting the sales quota and overachieving it. An ideal candidate will be someone who has experience in selling SAAS B2B enterprise product to large enterprises. We are looking for high achievers and hunters who made it to the president club / president's club multiple times."
That's about the role.
- Then "The responsibilities will involve the following:" then list:
Identify and close sales opportunities with Fortune 500 companies
Manage complex sales cycle selling the Source to Pay Suite to the CPOs, CFOs and CIOs.
Manage large enterprise accounts of 1 billion and above in revenue
Growing revenue via prospecting, qualifying, selling and closing enterprise client accounts
Forecast sales closures accurately based upon realistic opportunity assessments
Work with Inside sales and marketing to maximize territory penetration
Providing a consultative solutions sales process to prospects
Build key customer relationships with Zycus customers
These are responsibilities.
- Then "External Skills And Expertise" heading then list:
7-12 years years experience in a sales hunter role with a successful track record in large complex sales
A proven track record and demonstrated success in leading teams selling SaaS / Cloud enterprise software to large enterprises and global companies
Must be willing to travel to meet customers
Experience in selling eProcurement software solutions will be an added advantage
Must have been a part of President's Club/ Winner's Circle/ Achiever's Club/ Platinum Club/ Others
These are requirements/skills.
- Then "Why Join Zycus?" paragraph with multiple bullet-like sentences but not bullet list. It includes:
At Zycus, you won't just sell software — you'll help reshape how the world's largest companies run procurement. Work with a proven leader. Recognized by Gartner and Forrester as a Leader in Source-to-Pay, including the 2026 Gartner® Magic Quadrant™ — two decades of trust behind every pitch you make.
Sell the future, not the past. We're the pioneer of Agentic AI in procurement. Our Merlin Agentic AI Platform gives you a genuinely differentiated story that opens doors and shortens cycles.
Big logos, big deals. Engage Fortune 1000 and Global 2000 enterprises — Delta, Heineken, and more — and close deals with measurable, reference-able impact.
Be rewarded for winning. Competitive base, uncapped upside, and performance incentives — because top closers deserve top rewards. Great reps want great products, big logos, and real upside. That's Zycus. Come do the best sales work of your career.
This is benefits/why join. It includes competitive base, uncapped upside, performance incentives (pay). Also mentions benefits like working with proven leader, recognition, AI platform, big logos, etc. No explicit schedule.
Thus we can have sections:
About the role
with paragraph(s) summarizing the intro.
Responsibilities
with - list.
Requirements
maybe combine skills and expertise. Could also have Skills
but we can combine.
We need to decide: The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content.
We have content for About the role, Responsibilities, Requirements (skills/experience), Benefits (why join). Pay is mentioned inside benefits (competitive base, uncapped upside, performance incentives). Should we create a separate Pay section? The rule: "Prefer a few substantive sections over many thin ones." So we could include Pay within Benefits, or create a Pay section if we have specific pay details. The posting mentions "Competitive base, uncapped upside, and performance incentives". That's pay info. Could create a Pay section with that detail. But we also have other benefits like working with proven leader, recognition, AI platform, big logos. Might be better to have Benefits section covering those, and Pay separate if we want to follow the heading list. However the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we create Pay section, we need to have specific content. We have "Competitive base, uncapped upside, and performance incentives". That's specific enough. So we could have a Pay section.
Similarly Schedule: no info, so omit.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
But we also have Skills maybe separate from Requirements. However the posting lumps skills and expertise under "External Skills And Expertise". That could be Requirements or Skills. We could make a Skills section. But we also have requirements like years experience, willingness to travel, President's Club. Those are requirements. Could combine into Requirements. The instruction says prefer few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section called Requirements (or Skills). But we have headings list includes both; we can choose one.
I'll create:
About the role
... (intro)
Responsibilities
- ... list items
Requirements
- ... list items from External Skills And Expertise
Benefits
... (Why Join Zycus? content excluding pay specifics? but we could include all why join content, then Pay separate). However the why join includes pay info; we could split: Benefits section includes everything except pay details; Pay section includes pay details. But we need to preserve all substantive information; we can duplicate? Better to keep all why join content in Benefits, and then Pay separate with just pay details. But that would split the why join paragraph; we could keep the why join paragraph in Benefits and then Pay separate with the pay sentence extracted. However the why join paragraph includes the pay sentence; if we extract it, we might lose context. But we can keep the whole why join paragraph in Benefits and also have Pay section with the same sentence? That would duplicate. Better to keep the why join paragraph in Benefits and not have a separate Pay section, because pay is part of benefits. The instruction says we can have Pay section if posting actually states them. It does state pay, but we can also include it under Benefits. Since we prefer few sections, we can omit Pay and include pay details in Benefits.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
Now we need to format.
Let's extract About the role paragraph:
"The Enterprise Account Executive will be responsible for driving sales efforts in North America (East). As our Enterprise Account Executive for the region, you will drive new customer acquisitions and will be hunting new logos by developing key growth sales strategies, tactics and action plans. This is an individual contributor role and will be responsible for hitting the sales quota and overachieving it. An ideal candidate will be someone who has experience in selling SAAS B2B enterprise product to large enterprises. We are looking for high achievers and hunters who made it to the president club / president's club multiple times."
We can keep as one
.
Responsibilities list items:
- Identify and close sales opportunities with Fortune 500 companies
- Manage complex sales cycle selling the Source to Pay Suite to the CPOs, CFOs and CIOs.
- Manage large enterprise accounts of 1 billion and above in revenue
- Growing revenue via prospecting, qualifying, selling and closing enterprise client accounts
- Forecast sales closures accurately based upon realistic opportunity assessments
- Work with Inside sales and marketing to maximize territory penetration
- Providing a consultative solutions sales process to prospects
- Build key customer relationships with Zycus customers
Note: some start with verb forms; keep as is.
Requirements list items from External Skills And Expertise:
- 7-12 years years experience in a sales hunter role with a successful track record in large complex sales
- A proven track record and demonstrated success in leading teams selling SaaS / Cloud enterprise software to large enterprises and global companies
- Must be willing to travel to meet customers
- Experience in selling eProcurement software solutions will be an added advantage
- Must have been a part of President's Club/ Winner's Circle/ Achiever's Club/ Platinum Club/ Others
Note: there is a typo "years years". We must preserve as is.
Benefits paragraph: The "Why Join Zycus?" content.
Let's copy exactly:
"At Zycus, you won't just sell software — you'll help reshape how the world's largest companies run procurement. Work with a proven leader. Recognized by Gartner and Forrester as a Leader in Source-to-Pay, including the 2026 Gartner® Magic Quadrant™ — two decades of trust behind every pitch you make.
Sell the future, not the past. We're the pioneer of Agentic AI in procurement. Our Merlin Agentic AI Platform gives you a genuinely differentiated story that opens doors and shortens cycles.
Big logos, big deals. Engage Fortune 1000 and Global 2000 enterprises — Delta, Heineken, and more — and close deals with measurable, reference-able impact.
Be rewarded for winning. Competitive base, uncapped upside, and performance incentives — because top closers deserve top rewards. Great reps want great products, big logos, and real upside. That's Zycus. Come do the best sales work of your career."
We need to preserve line breaks? We can keep as a single
with sentences; line breaks not needed.
Now output HTML fragment.
Make sure no extra markdown fences.
Thus:
About the role
The Enterprise Account Executive will be responsible for driving sales efforts in North America (East). As our Enterprise Account Executive for the region, you will drive new customer acquisitions and will be hunting new logos by developing key growth sales strategies, tactics and action plans. This is an individual contributor role and will be responsible for hitting the sales quota and overachieving it. An ideal candidate will be someone who has experience in selling SAAS B2B enterprise product to large enterprises. We are looking for high achievers and hunters who made it to the president club / president's club multiple times.
Responsibilities
- Identify and close sales opportunities with Fortune 500 companies
- Manage complex sales cycle selling the Source to Pay Suite to the CPOs, CFOs and CIOs.
- Manage large enterprise accounts of 1 billion and above in revenue
- Growing revenue via prospecting, qualifying, selling and closing enterprise client accounts
- Forecast sales closures accurately based upon realistic opportunity assessments
- Work with Inside sales and marketing to maximize territory penetration
- Providing a consultative solutions sales process to prospects
- Build key customer relationships with Zycus customers
Requirements
- 7-12 years years experience in a sales hunter role with a successful track record in large complex sales
- A proven track record and demonstrated success in leading teams selling SaaS / Cloud enterprise software to large enterprises and global companies
- Must be willing to travel to meet customers
- Experience in selling eProcurement software solutions will be
for prose. Remove boilerplate. Include only sections with real specific content. Let's parse the posting: - Intro: "The Enterprise Account Executive will be responsible for driving sales efforts in North America (East). As our Enterprise Account Executive for the region, you will drive new customer acquisitions and will be hunting new logos by developing key growth sales strategies, tactics and action plans. This is an individual contributor role and will be responsible for hitting the sales quota and overachieving it. An ideal candidate will be someone who has experience in selling SAAS B2B enterprise product to large enterprises. We are looking for high achievers and hunters who made it to the president club / president's club multiple times." That's about the role. - Then "The responsibilities will involve the following:" then list: Identify and close sales opportunities with Fortune 500 companies Manage complex sales cycle selling the Source to Pay Suite to the CPOs, CFOs and CIOs. Manage large enterprise accounts of 1 billion and above in revenue Growing revenue via prospecting, qualifying, selling and closing enterprise client accounts Forecast sales closures accurately based upon realistic opportunity assessments Work with Inside sales and marketing to maximize territory penetration Providing a consultative solutions sales process to prospects Build key customer relationships with Zycus customers These are responsibilities. - Then "External Skills And Expertise" heading then list: 7-12 years years experience in a sales hunter role with a successful track record in large complex sales A proven track record and demonstrated success in leading teams selling SaaS / Cloud enterprise software to large enterprises and global companies Must be willing to travel to meet customers Experience in selling eProcurement software solutions will be an added advantage Must have been a part of President's Club/ Winner's Circle/ Achiever's Club/ Platinum Club/ Others These are requirements/skills. - Then "Why Join Zycus?" paragraph with multiple bullet-like sentences but not bullet list. It includes: At Zycus, you won't just sell software — you'll help reshape how the world's largest companies run procurement. Work with a proven leader. Recognized by Gartner and Forrester as a Leader in Source-to-Pay, including the 2026 Gartner® Magic Quadrant™ — two decades of trust behind every pitch you make. Sell the future, not the past. We're the pioneer of Agentic AI in procurement. Our Merlin Agentic AI Platform gives you a genuinely differentiated story that opens doors and shortens cycles. Big logos, big deals. Engage Fortune 1000 and Global 2000 enterprises — Delta, Heineken, and more — and close deals with measurable, reference-able impact. Be rewarded for winning. Competitive base, uncapped upside, and performance incentives — because top closers deserve top rewards. Great reps want great products, big logos, and real upside. That's Zycus. Come do the best sales work of your career. This is benefits/why join. It includes competitive base, uncapped upside, performance incentives (pay). Also mentions benefits like working with proven leader, recognition, AI platform, big logos, etc. No explicit schedule. Thus we can have sections:
About the role
with paragraph(s) summarizing the intro.Responsibilities
with- list.
Requirements
maybe combine skills and expertise. Could also haveSkills
but we can combine. We need to decide: The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We have content for About the role, Responsibilities, Requirements (skills/experience), Benefits (why join). Pay is mentioned inside benefits (competitive base, uncapped upside, performance incentives). Should we create a separate Pay section? The rule: "Prefer a few substantive sections over many thin ones." So we could include Pay within Benefits, or create a Pay section if we have specific pay details. The posting mentions "Competitive base, uncapped upside, and performance incentives". That's pay info. Could create a Pay section with that detail. But we also have other benefits like working with proven leader, recognition, AI platform, big logos. Might be better to have Benefits section covering those, and Pay separate if we want to follow the heading list. However the instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we create Pay section, we need to have specific content. We have "Competitive base, uncapped upside, and performance incentives". That's specific enough. So we could have a Pay section. Similarly Schedule: no info, so omit. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. But we also have Skills maybe separate from Requirements. However the posting lumps skills and expertise under "External Skills And Expertise". That could be Requirements or Skills. We could make a Skills section. But we also have requirements like years experience, willingness to travel, President's Club. Those are requirements. Could combine into Requirements. The instruction says prefer few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section called Requirements (or Skills). But we have headings list includes both; we can choose one. I'll create:About the role
... (intro)
Responsibilities
- ... list items
Requirements
- ... list items from External Skills And Expertise
Benefits
... (Why Join Zycus? content excluding pay specifics? but we could include all why join content, then Pay separate). However the why join includes pay info; we could split: Benefits section includes everything except pay details; Pay section includes pay details. But we need to preserve all substantive information; we can duplicate? Better to keep all why join content in Benefits, and then Pay separate with just pay details. But that would split the why join paragraph; we could keep the why join paragraph in Benefits and then Pay separate with the pay sentence extracted. However the why join paragraph includes the pay sentence; if we extract it, we might lose context. But we can keep the whole why join paragraph in Benefits and also have Pay section with the same sentence? That would duplicate. Better to keep the why join paragraph in Benefits and not have a separate Pay section, because pay is part of benefits. The instruction says we can have Pay section if posting actually states them. It does state pay, but we can also include it under Benefits. Since we prefer few sections, we can omit Pay and include pay details in Benefits. Thus sections: About the role, Responsibilities, Requirements, Benefits. Now we need to format. Let's extract About the role paragraph: "The Enterprise Account Executive will be responsible for driving sales efforts in North America (East). As our Enterprise Account Executive for the region, you will drive new customer acquisitions and will be hunting new logos by developing key growth sales strategies, tactics and action plans. This is an individual contributor role and will be responsible for hitting the sales quota and overachieving it. An ideal candidate will be someone who has experience in selling SAAS B2B enterprise product to large enterprises. We are looking for high achievers and hunters who made it to the president club / president's club multiple times." We can keep as one
. Responsibilities list items: - Identify and close sales opportunities with Fortune 500 companies - Manage complex sales cycle selling the Source to Pay Suite to the CPOs, CFOs and CIOs. - Manage large enterprise accounts of 1 billion and above in revenue - Growing revenue via prospecting, qualifying, selling and closing enterprise client accounts - Forecast sales closures accurately based upon realistic opportunity assessments - Work with Inside sales and marketing to maximize territory penetration - Providing a consultative solutions sales process to prospects - Build key customer relationships with Zycus customers Note: some start with verb forms; keep as is. Requirements list items from External Skills And Expertise: - 7-12 years years experience in a sales hunter role with a successful track record in large complex sales - A proven track record and demonstrated success in leading teams selling SaaS / Cloud enterprise software to large enterprises and global companies - Must be willing to travel to meet customers - Experience in selling eProcurement software solutions will be an added advantage - Must have been a part of President's Club/ Winner's Circle/ Achiever's Club/ Platinum Club/ Others Note: there is a typo "years years". We must preserve as is. Benefits paragraph: The "Why Join Zycus?" content. Let's copy exactly: "At Zycus, you won't just sell software — you'll help reshape how the world's largest companies run procurement. Work with a proven leader. Recognized by Gartner and Forrester as a Leader in Source-to-Pay, including the 2026 Gartner® Magic Quadrant™ — two decades of trust behind every pitch you make. Sell the future, not the past. We're the pioneer of Agentic AI in procurement. Our Merlin Agentic AI Platform gives you a genuinely differentiated story that opens doors and shortens cycles. Big logos, big deals. Engage Fortune 1000 and Global 2000 enterprises — Delta, Heineken, and more — and close deals with measurable, reference-able impact. Be rewarded for winning. Competitive base, uncapped upside, and performance incentives — because top closers deserve top rewards. Great reps want great products, big logos, and real upside. That's Zycus. Come do the best sales work of your career." We need to preserve line breaks? We can keep as a single
with sentences; line breaks not needed. Now output HTML fragment. Make sure no extra markdown fences. Thus:
About the role
The Enterprise Account Executive will be responsible for driving sales efforts in North America (East). As our Enterprise Account Executive for the region, you will drive new customer acquisitions and will be hunting new logos by developing key growth sales strategies, tactics and action plans. This is an individual contributor role and will be responsible for hitting the sales quota and overachieving it. An ideal candidate will be someone who has experience in selling SAAS B2B enterprise product to large enterprises. We are looking for high achievers and hunters who made it to the president club / president's club multiple times.
Responsibilities
- Identify and close sales opportunities with Fortune 500 companies
- Manage complex sales cycle selling the Source to Pay Suite to the CPOs, CFOs and CIOs.
- Manage large enterprise accounts of 1 billion and above in revenue
- Growing revenue via prospecting, qualifying, selling and closing enterprise client accounts
- Forecast sales closures accurately based upon realistic opportunity assessments
- Work with Inside sales and marketing to maximize territory penetration
- Providing a consultative solutions sales process to prospects
- Build key customer relationships with Zycus customers
Requirements
- 7-12 years years experience in a sales hunter role with a successful track record in large complex sales
- A proven track record and demonstrated success in leading teams selling SaaS / Cloud enterprise software to large enterprises and global companies
- Must be willing to travel to meet customers
- Experience in selling eProcurement software solutions will be