IT Enablement Coordinator
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info; not invent or summarize away detail.
We need to remove duplicated lines. There's some duplication: "Excellent written and verbal communication skills." appears multiple times. We should keep but maybe deduplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't explicitly say to deduplicate, but "duplicated lines" should be removed. So we should remove duplicate sentences.
We need to identify duplicate lines in the text.
Let's extract the content and see duplicates.
I'll copy the relevant parts.
Intro paragraph (first big paragraph) - we can treat as About the role.
Then "Specific Duties And Responsibilities" - list of duties.
Then "Position Qualifications - Required" - list.
Then "Position Qualifications - Preferred" - list.
Then "Working Conditions" - list.
Then "Base Pay Range Per Hour: $38.00 - 49.00 Individual compensation will vary based on factors such as qualifications, skill level, competencies, work location and shift, and will increase over time based on meeting performance and business needs."
Then "What We Offer" - benefits paragraph.
Then company description (maybe not needed? It's substantive about company; could be part of About the role? Might be considered boilerplate? It's about the company, not the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not explicitly listed to remove, but it's not about the role. However it's substantive info about the company; maybe we keep as part of About the role? The instruction: "Preserve ALL substantive information". So we should keep it unless it's considered boilerplate. It's not navigation/legal/EEO etc. So we keep.
Then EEO statement etc - remove.
Now we need to structure.
Sections:
- About the role: could combine intro paragraph + company description? Might be too much. But we can have About the role as the introductory paragraph describing role responsibilities (the first paragraph). Then Responsibilities as the list under Specific Duties And Responsibilities. Then Requirements as required qualifications. Then Qualifications as preferred qualifications? Or we could have Skills section for skills/competencies. But we have both required and preferred qualifications; we could put Required under Requirements, Preferred under Qualifications. Skills maybe combine communication, analytical etc. But we already have those in qualifications. To avoid thin sections, we could merge Required and Preferred into Qualifications with subheadings? But instruction: use headings only for those specific section names. We cannot create custom headings. So we must use only those headings. We can decide to put required qualifications under Requirements, preferred under Qualifications, and maybe skills under Skills (but we might not have distinct skills list separate from qualifications). However we have many skill-like items: "Excellent written and verbal communication skills.", "Ability to think and react in a high-energy, fast-paced environment...", "High level of proficiency with Microsoft Office products...", "Excellent interpersonal & problem-solving skills", "Strong oral, written, and interpersonal communication skills", "High degree of accuracy and attention to detail", "Proficiency with MS Word, Excel, and PowerPoint", "Excellent organizational skills with ability to prioritize assignments while handling various projects simultaneously". Some duplicates.
We could create a Skills section containing those skill statements. Then Requirements could be education/experience basics: Bachelor's degree, 3+ years experience, vendor management, budget experience, etc. Qualifications could be preferred qualifications: purchasing experience, IT procurement, medical device industry, etc. Working Conditions could be its own section? Not in the list of allowed headings; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Working Conditions is not allowed, so we must either drop it or fold into another section (maybe Qualifications or Skills?). The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid using other headings not listed? It says: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but likely the only allowed headings. Safer to stick to those. So we need to map Working Conditions content into one of those sections, perhaps under Qualifications or Skills? But Working Conditions is about physical demands, environment, travel, etc. Could be part of Qualifications? Not really. Could be part of Requirements? Not exactly. Could be part of Skills? No.
Maybe we can treat Working Conditions as part of Qualifications (since it's about candidate attributes). Or we could omit it? But we must preserve ALL substantive information. So we need to include it somewhere. The best fit is Qualifications (maybe as "Preferred Qualifications"?). But it's not a qualification; it's working condition. However we could put it under Requirements as "Must be able to..." which are requirements. Indeed many of those are requirements: "Willingness and ability to work on site.", "May have business travel from 0% - 5%", "Requires some lifting and moving of up to 15 pounds", etc. Those are job requirements. So we can put them under Requirements.
Thus Requirements will include education/experience plus working conditions.
Qualifications will be preferred qualifications.
Skills will be skill/competency statements.
Now we need to deduplicate duplicate lines.
Let's extract each piece.
First, intro paragraph (About the role):
"As an IT Enablement Coordinator, you will be responsible for coordinating and enhancing the user experience for IT employees - Onshore & Offshore. You will work closely with HR to supporting the IT new hire onboarding experience. You will be responsible for supporting and tracking overall IT internal spend and forecast, and will be the liaison between IT, Finance, and HR to ensure the accurate headcount and spend forecast is communicated and managed. Work closely with various IT leaders to provide help and guidance on their spending and vendor engagement program. Support and coordinate IT new employee trainings. Support strategic alignment process with Penumbra business teams. Support activities to improve overall user experience working with various IT groups. You will also be assisting in managing and coordinating the relationship between key strategic vendors and IT business partners, understanding the complete breadth of professional services provided by vendors and current support services for each IT group. Responsible for understanding the types of services being provided to Penumbra IT, oversee work product of each vendor account, including projects, project cost, SOW management, SLAs, executive reporting and serve as point person for Penumbra IT VMO and Vendors. Partners with key stakeholders across the IT Org to ensure that financial, performance, risk and compliance requirements are being met as per Penumbra Supplier Quality, Legal, Finance requirements."
We should keep as is, maybe split into sentences but keep as paragraph.
Now Specific Duties And Responsibilities list (I'll extract each bullet-like sentence):
- Partner with HR to assist in the coordination and enhancement of the IT new hire onboarding process; making sure new hires have all the required information, assets, access, cube allocated when they are onsite 1st day of their employment start.
- Manage basic training required for IT new hires - generic as well as specific to their job; introducing them to the rest of the team, send out a welcome email to new hires and rest of the IT team communicating the start of new employees.
- Organize a welcome lunch with the reporting manager and other senior members of the team.
- Assist in the coordination and vendor management to enhance the IT vendor relationship management program scalable to support Penumbra IT vendors / Partners working with Penumbra IT members on various projects or on-going operational support.
- Build effective relationships with suppliers/vendors and work to understand the service level agreements to manage supplier performance proactively to ensure to drive process improvements that will result in IT cost reduction, productivity, and service level enhancements.
- Establish vendor alliances through communication and information sharing.
- Ensure vendors remain focused on our mutual goals, plans, and investments to meet our growing needs.
- Ensure service levels are maintained, schedules are met, and formal reporting and invoicing are timely and accurate.
- Partner with the senior managers across IT to maintain the IT budget, forecast and identify opportunities for cost savings.
- Partner with senior management to assist in the negotiation of new and yearly software and hardware contracts.
- Support and plan IT employee trainings as part of the onboarding of new IT team members.
- Plan and manage IT meetings like - All Hands meetings, Strategy & Planning, Alignment meetings with other organizations within Penumbra.
- Track and manage IT headcount growth and hiring working with HR partner for IT.
- Support IT team in activities related to improving user experience for different employee profiles like manufacturing and non-manufacturing, office employees.
- Adhere to the Company's Quality Management System (QMS) as well as domestic and global quality system regulations, standards, and procedures.
- Understand relevant security, privacy and compliance principles and adhere to the regulations, standards, and procedures that are applicable to the Company.
- Ensure other members of the department follow the QMS, regulations, standards, and procedures.
- Perform other work-related duties as assigned
for prose. We need to preserve all substantive info; not invent or summarize away detail. We need to remove duplicated lines. There's some duplication: "Excellent written and verbal communication skills." appears multiple times. We should keep but maybe deduplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't explicitly say to deduplicate, but "duplicated lines" should be removed. So we should remove duplicate sentences. We need to identify duplicate lines in the text. Let's extract the content and see duplicates. I'll copy the relevant parts. Intro paragraph (first big paragraph) - we can treat as About the role. Then "Specific Duties And Responsibilities" - list of duties. Then "Position Qualifications - Required" - list. Then "Position Qualifications - Preferred" - list. Then "Working Conditions" - list. Then "Base Pay Range Per Hour: $38.00 - 49.00 Individual compensation will vary based on factors such as qualifications, skill level, competencies, work location and shift, and will increase over time based on meeting performance and business needs." Then "What We Offer" - benefits paragraph. Then company description (maybe not needed? It's substantive about company; could be part of About the role? Might be considered boilerplate? It's about the company, not the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not explicitly listed to remove, but it's not about the role. However it's substantive info about the company; maybe we keep as part of About the role? The instruction: "Preserve ALL substantive information". So we should keep it unless it's considered boilerplate. It's not navigation/legal/EEO etc. So we keep. Then EEO statement etc - remove. Now we need to structure. Sections: - About the role: could combine intro paragraph + company description? Might be too much. But we can have About the role as the introductory paragraph describing role responsibilities (the first paragraph). Then Responsibilities as the list under Specific Duties And Responsibilities. Then Requirements as required qualifications. Then Qualifications as preferred qualifications? Or we could have Skills section for skills/competencies. But we have both required and preferred qualifications; we could put Required under Requirements, Preferred under Qualifications. Skills maybe combine communication, analytical etc. But we already have those in qualifications. To avoid thin sections, we could merge Required and Preferred into Qualifications with subheadings? But instruction: use headings only for those specific section names. We cannot create custom headings. So we must use only those headings. We can decide to put required qualifications under Requirements, preferred under Qualifications, and maybe skills under Skills (but we might not have distinct skills list separate from qualifications). However we have many skill-like items: "Excellent written and verbal communication skills.", "Ability to think and react in a high-energy, fast-paced environment...", "High level of proficiency with Microsoft Office products...", "Excellent interpersonal & problem-solving skills", "Strong oral, written, and interpersonal communication skills", "High degree of accuracy and attention to detail", "Proficiency with MS Word, Excel, and PowerPoint", "Excellent organizational skills with ability to prioritize assignments while handling various projects simultaneously". Some duplicates. We could create a Skills section containing those skill statements. Then Requirements could be education/experience basics: Bachelor's degree, 3+ years experience, vendor management, budget experience, etc. Qualifications could be preferred qualifications: purchasing experience, IT procurement, medical device industry, etc. Working Conditions could be its own section? Not in the list of allowed headings; allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Working Conditions is not allowed, so we must either drop it or fold into another section (maybe Qualifications or Skills?). The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid using other headings not listed? It says: "use