National Account Sales Executive

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting. We have company description at start: "The CompanyMiner Ltd, an OnPoint Company, is an industry-leading service and equipment solutions provider..." That's about the company. Could be "About the role"? Actually "About the role" is for role description. The job summary is "Job SummaryThe National Accounts Sales Executive is responsible for generating business opportunities..." That could be under "About the role" or maybe "Job Summary". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content accordingly. We need to include sections: About the role (job summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule (if present). We must not repeat job title as heading. Also we should not include Job ID etc. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to drop EEO statement (the long paragraph about Miner Ltd. considers applicants...), disclaimer about external job boards, etc. Also drop "Physical Demands", "Work Environment" maybe? Those are not in the list of allowed headings; but we could possibly include them under something else? The instruction says use headings for those specific categories; we should not create other headings. However we could incorporate that info into existing sections if relevant? But the instruction: "Prefer a few substantive sections over many thin ones." It doesn't forbid other headings, but says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't say we cannot add other headings, but likely we should stick to those. However we have content like Physical Demands and Work Environment; maybe we can omit them as they are not required sections? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep that info. If we omit a section, we lose that info. But we could incorporate that info into e.g., Responsibilities or Requirements? Not appropriate. Perhaps we can create a section like "Physical Demands" and "Work Environment" as headings, but the instruction only gave examples, not an exhaustive list. It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings, but we could also use others if needed. However the instruction later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create sections for any meaningful content, using

. The examples are just typical. So we can include Physical Demands and Work Environment sections. But we also need to remove boilerplate like EEO, disclaimer, etc. We also need to include Benefits section with details: Competitive pay – Plus incentive opportunities! Full benefits package that starts day one – Includes medical, dental, vision, 401K with match, company-paid life insurance and disability coverage. PTO and Paid Holidays Training and mentoring – Learn from our experts in the industry Advancement opportunities Link to benefits overview: Benefits The benefits listed are subject to change at any time. Please speak with an HR Representative for details. In the case of conflict between the information listed and the official plan documents, the plan documents will always govern. We need to preserve that. Also Pay section: Salary Range $80,000 - $90,000 per year. Also note "Employees may be eligible for additional incentive pay." That's part of Pay. Schedule: Not mentioned. So we should not create a Schedule section. Qualifications: Might be covered under Requirements? The posting has Requirements section with experience, education, etc. Also there is a "Competencies" list: Sales, Customer service, Initiative, Teamwork, Timeliness, Attention to detail, Organizational skills, Ability to manage a book of business while meeting goals and deadlines. Those could be Skills or Qualifications. The instruction includes Qualifications and Skills sections. We need to decide where to put competencies. Could be Skills. Requirements could be experience, education, etc. Qualifications could be maybe "High School Diploma or GED is required. Further education is preferred." But that's also in Requirements. Might be overlapping. Better to follow the posting: There's a "Requirements" bullet list (Experience in customer service, required. Direct business-to-business sales experience preferred. Experience in Industrial Sales, preferred. High School Diploma or GED is required. Further education is preferred. Excellent oral and written communication. Experience with Microsoft Office Products such as: Word, Excel, PowerPoint, Outlook, and Teams is preferred. Experience with Salesforce or a similar CRM is preferred. Willingness to travel frequently to meet with clients and future prospects. Must have valid drivers’ license and clean driving record (Department of Motor Vehicles). Must own reliable transportation. The selected candidate will be required to pass a criminal history background check.) That's clearly Requirements. Then there is a "Competencies" list: Sales, Customer service, Initiative, Teamwork, Timeliness, Attention to detail, Organizational skills, Ability to manage a book of business while meeting goals and deadlines. Those could be Skills. Qualifications maybe not separate; but we could treat Qualifications as education/credentials? However the posting doesn't have a separate Qualifications section besides what's in Requirements. We could omit Qualifications section if no specific content beyond what's already in Requirements. But we must preserve all substantive info; if we omit Qualifications, we lose nothing because it's covered. However we need to avoid empty headings. So we can skip Qualifications. Skills section: we can put Competencies there. Responsibilities: we have Job Responsibilities paragraph with many duties. About the role: we have Job Summary. Benefits: we have Benefits paragraph. Pay: we have Salary Range. Schedule: none. Physical Demands and Work Environment: we could include as separate sections, but not in the examples. However we need to preserve all substantive info. So we should include them. Could we incorporate them into Responsibilities? Not appropriate. Better to add sections Physical Demands and Work Environment. But the 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 we should follow the pattern. However adding Physical Demands and Work Environment is okay as they are substantive. We also need to remove boilerplate: EEO paragraph, Disclaimer about external job boards, etc. Also remove "Link to benefits overview: Benefits" maybe keep as part of benefits? It's a link; we can keep the text but maybe it's not substantive? It's a link; we can keep as part of benefits description. Also remove "*This job description is subject to change at any time." That's in Requirements? Actually appears after Requirements: "*This job description is subject to change at any time." That's a note; we could keep it as part of Requirements? It's a meta note; maybe we can drop as boilerplate? It's not exactly EEO but it's a disclaimer about job description changes. Might be considered boilerplate; but it's not navigation/legal/EEO. It's a generic statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those; it's a disclaimer about job description changes. Might be considered legal boilerplate. Safer to remove it. Also remove "Physical DemandsThe physical demands described here are representative..." That's not boilerplate; it's substantive. Also remove "Work EnvironmentThe work environment characteristics described here are representative..." Also substantive. Also remove "Miner Ltd. considers applicants for all positions without regard to race, color, religion, creed, gender, national origin, age, disability, genetic information, marital or veteran status, or any other legally protected status." That's EEO; remove. Also remove "DisclaimerThis job posting may also appear on other job boards...." That's disclaimer; remove. Also remove "Salary RangeThe pay range noted represents the company’s good faith minimum and maximum range for this role at the time of posting. The actual compensation offered to a candidate will be dependent upon several factors, including but not limited to experience, qualifications, and geographic location. Employees may be eligible for additional incentive pay." That's part of Pay; we can keep the substantive salary range and note about incentive pay. The preceding sentences about good faith range etc. is somewhat boilerplate but still part of Pay description; we can keep it as it's relevant to pay. However we might trim to just the salary range and incentive eligibility. But we must preserve ALL substantive information; the good faith range statement is substantive about how the range is determined. So keep. Also we have "Salary Description$80,000 - $90,000 per year". We'll combine. Now we need to output HTML fragment only, no /, no markdown fences. We'll structure:

