(Sr) Project Manager, Feasibility Site Activation
ICON plc · Blue Bell, PA · 3 wk ago
HybridFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes two roles: Project Manager, FSA and Senior Project Manager, FSA. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". But we have two titles. Likely we need to treat each as separate job posting? The user gave combined text with two titles. We need to reformat into clean semantic HTML. Probably we need to output sections for each role? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to create sections like About the role, Responsibilities, Requirements, etc. But we have two roles; maybe we need to output two separate blocks each with its own headings? The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". So we should not put the title as heading. But we need to differentiate the two roles? Possibly we can wrap each role in a with an for the title? But they said not to repeat job title as heading. However the page already shows it, meaning the title is already displayed elsewhere, so we shouldn't duplicate it. But we still need to differentiate content for each role. Could use for role title? Might violate. Perhaps we can just output one combined posting? But there are two distinct roles with different responsibilities. The instruction: "Prefer a few substantive sections over many thin ones." Could combine? But they are separate roles; maybe we should output two separate blocks each with its own headings (About the role, Responsibilities, Requirements, etc.) but not include the job title heading. The page already shows the title, so we can omit it.
Thus we will produce something like:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to create sections like About the role, Responsibilities, Requirements, etc. But we have two roles; maybe we need to output two separate blocks each with its own headings? The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". So we should not put the title as heading. But we need to differentiate the two roles? Possibly we can wrap each role in a with an for the title? But they said not to repeat job title as heading. However the page already shows it, meaning the title is already displayed elsewhere, so we shouldn't duplicate it. But we still need to differentiate content for each role. Could use for role title? Might violate. Perhaps we can just output one combined posting? But there are two distinct roles with different responsibilities. The instruction: "Prefer a few substantive sections over many thin ones." Could combine? But they are separate roles; maybe we should output two separate blocks each with its own headings (About the role, Responsibilities, Requirements, etc.) but not include the job title heading. The page already shows the title, so we can omit it.
Thus we will produce something like:
About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
About the role
As a Project Manager, Feasibility and Site Activation (FSA) at ICON, you will be responsible for planning and manage Feasibility and Site Activation (FSA) activities for assigned clinical studies. You will oversee site start-up and activation workstreams, ensuring deliverables meet quality and timeline expectations.
Responsibilities
- Developing and managing FSA project plans, timelines, and deliverables for assigned studies.
- Coordinating feasibility assessments, country and site recommendations, and start-up strategies in collaboration with functional experts.
- Overseeing essential document collection, ethics and regulatory submissions, and site activation milestones.
- Tracking progress against timelines and KPIs, proactively identifying risks and implementing mitigation plans.
- Serving as the primary FSA contact for internal teams and customers for study-level start-up matters.
- Contributing to process improvement and best practice sharing within the FSA project management team.