Territory Manager

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Overview: description about role. Could be "About the role". We'll put that as

About the role

with

containing overview. Responsibilities: there is a big list under Job Duties and Responsibilities with subcategories: Operational Excellence, Associate Support, Leadership, Customer Satisfaction and Engagement, Sales and Marketing. We'll combine into a

• list. Should we keep subheadings? Not required; just list items. We'll include each bullet as
• . Ensure we preserve all substantive info. Requirements: Education and Experience section. We'll put as

  Requirements

  maybe also Qualifications? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. The posting has Education and Experience, Core Knowledge and Skills, Work Environment and Physical Demands, Salary Range, Benefits and Well-Being. So we can map: - About the role: Overview paragraph. - Responsibilities: Job Duties and Responsibilities. - Requirements: Education and Experience (maybe also Work Environment? but that's more about demands). Could treat Work Environment as Requirements? But better to separate: Requirements (education/experience), Qualifications (maybe core knowledge and skills?), Skills (maybe also core knowledge and skills). However we need to avoid thin sections. Let's see content: Education and Experience: Bachelor’s Degree or equivalent combination of education and experience; At least 4 years’ professional experience with 2 years of related management experience; Prior experience in improving customer satisfaction and driving positive business outcomes; Experience in account management and direct customer interface; Prior experience managing in the staffing industry or similar preferred; Proven leadership competencies and experience. Core Knowledge and Skills: list of skills: Excellent written and verbal communication skills; Proficient in financial performance analysis; Success in developing and maintaining customer relationships; Advanced problem-solving abilities; Capable of defining problems, collecting data, and making informed decisions; Ability to prioritize tasks and meet deadlines under pressure; Proven ability to drive processes and improve operational performance; Demonstrated leadership competencies; Experience in hiring, managing, developing, and leading individuals and teams; Proficient in MS Office suite (Excel, PowerPoint, Outlook) and Teams. Work Environment and Physical Demands: details about driver's license, vehicle, work hours, travel, physical demands. Salary Range: $62,673 - $75,207 annually, depending on experience and geographic location, plus eligibility for incentive pay, subject to plan terms. Note about actual compensation. Benefits and Well-Being: list of benefits. Thus we can map: - About the role: Overview. - Responsibilities: Job Duties and Responsibilities. - Requirements: Education and Experience. - Qualifications: Core Knowledge and Skills (maybe also Work Environment? but that's more about demands; could be Qualifications). - Skills: maybe we could combine Core Knowledge and Skills into Skills, but we already used Qualifications for that. Could also put Work Environment under Requirements? But we need to avoid thin sections. Let's think: The instruction says prefer a few substantive sections over many thin ones. So we could combine Education and Experience + Core Knowledge and Skills into Requirements (or Qualifications). But we need to follow headings list: they gave examples but not mandatory to use all. We should include sections only when posting has real specific content. So we can choose which headings to use based on content. We have content for: About the role, Responsibilities, Requirements (education/experience), Qualifications (core knowledge/skills), Benefits, Pay (salary range). Schedule? Not mentioned besides work hours may require flexibility and availability in evenings and weekends as necessary. That's schedule info. Could create Schedule section with that detail. It's specific enough. So include Schedule. We should not include sections like "Work Environment" as separate heading unless we map to something else. Could incorporate physical demands into Schedule? Not ideal. Could add a section "Working Conditions" but not in allowed headings list. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should map our content to those headings. We can omit any that don't have content. Thus we need to map: - About the role: Overview paragraph. - Responsibilities: Job Duties and Responsibilities. - Requirements: Education and Experience. - Qualifications: Core Knowledge and Skills. - Skills: maybe we could put Work Environment and Physical Demands under Skills? Not really skills. Could omit Skills section if no specific skill content beyond what's in Qualifications. But we have core knowledge and skills already; maybe we treat that as Skills and Qualifications as something else? The distinction is ambiguous. But we can decide to put Core Knowledge and Skills under Skills, and Requirements under Requirements (education/experience). Then Qualifications could be omitted or we could put something like "Proven leadership competencies" but that's already in core knowledge. Better to follow typical pattern: Requirements = education/experience; Qualifications = knowledge/skills; Skills = maybe technical skills? But we have both. To avoid thin sections, we could combine Qualifications and Skills into one section, but we need to pick one heading. Let's see: The posting has "Core Knowledge and Skills". That's essentially skills. So we can put that under Skills heading. Then Requirements heading for education/experience. Then we can omit Qualifications heading (since no separate qualifications beyond those). That seems reasonable. Thus sections: - About the role - Responsibilities - Requirements - Skills - Benefits - Pay - Schedule Check each for substantive content. About the role: Overview paragraph (first paragraph). We'll copy that. Responsibilities: list all duties from Job Duties and Responsibilities. We'll need to convert each bullet into

  . The text includes headings like Operational Excellence:, Associate Support:, Leadership:, Customer Satisfaction and Engagement:, Sales and Marketing:. We could keep those as part of list items or as subheadings inside

  . Probably better to keep as part of the item text. We'll extract each bullet: Operational Excellence: - Manage territory profit and loss (P&L). - Monitor performance metrics and financial data to assess and improve operational effectiveness. - Identify, prioritize, and resolve operational issues. - Oversee day-to-day operations. - Maintain branch appearance in alignment with company standards. - Identify high-priority tasks and assign them to team members for timely and successful completion. - Promote and ensure a culture of safety. - Manage workers' compensation claims. - Accountable for compliance with organizational standards, customer requirements, as well as federal, state, and local regulations. - Streamline processes for operational excellence. - Lead change initiatives and adopt new systems. Associate Support: - Promote a Safe Workplace by conducting on-site safety visits, performing associate check-ins, and ensuring personal protective equipment (PPE) is accessible to associates. - Lead investigations for workers' compensation claims - Conduct new hire orientations at customer locations as needed. - Represent the company at local job fairs and build relationships with community partners, including unemployment offices. Leadership: - Manages territory staff including hiring, scheduling and assigning work, reviewing performance, and recommending promotions, transfers, demotions or terminations. - Set performance goals and professional development plans. - Lead team building and staff development activities. - Strategize and drive grassroots recruiting in local markets when needed. - This role will manage 2 - 7 individual contributors potentially across multiple locations. Customer Satisfaction and Engagement: - Retain and expand existing customer accounts. - Monitor customer feedback and recommend strategies to improve the customer experience. - Travel to customer sites for sales and safety needs. - Troubleshoot customer service issues and provide resolutions. Sales and Marketing: - Use existing data and dashboards to identify and re-engage with past billing customers. - Support existing customer base to drive additional sales. - Create price quotes for prospective customers. - Understand local market conditions and support current and prospective sales opportunities. - Ensure leads sourced by Sales Enablement are followed up on – when applicable. We'll combine all into one

  • list. Requirements: Education and Experience paragraph. Skills: Core Knowledge and Skills list. Benefits: Benefits and Well-Being paragraph. Pay: Salary Range paragraph. Schedule: Work Environment and Physical Demands includes work hours flexibility, travel, physical demands. We'll extract schedule info: "Work hours may require flexibility and availability in the evenings and weekends as necessary." Also "Up to 50% of the work could be outside of the territory at customer sites performing sales activities." That's more about travel but could be schedule. We'll include that. We should not include physical demands like lifting etc. That's not schedule. Might be considered work environment but we don't have a heading for that. Could we include under Schedule? It's not schedule but we could still include as part of Schedule? Might be odd. Better to omit physical demands if not fitting any heading. But we must preserve ALL substantive information; we cannot omit details. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include the physical demands info somewhere. Since we don't have a specific heading for work environment, we could incorporate it into Schedule or maybe into Requirements? But it's not about requirements. Could we add a section "Work Environment" even though not in the examples? The 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 an exhaustive list. So we could add other headings if needed, as long as they are

    . The instruction: "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 not strictly limited to them. However 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 a heading for Work Environment if we have content. It didn't forbid other headings. So we can add a heading "Work Environment and Physical Demands". That would be appropriate. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule, Work Environment and Physical Demands. But we must avoid thin sections. Work Environment and Physical Demands has substantive content, so okay. Now we need to ensure we don't repeat job title as heading. We won't. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. At the end there is a lot of EEO statement. We'll remove that. Also remove "We consider qualified applicants with arrest and conviction records..." etc. That's EEO/boilerplate. Remove. Also remove navigation/cookie etc. Not present. Now produce HTML fragment. We'll need to wrap each section in

    and then content. For lists: use

    • . For prose:

      . We'll need to preserve all details exactly as given, but we can format. Let's draft. About the role: The overview paragraph: "The Territory Manager is a key role in the organization and is responsible for the day-to-day operations and well-being of the branch (s) in the territory. This role is accountable for driving revenue growth and profitability of the territory. Responsibilities include ensuring that the territory meets performance goals, following standard operating procedures, and optimizing customer service. Additionally, this role includes supervisory and staff development