About the role

Job Summary content.

Responsibilities

• ... each duty as li

We need to break responsibilities into list items. The responsibilities paragraph includes many items separated by semicolons and periods. We'll parse. Responsibilities text: "Drive and manage the sales process with designated national accounts based on the agreement executed between Miner and the national account. This includes: Contacting defined locations; Identifying client solutions; Negotiating; Quoting & Closing sales; and maintaining communications based upon Miner’s approved tracking procedures. Drive KPI results to target including: site calls, site visits, site activations, revenue, gross profit, SafeACT sold, SafeCHECK sold, quotes generated, quotes closed-won, quotes closed-lost. Act as a "solutions expert" consultant in helping partners with their unique business challenges and strategic initiatives. Work with senior management to establish a clear and effective plan for growing national account sales within a defined territory / region. Collaborate with sales teams to share ideas, knowledge and new business development strategies. Work seamlessly with National Account Managers to address barriers or customer issues promptly. Utilize company CRM / Tracker to provide visibility and effectively communicate activity in assigned territory. Utilize SafeACT to provide recurring service to customers – Volume to be defined. Utilize SafeCHECK to provide national account surveys & summaries – Volume to be defined. Attend company national account introductory (rollout) sessions and/or training programs and accompany other associates or managers during ride-alongs to promptly penetrate defined national accounts. Prepare appropriate specifications and level of service expectations in accordance with existing laws, regulations, and company policies. Calculate accurate job costs & market-based pricing for solutions. Demonstrate excellent customer service when communicating with customers. Other duties assigned by supervisor." We'll turn each sentence or clause into

. Might be many; but okay. Next, Requirements section: list items. Requirements text: "Experience in customer service, required. Direct business-to-business sales experience preferred. Experience in Industrial Sales, preferred. High School Diploma or GED is required. Further education is preferred. Excellent oral and written communication. Experience with Microsoft Office Products such as: Word, Excel, PowerPoint, Outlook, and Teams is preferred. Experience with Salesforce or a similar CRM is preferred. Willingness to travel frequently to meet with clients and future prospects. Must have valid drivers’ license and clean driving record (Department of Motor Vehicles