Account Executive, Majors - New England

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. No job title heading. No Job ID. Remove boilerplate, EEO, etc. Keep substantive info. Let's parse the posting. First paragraph: description of Zscaler (company overview). Could be "About the role"? Actually it's about company. Might be "About the role" or "About Zscaler". The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for company overview and role description. Then: "The Zscaler Sales and Go-to-Market team is a global group..." That's also about role/team. Then: "We're Looking For An Account Executive, Majors Based In Massachusetts Metro To Join Our East Team. Reporting To The Regional Director, You Will Build relationships with important internal and customer stakeholders, including c-suite decision-makersCreate a long-term account strategy aligned with customer goalsCollaborate with our teams to meet customer needs and contribute to account planningBe a trusted advisor, understanding client businesses and aligning Zscaler solutions with their goals" Note there is missing punctuation; but we can treat as responsibilities list. Then "What We're Looking For (Minimum Qualifications)" then bullet list: "Demonstrated curiosity and active exploration of AI tools, with a proven history of integrating new technologies to enhance daily workflows and augment problem-solving" then "10+ years of full-cycle sales experience within software or security industry", "Bachelor's degree or equivalent experience", "Progressive selling experience engaging with accounts and selling at C-Level", then repeated "Demonstrate curiosity and active exploration of AI tools, with a proven history of integrating new technologies to enhance daily workflows and augment problem-solving". Duplicate. Then "What Will Make You Stand Out (Preferred Qualifications)" bullet list: "You have established relationships with current and prospective customers and understand the bigger picture, customer goals and how technology can facilitate them", "Proficiency in strategic sales planning with experience closing net new logos", "Experience meeting or achieving sales targets, using channel partnerships" Then "Zscaler’s salary ranges are benchmarked..." then "Base Pay Range $145,250—$207,500 USD". That's Pay. Then "Benefits Our Benefits program is one of the most important ways we support our employees. Zscaler proudly offers comprehensive and inclusive benefits..." then list: Various health plans, Time off plans for vacation and sick time, Parental leave options, Retirement options, Education reimbursement, In-office perks, and more! Then there is EEO etc which we remove. Also there is "Pay Transparency" etc maybe not needed. Schedule not mentioned, so omit. Skills? Could be derived from qualifications but we can put under Requirements or Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Requirements and Qualifications maybe. But we need to avoid thin sections. Let's decide sections: - About the role (company overview + team description) - Responsibilities (the bullet list of duties) - Requirements (minimum qualifications) - Preferred Qualifications (maybe as "Preferred Qualifications" but not in list; we could put under Qualifications or Skills. Since they said "Qualifications" heading can be used. We could have "Qualifications" covering both minimum and preferred? But better to separate: "Requirements" for minimum, "Preferred Qualifications" maybe as "Skills"? Not exactly. Could use "Skills" for preferred qualifications. But we need to follow instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (minimum), Qualifications (maybe preferred?), Skills (maybe other). However we have both minimum and preferred; we could put minimum under Requirements, preferred under Qualifications. Or we could put both under Requirements and Qualifications combined but that may be thin. Let's do:

About the role

(company overview + team)

Responsibilities

(list of duties)

Requirements

(minimum qualifications)

Qualifications

(preferred qualifications)

Benefits

(list)

Pay

(salary range) No Schedule. We must not repeat job title as heading. Good. We must preserve all substantive information; not invent or summarize away detail. So we need to include all bullet points exactly as given (maybe rephrase slightly but preserve meaning). We'll output

