Territory Manager
Enovis · Minneapolis, MN · 1 mo ago
SalesFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
First part: "Who We Are ABOUT ENOVIS™ Enovis Corporation (NYSE: ENOV) is an innovation-driven medical technology growth company dedicated to developing clinically differentiated solutions that generate measurably better patient outcomes and transform workflows. Powered by a culture of continuous improvement, global talent and innovation, the Company’s extensive range of products, services and integrated technologies fuels active lifestyles in orthopedics and beyond. For more information about Enovis, please visit www.enovis.com."
That's about the company. Could be "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction: use
. Need to ensure we capture all responsibilities.
List of responsibilities from text:
"Accountable for achievement of assigned Company goals and objectives through sales to designated accounts.
Cultivates customer relationships by initiating contact with physicians, clinic staff, and other device users.
Understands the competitive landscape, trends in the industry, and the Company’s position in the market.
Layperson expert concerning clinical science & Enovis platforms’ mechanisms of action
Demonstration & education on technical and clinical aspects of products to customers, prospective customers, and patients.
Coordinates company technical engineering services to develop solutions to customers’ needs.
Prepares price quotations, communicates, and/or negotiates terms and conditions of sales within limits of authority
Writes orders subject to company policy.
Assists with equipment delivery, set-up, follow-up, and service as needed.
Supports network of key professionals & related personnel to educate referrals on Enovis products.
Facilitates local educational and sales events, with the support of other internal resources, to augment the business presence.
National, Regional, State and Local attendance at various tradeshows and conferences are required.
Expand usage of Lightforce Laser & Chattanooga Shockwave administrations
Sales Territory Management Develops & executes a business plan designed to exceed financial, market, and product portfolio goals for assigned territory.
Utilizes Salesforce to maintain up to date contacts, opportunities, targets, and outcomes.
Maintains sales funnel for sustained opportunities.
Maintains comprehensive and effective strategic call plans that drive positive sales results.
Schedules and prioritizes time for effective territory coverage.
Effectively manages leads: Identifies, qualifies, and cultivates new sales opportunities
Responsible for performing region penetration coverage and account identification to drive sales and increase customer base.
Pre-plans sales calls and maintains efficient time management skills to ensure maximum customer contact and service.
Drives sales through indirect sales channels
Customer Relationship Develops and maintains key customer relationships to achieve account objectives.
Takes responsibility for customer satisfaction and loyalty.
Responds to customer needs and concerns to resolve issues quickly and professionally.
Effectively manages customer & dealer relationships to meet sales revenue objectives.
Fosters strong relationships with Regional Account Managers (Chattanooga) and dealer network.
Competitive Selling Proactively cultivates competitive opportunities that result in converted business.
Defends competitive threats to minimize losses.
Identifies underlying problems affecting organizational or individual performance such as market conditions, competitor actions, or other external forces.
Provides presentations and demonstrations to the customer on application and use of Enovis products using effective communication and sales techniques.
Compliance Demonstrates commitment to the Enovis Compliance & Ethics Program, the Enovis Code of Conduct, the Enovis Sales and Marketing Code of Conduct, the AdvaMed Code of Ethics, and all supporting and applicable regulations, policies, and procedures.
Treats Protected Health Information (PHI) with the strictest confidentiality in accordance with HIPAA standards.
Acquires a basic understanding of the field to include regulatory compliance issues and adhere to these guidelines.
Administrative Completes administrative responsibilities in an accurate and timely manner.
Completes tasks assigned as well as expense reports, surveys, business plans, regional reports, training records, etc.
Develops or uses systems to organize and track information."
We need to split into separate items. Some lines are long sentences; we can keep each as separate . Might be many items; that's okay.
- Requirements: The posting has "Qualifications" section with subparts: Experience, Education, General Skills/Competencies/Specialized Knowledge (list of many). Also there is "TRAVEL REQUIREMENTS/WORK ENVIRONMENT And PHYSICAL DEMANDS". That could be considered Requirements? But we have separate headings for Requirements and Qualifications. Usually Requirements = experience/education; Qualifications = skills. But we can decide.
We have "Experience Minimum of 3 years of experience in Sales or relevant Customer Service". "Education Minimum Bachelor’s degree or equivalent combination of education and experience". Then a long list of General Skills/Competencies/Specialized Knowledge (communication, interpersonal, presentation, initiative, problem solving, decision making, adaptability, trust and integrity, collaboration and teamwork, customer orientation, business acumen, global/business perspective, computer skills, technical skills). Those could be under Skills.
Thus we can have:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." It might be okay to add another heading like "About Enovis". However the instruction says "Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
First part: "Who We Are ABOUT ENOVIS™ Enovis Corporation (NYSE: ENOV) is an innovation-driven medical technology growth company dedicated to developing clinically differentiated solutions that generate measurably better patient outcomes and transform workflows. Powered by a culture of continuous improvement, global talent and innovation, the Company’s extensive range of products, services and integrated technologies fuels active lifestyles in orthopedics and beyond. For more information about Enovis, please visit www.enovis.com."
That's about the company. Could be "About the role"? Actually "Who We Are" is about company. Could be "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading for description of role. But we also have "Who We Are" which is about company; maybe we can treat as "About the company" but not in list. However we should only use those headings if content matches. The posting includes "What You'll Do" and then details. So we can have sections: About the role (maybe summarizing what you'll do), Responsibilities (list of duties), Requirements (maybe qualifications), Qualifications (maybe education/experience), Skills (maybe competencies), Benefits (none explicit), Pay (none), Schedule (none). We must not create sections with placeholder text. So only include sections where we have real content.
Let's extract:
- About the role: Could be the paragraph under "What You'll Do Sales Territory Manager At Enovis™ we pay attention to the details..." That's a description. We'll put that as prose under About the role
.
- Responsibilities: The bullet list under "Key Responsibilities" (multiple lines). We'll convert each line to
About the role
. - Responsibilities: The bullet list under "Key Responsibilities" (multiple lines). We'll convert each line toRequirements
with- Minimum of 3 years of experience in Sales or relevant Customer Service
- Minimum Bachelor’s degree or equivalent combination of education and experience
Skills
with list of each skill. We also have "TRAVEL REQUIREMENTS/WORK ENVIRONMENT And PHYSICAL DEMANDS" which includes travel up to 75%, occasional overnight up to 5 days, considerable time traveling in car, requires air travel based on territory needs. That's substantive; we could put under a heading like "Travel Requirements" but not in allowed list. The allowed headings are limited to those examples; but we could still use "Schedule"? Not exactly. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should prefer those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create a section for "Travel Requirements" if we think it's appropriate, but the instruction suggests we should stick to those examples. However "Schedule" could cover travel? Not really. "Pay" and "Benefits" not present. So we may omit travel info? But we must preserve ALL substantive information; we cannot drop travel requirement. So we need to include it somewhere. Perhaps we can put it under "Requirements" as a bullet? Or under "Responsibilities"? Travel is a requirement of the job. Could be included under "Requirements" as a bullet: "Must be able to travel up to 75% of the time, with occasional overnight travel up to 5 days; considerable time spent traveling in car to customer accounts; requires air travel based on territory needs." That seems reasonable. Thus we can add that to Requirements list. Now "Qualifications" heading: The posting has a "Qualifications" section that includes the experience, education, and skills. But we already used Requirements for experience/education and Skills for competencies. Could we still have a Qualifications heading with maybe nothing? Better to avoid empty. So we might not include Qualifications heading; instead we treat the content under Requirements and Skills. The instruction says we can use those headings as examples; we are not required to use all. So we can omit Qualifications if we have split content. But we also have a separate "Qualifications" heading in the posting that includes the experience, education, and skills. If we omit Qualifications heading, we still preserve the info under Requirements and Skills. That's fine. Now "About the role": we have the paragraph under "What You'll Do". Let's extract that paragraph: "What You'll Do Sales Territory Manager At Enovis™ we pay attention to the details. We embrace collaboration with our partners and patients, and take pride in the pursuit of scientific excellence — with the goal of transforming medical technology as we know it. Because that’s how we change the lives of patients for the better. And that’s how we create better together. Why work at Enovis? See for yourself. As a key member of Recovery Sciences, you will play an integral part in helping Enovis drive the medical technology industry forward through transforming patient care and creating better patient outcomes." We need to preserve that as prose. Might be multiple sentences; we can put in
. Now "Who We Are" about company: Should we include? It's substantive but not under allowed headings. Could we put under "About the role"? No. Could we create a heading "About the company"? Not in list but maybe allowed as it's not prohibited; 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 says "Prefer a few substantive sections over many thin ones." It might be okay to add another heading like "About Enovis". However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the expected headings. Safer to stick to those. But we need to preserve all substantive info; we could fold the company description into the About the role paragraph? Might be odd but we could add a sentence at start: "Enovis Corporation is an innovation-driven medical technology growth company..." as part of About the role description. That would preserve it.
Thus About the role paragraph can include both the company overview and the role description. Let's combine: start with company description then the role description.
Now we need to ensure we don't include boilerplate like EEO statements, navigation, etc. Remove those at end.
Now produce HTML:
About the role
About the role
Enovis Corporation (NYSE: ENOV) is an innovation-driven medical technology growth company dedicated to developing clinically differentiated solutions that generate measurably better patient outcomes and transform workflows. Powered by a culture of continuous improvement, global talent and innovation, the Company’s extensive range of products, services and integrated technologies fuels active lifestyles in orthopedics and beyond. For more information about Enovis, please visit www.enovis.com. As a key member of Recovery Sciences, you will play an integral part in helping Enovis drive the medical technology industry forward through transforming patient care and creating better patient outcomes. At Enovis™ we pay attention to the details. We embrace collaboration with our partners and patients, and take pride in the pursuit of scientific excellence — with the goal of transforming medical technology as we know it. Because that’s how we change the lives of patients