Product Application Specialist
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe slight formatting). Ensure we don't lose any.
Let's extract sections.
About the role: The initial paragraph(s) before Responsibilities. Let's combine:
"We are constantly looking to add to our core talent. If you are seeking a career that is challenging and rewarding, a work environment that is diverse and dynamic, look no further — Haemonetics is your employer of choice. This position is responsible for providing technical support for customers within an assigned territory, providing support on product-related technical, quality, and regulatory questions. Provides technical support for the North America product portfolio, new product implementations, internal and external training. Working closely with senior team members, the incumbent collaborates with appropriate departments (Quality, Regulatory, R&D, Manufacturing, North America Marketing teams) to address customer needs, support product adoption, and contribute to customer satisfaction and business growth. Coordinates all activities to maintain product application consistency and to optimize business opportunities."
That's the prose.
Responsibilities: list bullet points after "Responsibilities". Let's capture each:
- Provide technical support for customers within assigned territory, addressing product, quality, and application-related inquiries and escalating issues as appropriate.
- Assist with the development or delivery of technical education and product training programs to ensure a uniform, high standard of training and optimal product results, promoting product confidence and ensuring customer satisfaction.
- In partnership with senior team members, provide training to internal and external customers as needed.
- Communicate success, best practices, and techniques of tactile execution programs to Product Applications, Marketing, and Sales teams.
- Maintain and expand technical knowledge of Haemonetics’ existing product portfolio as well as competitive products.
- Support the execution of sales and marketing initiatives for assigned products to promote successful product utilization and achievement of business objectives.
- Provide sales and account management team with technical representation during customer presentations, meetings, conferences, and seminars.
- Assist in providing technical, quality, and regulatory support for the assigned product portfolio within the territory.
- Support product implementations and customer onboarding activities, working collaboratively with senior team members and cross-functional partners.
- Act as a liaison between customers and internal teams by communicating customer feedback, technical concerns, and product-related opportunities.
Check if any missing: The original had line breaks but these are the items.
Requirements: after "Requirements". The text:
"1 to 2 years working experience with technical experience with medical devices, or clinical experience with plasma collection
Experience in customer product integration and training desired
Remote based with ability to travel domestically 50% of the time
Bachelor’s Degree Required, degree in biomedical engineering, electrical engineering, computer engineering or other technical discipline desired
People Person With Excellent Presentation And Communication Skills Required
Ability to troubleshoot product, application, and customer issues.
Ability to work effectively within cross-functional teams.
Strong organizational and time-management skills.
Attention to detail and follow-through."
We need to keep each as list items. Note "Remote based with ability to travel domestically 50% of the time" could be schedule but it's in requirements. We'll keep it there; but we also might create Schedule section. However we should not duplicate content. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move that line to Schedule, we must remove it from Requirements to avoid duplication. But we could keep it in both? That would be duplication, which is not allowed? It says "do NOT repeat the job title as a heading" and "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't explicitly forbid duplication of content, but we should avoid redundancy. Better to keep it in Requirements (as it's listed there) and not create a separate Schedule section unless we have other schedule info. However we could create Schedule section and keep the line there, and remove from Requirements. But then we lose that line from Requirements as originally listed; but we could still keep it in Requirements as part of the list? The instruction says preserve ALL substantive information; we can keep it in both places? That would be duplication but still preserving. However they said "fold minor metadata into a short
or drop it." This line is not minor metadata; it's a requirement about remote/travel. So it's substantive. I'd keep it in Requirements as a list item. And not create Schedule section unless we have other schedule specifics like "Remote based" etc. But we could still create Schedule section with that line and keep it also in Requirements? That would be duplication but still preserving. Might be okay but they'd prefer not to have thin sections. I'd rather not create Schedule section; just keep it in Requirements.
Thus sections: About the role, Responsibilities, Requirements, Pay, Benefits.
Pay: we have pay range and details. Let's capture:
"The pay range for this role is: $68,200.00-$116,000.00/Annual
The base pay actually offered to the successful candidate will take into account, without limitation, the candidate’s location, education, job-knowledge, skills, and experience in prior relevant roles.
Incentives may also be provided as part of Haemonetics’ employee compensation.
For sales roles, employees will be eligible for sales incentive (i.e., commission) under the applicable plan terms.
For non-sales roles, employees will be eligible for a discretionary annual bonus, the target amount of which varies based on the applicable role, to be governed by the applicable plan terms.
Employees may also be eligible to participate in the Company’s long-term incentive plan, with eligibility and target amount dependent on the role.
In addition to compensation, the Company offers a competitive suite of benefits to its employees, including without limitation, a 401(k) with up to a 6% employer match and no vesting period, an employee stock purchase plan, “flexible time off” for salaried employees and, for hourly employees, accrual of three to five weeks’ vacation annually (based on tenure), accrual of up to 64 hours (annually) of paid sick time, paid and/or floating holidays, parental leave, short- and long-term disability insurance, tuition reimbursement, and/or health and welfare benefits.
Depending on your location, you may be eligible for more detailed information related to the compensation and benefits related to this job posting.
If you believe you may be entitled to such information by law, you may contact 1-781-348-7777, Monday through Friday, 7:30 a.m. – 5 p.m. ET or email AskHR@Haemonetics.com."
But we need to remove boilerplate: EEO Policy Statement, contact info for compensation details? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The contact info for compensation details might be considered legal/boilerplate? It's about compensation transparency; maybe we keep it? It's not EEO, but it's a statement about contacting for more info. Might be considered boilerplate? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is not EEO. It's about compensation transparency contact. Might be okay to keep? However they also say "Remove ... application instructions." This is not application instructions. It's contact for compensation info. I'd keep it as part of Pay section? But the Pay section should include pay range and details. The contact info could be considered minor metadata; maybe we fold into a short
or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This contact info is minor metadata; we could fold into a short
under Pay or drop it. Safer to drop it? But we need to preserve ALL substantive information. Is that contact info substantive? It's about how to get more info; maybe not essential to the job description. I'd drop it to avoid boilerplate. Also the line "Depending on your location, you may be eligible for more detailed information related to the compensation and benefits related to this job posting." is also somewhat boilerplate. Might drop.
Thus Pay section: include pay range and details about base pay, incentives, sales incentive, discretionary bonus, long-term incentive plan. Keep those.
Benefits: we have list of benefits. Keep as list.
Now format.
We'll output:
About the role
...
Responsibilities
- ...
...
Requirements
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all bullet points exactly as given (maybe slight formatting). Ensure we don't lose any. Let's extract sections. About the role: The initial paragraph(s) before Responsibilities. Let's combine: "We are constantly looking to add to our core talent. If you are seeking a career that is challenging and rewarding, a work environment that is diverse and dynamic, look no further — Haemonetics is your employer of choice. This position is responsible for providing technical support for customers within an assigned territory, providing support on product-related technical, quality, and regulatory questions. Provides technical support for the North America product portfolio, new product implementations, internal and external training. Working closely with senior team members, the incumbent collaborates with appropriate departments (Quality, Regulatory, R&D, Manufacturing, North America Marketing teams) to address customer needs, support product adoption, and contribute to customer satisfaction and business growth. Coordinates all activities to maintain product application consistency and to optimize business opportunities." That's the prose. Responsibilities: list bullet points after "Responsibilities". Let's capture each: - Provide technical support for customers within assigned territory, addressing product, quality, and application-related inquiries and escalating issues as appropriate. - Assist with the development or delivery of technical education and product training programs to ensure a uniform, high standard of training and optimal product results, promoting product confidence and ensuring customer satisfaction. - In partnership with senior team members, provide training to internal and external customers as needed. - Communicate success, best practices, and techniques of tactile execution programs to Product Applications, Marketing, and Sales teams. - Maintain and expand technical knowledge of Haemonetics’ existing product portfolio as well as competitive products. - Support the execution of sales and marketing initiatives for assigned products to promote successful product utilization and achievement of business objectives. - Provide sales and account management team with technical representation during customer presentations, meetings, conferences, and seminars. - Assist in providing technical, quality, and regulatory support for the assigned product portfolio within the territory. - Support product implementations and customer onboarding activities, working collaboratively with senior team members and cross-functional partners. - Act as a liaison between customers and internal teams by communicating customer feedback, technical concerns, and product-related opportunities. Check if any missing: The original had line breaks but these are the items. Requirements: after "Requirements". The text: "1 to 2 years working experience with technical experience with medical devices, or clinical experience with plasma collection Experience in customer product integration and training desired Remote based with ability to travel domestically 50% of the time Bachelor’s Degree Required, degree in biomedical engineering, electrical engineering, computer engineering or other technical discipline desired People Person With Excellent Presentation And Communication Skills Required Ability to troubleshoot product, application, and customer issues. Ability to work effectively within cross-functional teams. Strong organizational and time-management skills. Attention to detail and follow-through." We need to keep each as list items. Note "Remote based with ability to travel domestically 50% of the time" could be schedule but it's in requirements. We'll keep it there; but we also might create Schedule section. However we should not duplicate content. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we move that line to Schedule, we must remove it from Requirements to avoid duplication. But we could keep it in both? That would be duplication, which is not allowed? It says "do NOT repeat the job title as a heading" and "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't explicitly forbid duplication of content, but we should avoid redundancy. Better to keep it in Requirements (as it's listed there) and not create a separate Schedule section unless we have other schedule info. However we could create Schedule section and keep the line there, and remove from Requirements. But then we lose that line from Requirements as originally listed; but we could still keep it in Requirements as part of the list? The instruction says preserve ALL substantive information; we can keep it in both places? That would be duplication but still preserving. However they said "fold minor metadata into a short
or drop it." This line is not minor metadata; it's a requirement about remote/travel. So it's substantive. I'd keep it in Requirements as a list item. And not create Schedule section unless we have other schedule specifics like "Remote based" etc. But we could still create Schedule section with that line and keep it also in Requirements? That would be duplication but still preserving. Might be okay but they'd prefer not to have thin sections. I'd rather not create Schedule section; just keep it in Requirements. Thus sections: About the role, Responsibilities, Requirements, Pay, Benefits. Pay: we have pay range and details. Let's capture: "The pay range for this role is: $68,200.00-$116,000.00/Annual The base pay actually offered to the successful candidate will take into account, without limitation, the candidate’s location, education, job-knowledge, skills, and experience in prior relevant roles. Incentives may also be provided as part of Haemonetics’ employee compensation. For sales roles, employees will be eligible for sales incentive (i.e., commission) under the applicable plan terms. For non-sales roles, employees will be eligible for a discretionary annual bonus, the target amount of which varies based on the applicable role, to be governed by the applicable plan terms. Employees may also be eligible to participate in the Company’s long-term incentive plan, with eligibility and target amount dependent on the role. In addition to compensation, the Company offers a competitive suite of benefits to its employees, including without limitation, a 401(k) with up to a 6% employer match and no vesting period, an employee stock purchase plan, “flexible time off” for salaried employees and, for hourly employees, accrual of three to five weeks’ vacation annually (based on tenure), accrual of up to 64 hours (annually) of paid sick time, paid and/or floating holidays, parental leave, short- and long-term disability insurance, tuition reimbursement, and/or health and welfare benefits. Depending on your location, you may be eligible for more detailed information related to the compensation and benefits related to this job posting. If you believe you may be entitled to such information by law, you may contact 1-781-348-7777, Monday through Friday, 7:30 a.m. – 5 p.m. ET or email AskHR@Haemonetics.com." But we need to remove boilerplate: EEO Policy Statement, contact info for compensation details? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The contact info for compensation details might be considered legal/boilerplate? It's about compensation transparency; maybe we keep it? It's not EEO, but it's a statement about contacting for more info. Might be considered boilerplate? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. This is not EEO. It's about compensation transparency contact. Might be okay to keep? However they also say "Remove ... application instructions." This is not application instructions. It's contact for compensation info. I'd keep it as part of Pay section? But the Pay section should include pay range and details. The contact info could be considered minor metadata; maybe we fold into a short
or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This contact info is minor metadata; we could fold into a short
under Pay or drop it. Safer to drop it? But we need to preserve ALL substantive information. Is that contact info substantive? It's about how to get more info; maybe not essential to the job description. I'd drop it to avoid boilerplate. Also the line "Depending on your location, you may be eligible for more detailed information related to the compensation and benefits related to this job posting." is also somewhat boilerplate. Might drop. Thus Pay section: include pay range and details about base pay, incentives, sales incentive, discretionary bonus, long-term incentive plan. Keep those. Benefits: we have list of benefits. Keep as list. Now format. We'll output:
About the role
...
Responsibilities
- ... ...