• for each. We need to remove duplicated lines: The "Demonstrated curiosity..." appears twice in minimum qualifications; we should include only once. Also need to remove boilerplate like EEO, etc. Let's extract content. About the role: combine first paragraphs: "Zscaler (NASDAQ: ZS) accelerates digital transformation so customers can be more agile, efficient, resilient, and secure. The Zscaler Zero Trust Exchange™️ platform protects thousands of customers from cyberattacks and data loss by securely connecting users, devices, and applications in any location. Distributed across 160+ public exchanges globally and thousands of private exchanges at the edge, the SASE-based Zero Trust Exchange is the world’s largest in-line cloud security platform. We believe the future of work is Human + AI and are building an AI-native enterprise where human potential is amplified by machine intelligence to solve the world’s hardest security challenges. Driven by deep customer obsession, we are committed to the mission, outcome, and to each other. We bring these commitments to life through three core behaviors: ownership and collaboration, trust through outcomes and impact, and a challenge culture with ongoing feedback. Ready to make an impact at the company pioneering security transformation in the AI era? Join us at Zscaler. The Zscaler Sales and Go-to-Market team is a global group of professionals who are passionate about delighting our customers, nurturing trusted partnerships, and sharing their expertise to lead a secure, cloud-enabled digital future and further cement our position as the world leader in cloud security. Sales, Customer Success, Sales Enablement, Solution Architects, Business Development, Transformation, and Technology Partnerships all work together to demonstrate the power and agility of Zscaler cloud transformation to the world." That's substantive. Responsibilities: from "We're Looking For An Account Executive, Majors Based In Massachusetts Metro To Join Our East Team. Reporting To The Regional Director, You Will Build relationships with important internal and customer stakeholders, including c-suite decision-makersCreate a long-term account strategy aligned with customer goalsCollaborate with our teams to meet customer needs and contribute to account planningBe a trusted advisor, understanding client businesses and aligning Zscaler solutions with their goals" We need to split into list items. The text seems missing punctuation; we can interpret as: - Build relationships with important internal and customer stakeholders, including C-suite decision-makers - Create a long-term account strategy aligned with customer goals - Collaborate with our teams to meet customer needs and contribute to account planning - Be a trusted advisor, understanding client businesses and aligning Zscaler solutions with their goals Also maybe include "We're Looking For An Account Executive, Majors Based In Massachusetts Metro To Join Our East Team. Reporting To The Regional Director," as part of role description but not a responsibility. Could be included in About the role? But we already have About the role; we could include location and reporting line in Responsibilities or About the role. Since it's part of the role description, we could add a bullet: "Reporting to the Regional Director, based in Massachusetts Metro." But the instruction: preserve ALL substantive information; do not invent or summarize away detail. So we should include that sentence somewhere. Could be a paragraph under About the role or Responsibilities. Since it's about the role, maybe include in About the role after team description. But we already used About the role for company overview; we could add a paragraph: "We're Looking For An Account Executive, Majors Based In Massachusetts Metro To Join Our East Team. Reporting To The Regional Director," as a paragraph. However that is not a responsibility; it's role description. Could be part of About the role. Let's add a short paragraph after the team description: "We're looking for an Account Executive based in the Massachusetts Metro area to join our East team, reporting to the Regional Director." That preserves info. Now Responsibilities list as above. Requirements (minimum qualifications): list: - Demonstrated curiosity and active exploration of AI tools, with a proven history of integrating new technologies to enhance daily workflows and augment problem-solving - 10+ years of full-cycle sales experience within software or security industry - Bachelor's degree or equivalent experience - Progressive selling experience engaging with accounts and selling at C-Level We should not repeat the curiosity line. Qualifications (preferred): - You have established relationships with current and prospective customers and understand the bigger picture, customer goals and how technology can facilitate them - Proficiency in strategic sales planning with experience closing net new logos - Experience meeting or achieving sales targets, using channel partnerships Benefits: list: - Various health plans - Time off plans for vacation and sick time - Parental leave options - Retirement options - Education reimbursement - In-office perks, and more! We could keep "and more!" as part of last item. Pay: just a paragraph: "Base Pay Range $145,250—$207,500 USD" We should not include the explanatory text about salary ranges being benchmarked etc? That is substantive but maybe considered boilerplate? It's about pay range explanation. 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 salary range explanation is not boilerplate; it's substantive about how range determined. Should we keep it? It says "Zscaler’s salary ranges are benchmarked and are determined by role and level. The range displayed on each job posting reflects the minimum and maximum target for new hire salaries for the position across all US locations and could be higher or lower based on a multitude of factors, including job-related skills, experience, and relevant education or training. The base salary range listed for this full-time position excludes commission/ bonus/ equity (if applicable) + benefits." That is substantive. We should keep it. However we need to avoid too much fluff? But it's substantive. We'll include as a paragraph under Pay. Now ensure we don't include any EEO etc. Now output HTML fragment. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  ...

  Make sure no extra whitespace? It's fine. Now craft the paragraphs. About the role paragraph: combine company overview and team description plus location line. Let's write:

  Zscaler (NASDAQ: ZS) accelerates digital transformation so customers can be more agile, efficient, resilient, and secure. The Zscaler Zero Trust Exchange™️ platform protects thousands of customers from cyberattacks and data loss by securely connecting users, devices, and applications in any location. Distributed across 160+ public exchanges globally and thousands of private exchanges at the edge, the SASE-based Zero Trust Exchange is the world’s largest in-line cloud security platform. We believe the future of work is Human + AI and are building an AI-native enterprise where human potential is amplified by machine intelligence to solve the world