Manager, Regional Sales

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate, navigation, EEO, etc. Include only sections with real specific content. Must preserve all substantive info. We need to parse the posting. Key sections: - About the role: The first paragraph(s) describing role: "The Manager, Regional Sales is responsible for translating Roadrunner’s regional growth strategy into disciplined field execution and sustained contribution margin performance. This role leads a team of Account Executives across a competitive transportation market where customer expectations, pricing dynamics, and service requirements evolve quickly. Success requires more than managing activity. This leader will build a rigorous sales operating system, strengthen pipeline quality, develop Account Executive capability, and create clear accountability for customer acquisition, retention, and profitable account growth. The successful candidate will establish a high-performance regional sales culture, improve forecast reliability, deepen strategic customer relationships, and ensure the team consistently delivers measurable business results." That's about role. - Responsibilities: The "What You’ll Do" section with bullet points: Lead regional sales execution (subpoints), Build a high-performing sales team, Strengthen pipeline and forecasting discipline, Expand strategic customer relationships, Convert market intelligence into action, Improve sales systems and effectiveness. Each bullet has subpoints. We need to output as

  • for each duty. Could nest? Probably just list each bullet as
  • with internal sentences. Could break subpoints into separate
  • but spec says use
    • for any list of duties/requirements/benefits. Could treat each major duty as
    • and include subpoints as sentences within. - Requirements: The "What You Bring" section includes minimum years experience etc. That's requirements. - Qualifications: maybe education? "Bachelor’s degree is preferred." Could be qualifications. - Skills: maybe "Strong analytical capability, including the ability to interpret market conditions, sales performance, and account-level economics. Excellent written, verbal, presentation, and executive communication skills. Strong knowledge of regional geography, competitive conditions, and economic trends. Ability to develop strategic customer relationships and participate effectively in complex sales discussions." Also "Experience using CRM platforms to manage opportunities, track activity, and improve forecast accuracy. Experience with Zoho CRM is preferred." Also "Willingness and ability to travel approximately 50% within the assigned region." Also "Less-than-truckload transportation experience is strongly preferred." Also "You think in systems..." etc (How You Operate) maybe part of skills/behaviors. - Benefits: "Benefits: Competitive benefits package including medical, dental, and vision insurance, 401(k), paid time off, and growth opportunities." - Pay: "Compensation: $110,000 per year" - Schedule: maybe "Location: Hybrid | Dallas, TX / Atlanta, GA Travel: Approximately 50% within the assigned region" This includes location and travel. Could be schedule? Not exactly schedule but location and travel. The spec says include Schedule section only if posting actually states them. There's no explicit schedule like full-time, part-time, hours. There's location and travel. Might treat as "Location & Travel" but not schedule. Since schedule not present, we should not create a Schedule section. However spec says include a section ONLY when posting has real, specific content for it. So we omit Schedule. Also we need to include Pay section (we have compensation). Benefits section. We need to avoid boilerplate like Physical Demands and Work Environment, EEO, etc. Remove those. Also remove duplicated lines like "Thank you! , TX , GA About Roadrunner" etc. We need to preserve all substantive info. So include the "How You Operate" bullet points? That's more about behaviors/skills. Could be placed under Skills or maybe a separate section like "Core Competencies". But spec only allows certain headings; we can put them under Skills as list. We need to decide what goes where. Let's extract content: About the role paragraph(s) as above. Responsibilities (What You’ll Do): - Lead regional sales execution - Lead, motivate, and hold Account Executives accountable for achieving and exceeding regional contribution margin goals. - Translate regional objectives into focused territory strategies, account priorities, and measurable execution plans. - Maintain a visible field presence through frequent customer meetings, sales calls, and ride-alongs. - Establish clear performance expectations and address execution gaps quickly and directly. - Partner with the Regional Director, Sales on territory alignment, resource deployment, and regional growth initiatives. - Build a high-performing sales team - Coach new and tenured Account Executives through structured one-on-one meetings, performance reviews, and field-based development. - Observe customer interactions and reinforce effective prospecting, discovery, negotiation, and account-management behaviors. - Develop targeted training programs that improve individual capability and strengthen team consistency. - Create a culture defined by ownership, urgency, collaboration, and measurable performance. - Recognize strong execution while maintaining clear accountability for results. - Strengthen pipeline and forecasting discipline - Ensure each Account Executive maintains a balanced pipeline across new business, customer retention, and profitable account expansion. - Drive disciplined use of Zoho CRM to support pipeline visibility, opportunity management, and accurate forecasting. - Review pipeline health, conversion performance, account activity, and forecast risk on a consistent cadence. - Identify gaps early and implement focused actions to improve opportunity quality and sales velocity. - Communicate regional forecasts, account activity, and territory strategies clearly to sales leadership. - Expand strategic customer relationships - Build senior-level relationships with priority customers, prospects, and other key market stakeholders. - Support Account Executives in securing new business, expanding profitable accounts, and strengthening long-term partnerships. - Engage directly in complex opportunities where leadership involvement can improve positioning or accelerate decisions. - Anticipate customer needs and translate operational capabilities into differentiated business value. - Reinforce Roadrunner’s commitment to reliability, precision, speed, and accountable service. - Convert market intelligence into action - Analyze regional market conditions, competitive activity, customer trends, and economic developments. - Identify emerging opportunities and risks, then convert those insights into actionable territory and account plans. - Maintain strong knowledge of the regional transportation landscape and relevant competitive alternatives. - Challenge assumptions using customer feedback, CRM data, and measurable market indicators. - Adjust regional priorities quickly when market conditions or business needs change. - Improve sales systems and effectiveness - Evaluate sales processes, CRM practices, training methods, and incentive programs for opportunities to improve execution. - Implement continuous-improvement initiatives that increase productivity, pipeline quality, and customer experience. - Use performance data to identify recurring barriers and establish scalable solutions. - Partner cross-functionally to align customer commitments with operational capabilities and service expectations. - Recommend programs, tools, and methods that strengthen regional sales performance. Requirements (What You Bring): - Minimum of five years of transportation sales experience. - Minimum of three years of sales management experience, including direct responsibility for coaching and performance accountability. - Demonstrated success leading field-based sales teams and delivering against revenue or contribution margin objectives. - Strong understanding of pipeline management, territory planning, forecasting, customer retention, and profitable account growth. - Experience using CRM platforms to manage opportunities, track activity, and improve forecast accuracy. Experience with Zoho CRM is preferred. - Strong analytical capability, including the ability to interpret market conditions, sales performance, and account-level economics. - Excellent written, verbal, presentation, and executive communication skills. - Strong knowledge of regional geography, competitive conditions, and economic trends. - Ability to develop strategic customer relationships and participate effectively in complex sales discussions. - Willingness and ability to travel approximately 50% within the assigned region. - Less-than-truckload transportation experience is strongly preferred. - Bachelor’s degree is preferred. Qualifications: maybe we separate education? But we already have Bachelor's degree in Requirements. Could treat Qualifications as education and certifications? Not much else. Could combine with Requirements. But spec says we can have both sections if content. We could put "Bachelor’s degree is preferred." under Qualifications. However we already have it in Requirements. To avoid duplication, maybe we put education under Qualifications and keep other items under Requirements. Let's see: The posting lumps education with other requirements. But we can split: Requirements: experience, management, success, understanding, CRM experience, analytical capability, communication skills, knowledge, ability to develop relationships, travel willingness, LTL experience. Qualifications: Bachelor’s degree preferred. That seems reasonable. Skills: Could be the "How You Operate" behaviors plus maybe the analytical capability etc. But we already used analytical capability in Requirements. To avoid duplication, we can keep Skills as the "How You Operate" list: systems thinking, ownership, data-driven, coaching, challenging assumptions, urgency, communication, balancing short/long term, credibility, modeling integrity. Also maybe "Strong analytical capability" etc could be considered skill but we already used. We'll keep Skills as the How You Operate bullet points. Benefits: as given. Pay: Compensation: $110,000 per year. Schedule: not present, omit. Now we need to output HTML fragment with headings

      and content. We must not include any markdown fences. We'll produce something like:

      About the role

      ...

      Responsibilities

      • Lead regional sales execution
        ... nested? But spec says use
        • for any list. It didn't forbid nested lists. Could nest but safer to just have flat list with sentences containing subpoints separated by semicolons. However that may lose readability but okay. Could also keep nested
          inside
          • . That still uses
            • . I think nested is fine. We'll produce nested lists. Similarly for Requirements, Qualifications, Skills, Benefits. We need to ensure we don't include boilerplate like "Physical Demands and Work Environment", EEO, etc. Let's craft. About the role paragraph: combine the two paragraphs? Actually there are two paragraphs: first about role responsibilities, second about successful candidate will... We'll combine into one

              . Now Responsibilities: We'll have

              Responsibilities

              with six main
              • each containing a
                of subpoints. Requirements:

                Requirements

                with each bullet as
                • . Qualifications:

                  Qualifications

                  • Bachelor’s degree is preferred.
                  Skills:

                  Skills

                  with each of the How You Operate points. Benefits:

                  Benefits

                  • Competitive benefits package including medical, dental, and vision insurance, 401(k), paid time off, and growth opportunities.
                  Pay:

                  Pay

                  Compensation: $110,000 per year

                  We should not include Schedule. Check for any other substantive content: Location and travel: "Location: Hybrid | Dallas, TX / Atlanta, GATravel: Approximately 50% within the assigned region". This is location and travel info. Could be considered under "Location & Travel" but not in allowed headings. Could we put under Responsibilities? Not appropriate. Could we put under Requirements? Travel willingness is already there. Location maybe not needed. The spec says we must preserve ALL substantive information. So we need to include location and travel somewhere. Since we don't have a heading for location, we could incorporate into Benefits? Not appropriate. Could add a

                  under maybe after Pay? But we need to follow allowed headings only? The instruction: "Use

                  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule