Regional Sales Manager - East
maybe. We need to remove boilerplate: EEO statements, navigation, legal, etc. Also remove "What We Offer" maybe we can treat as Benefits? The posting includes a benefits paragraph: "Our benefits include healthcare coverage (medical, prescription, dental, and vision), wellness programs, life insurance, a 401(k) plan with company match, paid time off, and an employee stock program, among other offerings." That's benefits. Pay: "Pay Range: The total pay range for this role, including incentive opportunities, is $100,000 - $120,000." Also mention bonuses. Schedule: Not given. Travel & Work Arrangements: Up to 50%+ overnight travel is common. That could be considered schedule? Not exactly schedule but maybe we can include under "Travel" but not required. Since schedule not specified, we should not create a Schedule section. Qualifications: The posting includes "Requirements:" with bullet list of competencies. Also "Preferences:" with extra experience. Could treat Requirements as qualifications. Also maybe "Skills" separate? The posting includes core competencies list; we could put under Requirements or Skills. According to rules, we can have sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to decide. We have "Responsibilities:" clearly a list. We have "Requirements:" includes Bachelor’s Degree 3+ years relevant Industrial Pump product sales experience. Then list of Core Competencies (these are skills/qualifications). Could treat as Requirements. We have "Preferences:" additional preferences. We have "What We Offer:" benefits. We have "Pay Range:" pay. We have location and maybe "About Us" could be "About the role"? Actually "About Us" is company overview; could be placed under a short paragraph maybe not a heading. The rule: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have an "About the role" section summarizing Job Overview. The posting includes "Job Overview:" paragraph. So we can put that under About the role. Thus sections: - About the role (h3) containing Job Overview paragraph. - Responsibilities (h3) with ul list of responsibilities. - Requirements (h3) with ul list: Bachelor’s Degree, 3+ years relevant Industrial Pump product sales experience, plus core competencies list? Might be too many. Could separate core competencies into Skills section. Let's think: The posting lists Core Competencies under Requirements. Could treat them as Skills. But we also have Preferences. Could put Preferences under Requirements as extra bullet. Better: Have Requirements (education/experience) and Skills (core competencies). But we need to avoid thin sections. However we have enough content for both. Let's extract: Education/Experience: Bachelor’s Degree, 3+ years relevant Industrial Pump product sales experience. Preferences: 5+ years outside sales experience preferred. Working knowledge of Salesforce. Working knowledge of SAP. Core Competencies list: Channel Sales Expertise, Product and Market Knowledge, Strategic Thinking and Planning, Customer-Centric Approach, Technical Proficiency, Strong Communication and Collaboration, Time and Task Management, Business Acumen, Self-Motivation and Discipline, Technology Proficient (Microsoft Office Suite, CRM tools like Salesforce). We could put core competencies under Skills. Thus sections: - About the role (Job Overview) - Responsibilities - Requirements (education/experience + preferences maybe) - Skills (core competencies) - Benefits - Pay We should not include Schedule. Now we need to preserve all substantive information, not invent or summarize away detail. Must not omit details like location, travel, etc. We need to include location somewhere. Could add a short
after the heading? The rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we can include in a
before sections. Also travel arrangement: Up to 50%+ overnight travel is common. That's substantive; we could include under Responsibilities maybe as a bullet? Or we could add a note in Responsibilities or a separate paragraph. Since it's not a responsibility but a work arrangement, we could add a
after Responsibilities maybe under a heading? But we don't have a heading for travel. Could add a short
after Responsibilities: "Travel: Up to 50%+ overnight travel is common." That preserves info. Also we need to include the part about "Hired applicant will be eligible to receive (discretionary/nondiscretionary) annual bonuses and incentive compensation." That's part of Pay section. Now let's craft HTML. We'll start with a
for location and maybe travel? Actually travel separate. We'll do:
Location: Remote within Territory (ME, VT, NH, MA, RI, CT, NY, NJ, MD, PA, WV, VA, TN, NC, SC, & GA).
Then About the role:About the role
[Job Overview text]
Job Overview text: "The Regional Sales Manager (RSM) is responsible for increasing the sales of the HASKEL BUTECH portfolio through all assigned Channel Distributors and Direct Key accounts (OEM, EPCs, and System Integrators.) The RSM will use superior sales strategy techniques and channel management skills and a full understanding of selling skills to ensure that all focus market sectors are targeted and that sales of all HASKEL BUTECH products are maximized. This role requires a Regional Sales Manager with high technical aptitude, accomplished in influencing brand preference, and the ability to articulate value proposition as part of the solution selling process. The individual should be well-versed in assisting, specifying, and purchasing decisions relative to the advantages of process equipment, including pressure boosting, flow calculations, etc." We need to preserve exactly; we can copy. Now Responsibilities: list each bullet from Responsibilities section. Let's extract bullet points: - Manage and Develop Channel Partners: Build, manage, and develop a robust network of Channel Partners to drive the sale of Paragon products. Assess partner competencies to identify strengths and areas of improvement, develop action plans, and appoint new partners in underperforming areas to meet business goals. - Collaborate with Stakeholders to Drive Strategy: Work closely with Channel Partner Principals, Product Champions, and the Senior Regional Sales Manager to develop and execute territory strategies that align with revenue, margin, and growth targets. - Lead Sales Activities and Pipeline Development: Identify, qualify, and pursue opportunities through cold calls, market research, and maintaining a network of industry contacts. Drive sales activity through Channel Partners to achieve measurable outcomes and maintain a documented pipeline via Salesforce. - Provide Technical and Product Support: Offer product education and technical assistance to customers, including troubleshooting, installation guidance, and identifying causes of product malfunctions to maintain the high-quality image of Paragon products. - Engage in the Sales Cycle and Account Management: Actively participate in all stages of the sales cycle, including quoting, account management, and assisting with collections. Establish measurable goals for targeted accounts and provide regular updates on progress and opportunities. - Collaborate with Cross-Functional Teams: Work with internal teams such as Engineering, Product Development, and Operations to ensure seamless implementation, new product commercialization, and effective account growth. - Lead Customer Engagement and Presentations: Schedule, facilitate, and lead presentations to customers while attending industry trade shows and conferences to establish contacts, identify trends, and proactively develop leads. - Oversee Channel Partner Network: Supervise a large network of Channel Partner organizations across multiple states, ensuring alignment with Paragon’s standards and objectives. We need to keep the colon after each heading? The original had headings like "Manage and Develop Channel Partners:" then description. We'll keep as list items with the heading bold? Not needed; just plain text. Now Requirements: Education/Experience and Preferences. We can list: - Bachelor’s Degree - 3+ years relevant Industrial Pump product sales experience - 5+ years outside sales experience preferred - Working knowledge of Salesforce - Working knowledge of SAP But note preferences are separate; we could still list them under Requirements as they are preferences. That's okay. Now Skills: core competencies list. List each: - Channel Sales Expertise: Strong understanding of channel sales strategies, including managing partner networks, driving revenue growth, and achieving measurable results through collaboration. - Product and Market Knowledge: Expertise in hydraulics, positive displacement blowers, and other rotating equipment, with the ability to articulate the value proposition of Paragon products in customer terms. - Strategic Thinking and Planning: Ability to assess market opportunities, develop actionable strategies, and set specific, measurable goals to drive growth and profitability. - Customer-Centric Approach: Skilled at building strong relationships, understanding customer needs, and providing tailored solutions to ensure high satisfaction and repeat business. - Technical Proficiency: Proficient in providing technical support, troubleshooting product issues, and guiding customers through product selection, installation, and maintenance. - Strong Communication and Collaboration: Excellent interpersonal, negotiation, and persuasion skills to foster positive relationships with customers, vendors, and internal teams. - Time and Task Management: Highly organized with strong time management skills, ensuring timely execution of tasks while balancing multiple priorities effectively. - Business Acumen: High level of business and financial acumen, enabling informed decision-making and alignment with organizational goals. - Self-Motivation and Discipline: Demonstrates intrinsic motivation, a disciplined work style, and the ability to work independently while contributing as part of a team. - Technology Proficiency: Skilled in using Microsoft Office Suite (Word, Excel, PowerPoint, Teams, Outlook) and CRM tools like Salesforce to document and manage sales opportunities. Now Benefits: paragraph from What We Offer. Paragraph: "At Ingersoll Rand, we embrace a culture of personal ownership — taking responsibility for our company, our communities, and our environment — as well as for our individual well-being. Our comprehensive benefits package is designed to empower you with the tools and support needed to take charge of your health and future. Our benefits include healthcare coverage (medical, prescription, dental, and vision), wellness programs, life insurance, a 401(k) plan with company match, paid time off, and an employee stock program, among other offerings. These benefits, combined with our pay transparency and inclusive culture, reflect our commitment to supporting you at work and beyond." We could split into two paragraphs but it's fine as one. Now Pay: paragraph. Paragraph: "Pay Range: The total pay range for this role, including incentive opportunities, is $100,000 - $120,000. The pay range takes into account a wide range of factors that include a candidate’s skills; experience and training; licensure and certifications; and geographic location. Hired applicant will be eligible to receive (discretionary/nondiscretionary) annual bonuses and incentive compensation." We need to keep the exact text. Now travel note: we can add a
after Responsibilities maybe: "
Travel: Up to 50%+ overnight travel is common with this role.
" Now ensure we didn't include boilerplate: removed EEO, "About Us" company overview (we didn't include that; we only used Job Overview). Did we lose any substantive info from "About Us"? That is company overview; not required to include as per rule? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Us" is substantive about company. Should we include it? Possibly yes. But we have limited sections; we could add an "About the company" section? Not in allowed headings list but we could use awithout heading. The rule says