Account Executive

We need to produce HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Given content: Location: Salt Lake City, United States of America Function: (DEAI HV) AMER Sales Requisition ID: R0145521 Our Company (repeated twice) description. The Team description. The Role description: includes bullet-like paragraphs with percentages. What You’ll Bring: includes bullet points with percentages. Qualifications: list. About Us (repeated twice) description. Fostering innovation through diverse perspectives. How We Look After You: description of benefits, flexible arrangements, etc. We need to extract substantive info. We must not repeat job title as heading (the page already shows it). We don't have job title given explicitly, but we can ignore. We must not put Job ID/requisition numbers as headings; fold minor metadata into short

or drop it. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to preserve all substantive information; do not invent or summarize away detail. We need to include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. We need to prefer a few substantive sections over many thin ones. We need to output only HTML fragment, no /, no markdown fences. Thus we need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content about role (The Role, What You’ll Bring). Could map to "About the role" and "Responsibilities". Qualifications section: we have Qualifications. Skills: maybe we can combine with Qualifications? But we need to follow headings list; we can include Skills if we have skill-specific content. There's mention of "Subject matter expertise in data storage, data management, data analytics and other IT services." "Domain knowledge of large enterprise IT environments and corporate buying centres are critical." "Must demonstrate a consistent track record of achieving annual quota targets while providing specific details on key customer wins." "The ideal candidate will bring an established sales management process, experience building and maintaining relationships with management and C level executives." "A successful track record of managing and closing complex sales campaigns, using outcome and solution selling techniques is a must." "Possesses a competitive attitude, strong work ethic and thrives in a fast pace, high growth and matrixed organizational environment." "Must be a proficient user of Salesforce and other MS Office tools." "Having a BA/BS degree or equivalent is desirable." These could go under Qualifications or Skills. Since we have Qualifications heading already, we can put qualifications there. Skills maybe we can omit if not distinct. Benefits: we have "How We Look After You" describing benefits: industry-leading benefits, support, services, flexible arrangements, work-life balance, etc. That's substantive. So we can include Benefits section. Pay: not mentioned; no salary info. So we should NOT include Pay section. Schedule: not mentioned; no schedule info. So we should NOT include Schedule. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Possibly also "About the company" or "Team"? But headings list limited to those; we could include "About the role" and "Responsibilities". Could also include "Qualifications". Could also include "Benefits". Could also include "Skills" if we want to separate skill-specific content, but we can keep Qualifications. We need to avoid duplication: The posting repeats "Our Company" and "About Us". We should include that content maybe under "About the role"? Actually "About the role" is for role description; "About the company" is not in headings list. Could we put company description under "About the role"? Not appropriate. But we could include a short paragraph about company under maybe a generic

before sections? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." It doesn't forbid other headings not in list? It says: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections; but we could also have other headings? Probably better to stick to those. However, we need to preserve all substantive information; if we omit company description, we lose info. But maybe we can incorporate company description into "About the role" or "Qualifications"? Not ideal. We could create a section "About the company" but not in the list; but instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive. But they also say "Prefer a few substantive sections over many thin ones." So we could add a section like "About the company" if needed. However, they might expect only those headings. Safer to include company description under a generic

before sections, not as a heading. That's allowed: we can have prose

for any content not under headings. The instruction: "Use

