Sr Director, Enterprise Program Management
Insulet Corporation · New Jersey, United States · 1 mo ago
Information Technology$249k–$373k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes "Job Summary", "Position Overview", "Responsibilities", "Education And Experience", "Physical Requirements", "Additional Information" (which includes Compensation & Benefits, Application Details, company description). We must not repeat job title as heading. Use h3 for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should map content to appropriate headings. The instruction: use . Let's parse:
"Segment Team: Participates as a key team member and strategic partner within the segment leadership. Collaborates to align EPMO activities with strategic goals and initiates and leads cross-functional development programs and sustaining activities for all relevant products."
That's two sentences; could be two li.
"Functional Teams: Participates across all functional area VP’s and Management staff in establishing overall product development program goals, scope, resources, and the plans for execution."
One li.
"Governance: Leads the governing and oversight of Insulet product development for the business segment through the Portfolio Decision Team ensuring program status are clearly communicated and issues/risk are escalated and mitigated cross-functionally."
One li.
"EPMO: Provides leadership to the Enterprise Program Management Office to help ensure that Program Managers and cross-functional initiatives and efforts align with overall business strategies in order to achieve successful outcomes per established goals and objectives."
One li.
"Player/Coach: Assists in directing program teams responsible for the development of all approved programs and products with accountability for delivery success as defined through scope, schedule, and resources. Prepared to lead from above or from along-side program teams to ensure timely delivery and execution."
Two li.
"Strategic Program Execution: when determined, perform as the overall program leader for large, strategic programs driving plans and execution to ensure products are delivered as defined, on time, and within budgets."
One li.
"People management: Hire, manage, and mentor staff for individual development and leadership in cross-functional product development programs."
One li.
"Specific Focus Area: Provides an unbiased, data-drive perspective of program status and risks to ensure Insulet is objectively managing product development."
One li.
"Performs additional duties as required."
One li.
Now Education And Experience: Minimum Requirements and Preferred Requirements.
We need to split into Requirements and Qualifications maybe. Use headings Requirements and Qualifications. The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements (minimum) and Qualifications (preferred). Skills maybe from preferred but we could also include under Qualifications. But we have a separate Skills heading optional; we could include skills from preferred: Ability to influence..., Effective collaborator..., Excellent verbal..., Ability to anticipate..., Ability to organize..., Ability to effectively handle multiple efforts simultaneously. Those are skills. So we could have Skills section.
Thus:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings? Probably we should use those headings where applicable. For example, we have a job summary (could be About the role). Responsibilities section present. Requirements: we have Education And Experience (minimum and preferred). Could map to Requirements and Qualifications. Skills maybe part of Requirements. Benefits and Pay: we have Compensation & Benefits section with salary range and benefits. Schedule: we have Physical Requirements includes travel; maybe schedule not present. We should only include sections when posting has real specific content. So we need to include About the role (job summary + position overview). Responsibilities (list). Requirements (education/experience). Qualifications (maybe preferred). Skills (maybe from preferred). Benefits (benefits list). Pay (salary range). Schedule? Not present; we have travel requirement but not schedule like full-time/part-time. Could treat travel as part of Physical Requirements but not schedule. Since schedule not specified, we should not include Schedule heading. Also we should not include placeholder like "commensurate with experience". We have actual salary range, so Pay section is valid. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At end there is EEO statement and "Know Your Rights". Remove that. Also remove application details like "This job posting will remain open..." and "To apply..." etc. Also remove company description? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The company description about Insulet may be considered substantive? It's not directly about the role but maybe considered boilerplate? It's about the company; could be considered extra but not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not listed as to remove, but it's not about the role. However "Preserve ALL substantive information" suggests we keep it unless it's boilerplate. The company description is substantive about the company; but maybe it's considered boilerplate? Usually job postings include company overview; could be considered substantive. I'd keep it as a paragraph maybe under a heading like "About Insulet" but we don't have a heading for that. Could just include as
after other sections. However the instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely they expect only those headings. So we should not add extra headings like About Insulet. We could incorporate company description into About the role paragraph. That would be okay. Thus structure:
About the role
Job Summary ... Position Overview ... (combined)
Responsibilities
- ... each responsibility as list items.
Requirements
Minimum Requirements: Bachelor’s degree in related field; 12+ years of related experience in product development within related field; Proven record of product development and implementation in electro-mechanic and/or software products; Experience with managing suppliers, external partners, and internal staff (at all levels); Experience in the medical device industry with knowledge related to the FDA design control process.
We could also make a list but it's okay as prose.Qualifications
Preferred Requirements: Master’s or PhD degree in related field; 15+ years of related experience in product development within related field.
Skills
- Ability to influence and manage others both as direct reports, and matrix reports
- Effective collaborator with strong IQ/EQ
- Excellent verbal, written, and interpersonal communication skills
- Ability to anticipate (“see around corners”) major challenges for hardware and software product development
- Ability to organize and judge (triage) priorities
- Ability to effectively handle multiple efforts simultaneously
Pay
For U.S.-based positions only, the annual base salary range for this role is $248,500.00 - $372,700.00. This position may also be eligible for incentive compensation.
Benefits
- Medical, dental, and vision insurance
- 401(k) with company match
- Paid time off (PTO)
- Additional employee wellness programs