Pricing Analyst II
Teleflex · St Paul, MN · 1 mo ago
Marketing$70k–$80k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID / requisition numbers as headings; we can fold minor metadata into short p or drop it. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to preserve all substantive information.
Let's parse the posting.
Key sections:
- Expected Travel: Up to 10% (maybe schedule? Travel is not schedule but could be under Schedule? Actually schedule section is for work schedule; travel is separate but we can include under Schedule? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Schedule section for travel? Travel is not schedule but maybe we can treat as Schedule? However they said include a section ONLY when posting has real, specific content for it. Travel is mentioned: "Expected Travel: Up to 10%" and later "TRAVEL REQUIRED: up to 10% as needed". So we have travel info. Could put under Schedule? Might be better to put under Schedule as travel expectation. Or we could create a separate section not listed? The instruction says use those headings as examples, but not strictly limited? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Schedule section for travel? Travel is not schedule but maybe we can treat as Schedule? However they said include a section ONLY when posting has real, specific content for it. Travel is mentioned: "Expected Travel: Up to 10%" and later "TRAVEL REQUIRED: up to 10% as needed". So we have travel info. Could put under Schedule? Might be better to put under Schedule as travel expectation. Or we could create a separate section not listed? The instruction says use those headings as examples, but not strictly limited? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. Travel could go under Schedule (maybe as "Travel: up to 10%"). Or we could omit Schedule if not present. But we have travel info, so we can include Schedule heading with travel detail.
- About Teleflex Incorporated: description of company. That could be "About the role"? Actually About the role is about the position, not company. But we have "About Teleflex Incorporated" and "Interventional Urology – The Interventional Urology business unit...". That's more about the business unit. Could be considered "About the role"? The role summary is "Position Summary". So we could have About the role: combine Position Summary and maybe company description? The instruction: do NOT repeat the job title as a heading. Use About the role for section heading. So we can put the Position Summary and maybe the company description under About the role? But the company description is not about the role. However we could still include it as part of About the role? Might be okay. But we need to preserve all substantive information. We could create a section "About the role" containing the Position Summary and maybe the description of the business unit. Or we could have separate sections: About the role (Position Summary), Responsibilities (Principal Responsibilities), Requirements (Education / Experience Requirements), Qualifications (maybe same as Requirements?), Skills (Specialized Skills / Other Requirements), Benefits, Pay, Schedule (Travel). Qualifications might be redundant with Requirements; but we can combine.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO statement, accommodation contact, trademark, copyright, etc. Also remove lines like "At Teleflex, we follow a comprehensive hiring process..." etc. Also remove "If hired, employee will be in an “at-will position”..." etc. Also remove "We do not accept unsolicited resumes..." etc. Also remove "Teleflex Incorporated is an equal opportunity employer..." etc. Also remove "If you require accommodation..." etc. Also remove trademark and copyright lines.
Also remove duplicated lines: maybe "Expected Travel: Up to 10%" appears twice; we keep once.
Now let's extract substantive content:
Company description: "As a global provider of medical technologies, Teleflex is driven by our purpose to improve the health and quality of people’s lives. Through our vision to become the most trusted partner in healthcare, we offer a diverse portfolio with solutions in the therapy areas of anesthesia, emergency medicine, interventional cardiology and radiology, surgical, vascular access, and urology. We believe that the potential of great people, purpose-driven innovation, and world-class products can shape the future direction of healthcare. Teleflex is the home of Arrow™, Barrigel™, Deknatel™, LMA™, Pilling™, QuikClot™, Rüsch™, UroLift™ and Weck™ – trusted brands united by a common sense of purpose. At Teleflex, we are empowering the future of healthcare. For more information, please visit teleflex.com."
Business unit description: "Interventional Urology – The Interventional Urology business unit of Teleflex is dedicated to developing innovative, minimally invasive and clinically effective devices that address unmet needs in the field of urology. Our flagship product, the UroLift® System, is the #1 minimally invasive procedure in the U.S. for treating an enlarged prostate, also called Benign Prostatic Hyperplasia, or BPH.* It is a proven approach that does not require heating, cutting, or destruction of prostate tissue.1 Join a dynamic, growing team that offers healthcare providers an array of medical technology solutions that make a difference in patients’ lives. U.S. 2022 estimates based on US Market Model 2022-24 (5-17-22 FINAL), which is in part based on data provided by Symphony Health PatientSource® 2018-21, as is and with no representations/warranties, including accuracy or completeness. Roehrborn, Can J Urol 2017"
Position Summary: "The Pricing Analyst II will play a vital role in supporting strategic pricing and contract management strategies within the Commercial Operations team. These executed strategies will help improve overall profitability and streamline the programs nationally. As an integral member of the Commercial Operations team, this position supports cross-functionally with Sales, Field Operations, Marketing, Legal, Finance and Shared Services to provide transactional and strategic pricing support while driving overall process improvements."
Principal Responsibilities: list of bullet points (each sentence ends with a period). We need to convert to - .
Education / Experience Requirements: "Bachelor’s Degree in Business Administration or Finance; or equivalent experience.Minimum 2 years of relevant experience with a track record of outstanding performance, preferably in a medical device company2+ years of experience in pricing, financial analysis, sales operations, revenue management, contract administration, or a related analytical role.Experience analyzing pricing, rebate, contract, sales, and profitability data to support business decisions."
Note there is some weird formatting missing spaces. We'll preserve as is but maybe add spaces for readability? Must preserve all substantive information; we can keep the text exactly but we can format nicely. Probably okay to add spaces for readability but not change meaning. We'll keep the content.
Specialized Skills / Other Requirements: list: "Advanced proficiency in Microsoft Excel, including pivot tables, lookups, financial modeling, and data analysis.Experience creating and maintaining reports, dashboards, and performance metrics.Strong attention to detail and ability to manage multiple priorities in a fast-paced environment.Excellent written and verbal communication skills, with the ability to present findings to cross-functional stakeholders.Ability to work independently while collaborating effectively with Finance, Sales, Operations, and other business partners.Experience with ERP, CRM, BI, or reporting tools such as SAP, Oracle, Salesforce, Power BI, Tableau, or similar systems."
Benefits: "The total compensation package for this position will also include benefits such as medical, prescription drug, dental and vision insurance, flexible spending accounts, participation in 401(k) savings plan, and various paid time off benefits, such as PTO, short- and long-term disability and parental leave, dependent on the position offered. Details of participation in these benefit plans will be provided if an employee receives an offer of employment."
Pay: "The pay range for this position at commencement of employment is expected to be between $70,000-$80,000 however, base pay offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience."
Schedule/Travel: "Expected Travel: Up to 10% as needed" (or "TRAVEL REQUIRED: up to 10% as needed").
We should not include the line about at-will position, EEO, etc.
Now produce HTML.
Structure:
About the role
... combine company description, business unit description, position summary? Might be too long but okay.
Better: About the role could contain Position Summary only. Company description and business unit description could be considered "About the company" but not a heading we have. Could we put them under About the role? Might be okay but could be considered filler? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we put company description under About the role, it's specific content about the company, not the role, but still substantive. It's not filler. So it's okay.
Alternatively we could omit About the role heading and instead start with Responsibilities etc. But we need to include sections only when we have content. We have content for About the role (position summary). So we will include About the role with position summary. We could also add company description there but maybe better to keep it separate? There's no heading for company overview. Could we treat it as "About the role" anyway? Might be acceptable.
Let's decide: About the role: Position Summary paragraph.
Responsibilities: Principal Responsibilities list.
Requirements: Education / Experience Requirements.
Qualifications: maybe we could combine with Requirements; but we have both Education/Experience Requirements and Specialized Skills/Other Requirements. Could treat Qualifications as Education/Experience Requirements, and Skills as Specialized Skills. Or we could have Requirements (Education/Experience) and Skills (Specialized Skills). Qualifications maybe not needed. But we have to decide which headings to use. We have content for Education/Experience Requirements and Specialized Skills/Other Requirements. So we can have two sections: Requirements (Education/Experience) and Skills (Specialized Skills). Qualifications could be omitted if no distinct content. Pay, Benefits, Schedule.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
Check if any content for Qualifications besides Education/Experience? Not really. So we omit Qualifications.
Now format.
We need to ensure we don't include any boilerplate like "U.S. 2022 estimates based on US Market Model..." that is part of business unit description; we keep it.
Now produce HTML.
We'll wrap each section in
then content.
For lists: Responsibilities: each sentence as
- . We need to split the responsibilities sentences.
Let's extract responsibilities sentences:
1. Analyze financial and operational metrics, including sales trends and forecasts, to identify trends, opportunities, and risks and support data-driven business decisions.
2. Process, maintain, and track pricing quotes, proposals, customer agreements, and contracts, ensuring accuracy and compliance with established pricing policies and approval processes.
3. Triage, coordinate, and help resolve contract, pricing, rebate, and billing-related issues across internal stakeholders, systems, and customers.
4. Develop, maintain, and distribute pricing, contracting, and rebate reports to support Commercial Operations, Finance, and Sales.
5. Calculate customer rebates in accordance with contractual agreements, approved pricing programs, and established guidelines.
6. Partner cross-functionally to support accurate rebate accruals, allocations, payments, and reconciliations, including the collection, documentation, and validation of customer banking information required for rebate payments.
7. Support the administration and tracking of customer contractual commitments and rebate programs in partnership with Finance, Accounts Payable, Global Procurement, Data Management Operations, and other stakeholders.
8. Analyze customer pricing using internal and external data sources to validate pricing parity, contract duration, effectiveness, and accuracy in accordance with customer agreements and established guidelines.
9. Develop and maintain financial models to evaluate pricing opportunities, contract scenarios, new product launches, rebate structures, projected customer spend, and potential revenue
- .
Education / Experience Requirements: "Bachelor’s Degree in Business Administration or Finance; or equivalent experience.Minimum 2 years of relevant experience with a track record of outstanding performance, preferably in a medical device company2+ years of experience in pricing, financial analysis, sales operations, revenue management, contract administration, or a related analytical role.Experience analyzing pricing, rebate, contract, sales, and profitability data to support business decisions."
Note there is some weird formatting missing spaces. We'll preserve as is but maybe add spaces for readability? Must preserve all substantive information; we can keep the text exactly but we can format nicely. Probably okay to add spaces for readability but not change meaning. We'll keep the content.
Specialized Skills / Other Requirements: list: "Advanced proficiency in Microsoft Excel, including pivot tables, lookups, financial modeling, and data analysis.Experience creating and maintaining reports, dashboards, and performance metrics.Strong attention to detail and ability to manage multiple priorities in a fast-paced environment.Excellent written and verbal communication skills, with the ability to present findings to cross-functional stakeholders.Ability to work independently while collaborating effectively with Finance, Sales, Operations, and other business partners.Experience with ERP, CRM, BI, or reporting tools such as SAP, Oracle, Salesforce, Power BI, Tableau, or similar systems."
Benefits: "The total compensation package for this position will also include benefits such as medical, prescription drug, dental and vision insurance, flexible spending accounts, participation in 401(k) savings plan, and various paid time off benefits, such as PTO, short- and long-term disability and parental leave, dependent on the position offered. Details of participation in these benefit plans will be provided if an employee receives an offer of employment."
Pay: "The pay range for this position at commencement of employment is expected to be between $70,000-$80,000 however, base pay offered may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience."
Schedule/Travel: "Expected Travel: Up to 10% as needed" (or "TRAVEL REQUIRED: up to 10% as needed").
We should not include the line about at-will position, EEO, etc.
Now produce HTML.
Structure:
About the role
... combine company description, business unit description, position summary? Might be too long but okay. Better: About the role could contain Position Summary only. Company description and business unit description could be considered "About the company" but not a heading we have. Could we put them under About the role? Might be okay but could be considered filler? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we put company description under About the role, it's specific content about the company, not the role, but still substantive. It's not filler. So it's okay. Alternatively we could omit About the role heading and instead start with Responsibilities etc. But we need to include sections only when we have content. We have content for About the role (position summary). So we will include About the role with position summary. We could also add company description there but maybe better to keep it separate? There's no heading for company overview. Could we treat it as "About the role" anyway? Might be acceptable. Let's decide: About the role: Position Summary paragraph. Responsibilities: Principal Responsibilities list. Requirements: Education / Experience Requirements. Qualifications: maybe we could combine with Requirements; but we have both Education/Experience Requirements and Specialized Skills/Other Requirements. Could treat Qualifications as Education/Experience Requirements, and Skills as Specialized Skills. Or we could have Requirements (Education/Experience) and Skills (Specialized Skills). Qualifications maybe not needed. But we have to decide which headings to use. We have content for Education/Experience Requirements and Specialized Skills/Other Requirements. So we can have two sections: Requirements (Education/Experience) and Skills (Specialized Skills). Qualifications could be omitted if no distinct content. Pay, Benefits, Schedule. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Check if any content for Qualifications besides Education/Experience? Not really. So we omit Qualifications. Now format. We need to ensure we don't include any boilerplate like "U.S. 2022 estimates based on US Market Model..." that is part of business unit description; we keep it. Now produce HTML. We'll wrap each section in
then content. For lists: Responsibilities: each sentence as
- . We need to split the responsibilities sentences. Let's extract responsibilities sentences: 1. Analyze financial and operational metrics, including sales trends and forecasts, to identify trends, opportunities, and risks and support data-driven business decisions. 2. Process, maintain, and track pricing quotes, proposals, customer agreements, and contracts, ensuring accuracy and compliance with established pricing policies and approval processes. 3. Triage, coordinate, and help resolve contract, pricing, rebate, and billing-related issues across internal stakeholders, systems, and customers. 4. Develop, maintain, and distribute pricing, contracting, and rebate reports to support Commercial Operations, Finance, and Sales. 5. Calculate customer rebates in accordance with contractual agreements, approved pricing programs, and established guidelines. 6. Partner cross-functionally to support accurate rebate accruals, allocations, payments, and reconciliations, including the collection, documentation, and validation of customer banking information required for rebate payments. 7. Support the administration and tracking of customer contractual commitments and rebate programs in partnership with Finance, Accounts Payable, Global Procurement, Data Management Operations, and other stakeholders. 8. Analyze customer pricing using internal and external data sources to validate pricing parity, contract duration, effectiveness, and accuracy in accordance with customer agreements and established guidelines. 9. Develop and maintain financial models to evaluate pricing opportunities, contract scenarios, new product launches, rebate structures, projected customer spend, and potential revenue