• for any list of duties/requirements/benefits, and

  for prose." So we can have

  for company overview, team description, etc. Thus we can output:

  Location: Salt Lake City, United States of America

  maybe minor metadata. But they said fold minor metadata into a short

  or drop it. Location and function and requisition ID are minor metadata; we can put them in a short

  . Then we can have sections:

  About the role

  with prose describing the role: The Role section plus What You’ll Bring? Actually "About the role" could include description of role and what you'll bring. But we also have Responsibilities: we can split. Better: About the role: brief description of role and team. Responsibilities: list of duties with percentages. Qualifications: list of qualifications. Benefits: description of benefits. We need to use
  • for any list of duties/requirements/benefits. Thus for Responsibilities we can make a
    with each bullet as a line (including percentages). For Qualifications we can make a
    with each qualification line. For Benefits we can make a
    with benefit items. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details. First, minor metadata: Location: Salt Lake City, United States of America; Function: (DEAI HV) AMER Sales; Requisition ID: R0145521. We'll put in a

    . Now company description: "Our Company We're Hitachi Vantara, the data foundation trusted by the world's innovators. Our resilient, high-performance data infrastructure means that customers - from banks to theme parks - can focus on achieving the incredible with data. If you've seen the Las Vegas Sphere, you've seen just one example of how we empower businesses to automate, optimize, innovate - and wow their customers. Right now, we're laying the foundation for our next wave of growth. We're looking for people who love being part of a diverse, global team - and who get excited about making a real-world impact with data." That's repeated twice; we need to preserve but not duplicate. We'll include once. Team description: "The Team Hitachi Vantara combines technology, intellectual property, and industry knowledge to deliver data-managing solutions that help enterprises improve their customers’ experiences, develop new revenue streams, and lower the costs of business. Hitachi Vantara elevates your innovation advantage by combining IT, operational technology (OT) and domain expertise. Join our team and our employee-focused culture and help drive our customers’ data to meaningful customer outcomes." We can include that as prose. Now About the role: "The Role We are seeking energetic and motivated sales professionals with strong hunting skills to join our Account Executive team. The ideal candidate will have a minimum of 5 years of new account or business development experience with a proven track record of selling complex technical solutions. In your role, you will leverage market intelligence resources, customer events, product specialist, partners and your own professional network to develop new relationships and close business with high value pursuit clients." What You’ll Bring: bullet points with percentages: - Planning – conduct market and customer research to expand commercial insight necessary to build effective customer call plans and sales strategies (10%) - Prospecting and lead management – drive a high volume of high value prospecting and business development activities, to include lead management, needed to reach key decision makers/influencers (technical and business) inside pursuit accounts (30%) - Selling - drive account strategies and coordinate team selling efforts with partners, specialist, management and technical resources necessary to close business. (50%) - Training – Through a rigorous and subject rich training agenda, you will become sale proficient with Hitachi Vantara’s solutions while becoming conversational ready on how Hitachi Vantara delivers business value to its customers and prospects. (5%) - Reporting - Managing forecast and updating activity plans inside Salesforce (5%) We could incorporate these under Responsibilities as a list. Qualifications: list: - Sales experience in infrastructure, data storage, data management or other IT services - A minimum of 5 years of outside sales experiences specializing in new logo acquisition and/or new business development. - An avid hunter with a proven track record of sourcing new leads and leveraging social networking to gain access to decision-makers/influencers necessary to close business. - Relationship and sell with experiences with top VARs and Integrators. - Subject matter expertise in data storage, data management, data analytics and other IT services. - Domain knowledge of large enterprise IT environments and corporate buying centres are critical. - Must demonstrate a consistent track record of achieving annual quota targets while providing specific details on key customer wins. - The ideal candidate will bring an established sales management process, experience building and maintaining relationships with management and C level executives. - A successful track record of managing and closing complex sales campaigns, using outcome and solution selling techniques is a must. - Possesses a competitive attitude, strong work ethic and thrives in a fast pace, high growth and matrixed organizational environment. - Must be a proficient user of Salesforce and other MS Office tools. - Having a BA/BS degree or equivalent is desirable. We need to keep each as list items. Benefits: from "How We Look After You": - We help take care of your today and tomorrow with industry-leading benefits, support, and services that look after your holistic health and wellbeing. - We're also champions of life balance and offer flexible arrangements that work for you (role and location dependent). - We're always looking for new ways of working that bring out our best, which leads to unexpected ideas. - So here, you'll experience a sense of belonging, and discover autonomy, freedom, and ownership as you work alongside talented people you enjoy sharing knowledge with. - We're proud to say we're an equal opportunity employer and welcome all applicants for employment without attention to race, colour, religion, sex, sexual orientation, gender identity, national origin, veteran, age, disability status or any other protected characteristic. - Should you need reasonable accommodations during the recruitment process, please let us know so that we can do our best to set you up for success. But note: EEO statement is considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the EEO paragraph and the accommodation request? The accommodation request might be considered part of EEO? It's about reasonable accommodations; could be considered legal. Probably remove that as well. However, the benefits section includes industry-leading benefits, flexible arrangements