Sr Project Manager - Full Service

We need to output HTML fragment with sections: About the role? The description includes intro about Syneos Health, but we need to follow rules: use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. The posting includes: - Description (intro about Syneos Health) – could be "About the role" or maybe "About Syneos Health". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for the introductory paragraph(s) describing the role and company. - Job Responsibilities: includes "Key Responsibilities" with bullet points under subheadings: Project Leadership & Delivery, Client & Stakeholder Management, Financial & Operational Oversight, Team Leadership & Mentoring. We need to output a

  • list for duties. Should we preserve subheadings? Possibly we can include them as part of list items or separate

    with bold? The instruction: Use

    • for any list of duties/requirements/benefits. So we can create a list of responsibilities, each item can be a sentence. We could keep subheadings as part of the list item text (e.g., "Project Leadership & Delivery: Independently manage clinical studies..."). - Required Qualifications: list of qualifications. Use
      • for list. - Benefits: The posting mentions benefits: "The benefits for this position may include a company car or car allowance, Health benefits to include Medical, Dental and Vision, Company match 401k, eligibility to participate in Employee Stock Purchase Plan, Eligibility to earn commissions/bonus based on company and individual performance, and flexible paid time off (PTO) and sick time." Also mention that eligibility for paid sick time may vary depending on location. This is substantive content for Benefits section. So we should include Benefits heading with a
        • list. - Pay: The posting includes "Salary Range: The base salary range represents the anticipated low and high of the Syneos Health range for this position. Actual salary will vary based on various factors such as the candidate’s qualifications, skills, competencies, and proficiency for the role." This is somewhat vague but still mentions salary range concept. However the instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state a salary range concept but not actual numbers. It says "Salary Range: The base salary range represents the anticipated low and high of the Syneos Health range for this position. Actual salary will vary..." This is still some content about pay, albeit not specific numbers. Should we include Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state a salary range description, albeit generic. I'd argue we can include Pay section with a

          describing that salary range is based on qualifications etc. However the instruction also says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "Actual salary will vary based on various factors..." is somewhat placeholder but still conveys that salary is variable. Might be considered filler? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them (salary range). So we can include Pay section with a

          that captures that sentence. - Schedule: Not mentioned. No schedule info. So we should not include Schedule. - Skills: Not explicitly listed as a separate section; qualifications include skills. Could combine under Qualifications or Requirements. The instruction says we can have Skills section if there is real specific content. There's no explicit skills list separate from qualifications. So we may omit Skills. - Requirements: Could be same as Qualifications. The instruction lists both Requirements and Qualifications as possible headings. We need to decide which to use. The posting has "Required Qualifications". So we can use "Qualifications" heading for that. Could also have "Requirements" but we should avoid duplication. Use Qualifications. - About the role: We'll include an

          About the role

          with paragraphs describing the role and company overview. We need to remove boilerplate: lines like "We are always excited to connect with great talent. This posting is intended for a [possible] upcoming opportunity rather than a live role. By expressing your interest, you'll be added to our talent pipeline and considered should this role become available." That's application instructions? It's about talent pipeline. Might be considered boilerplate? It's not exactly application instructions but it's about expressing interest. The instruction says remove application instructions. This is more about talent pipeline; maybe we should keep? It's not essential substantive info about the job. It's more about process. I'd consider it boilerplate and remove. Also remove: "At Syneos Health, we believe in providing an environment and culture in which Our People can thrive, develop and advance. We reward and recognize our people by providing valuable benefits and a quality-of-life balance." That's somewhat benefits but we already have benefits section; could be considered boilerplate. Might keep as part of About the role? It's generic. I'd remove. Remove: "Get to know Syneos Health Over the past 5 years, we have worked with 94% of all Novel FDA Approved Drugs, 95% of EMA Authorized Products and over 200 Studies across 73,000 Sites and 675,000+ Trial patients. No matter what your role is, you’ll take the initiative and challenge the status quo with us in a highly competitive and ever-changing environment. Learn more about Syneos Health. http://www.syneoshealth.com" This is company marketing; could be considered boilerplate. Might remove. Remove: "Additional Information Tasks, duties, and responsibilities as listed in this job description are not exhaustive. The Company, at its sole discretion and with no prior notice, may assign other tasks, duties, and job responsibilities. Equivalent experience, skills, and/or education will also be considered so qualifications of incumbents may differ from those listed in the Job Description. The Company, at its sole discretion, will determine what constitutes as equivalent to the qualifications described above. Further, nothing contained herein should be construed to create an employment contract. Occasionally, required skills/experiences for jobs are expressed in brief terms. Any language contained herein is intended to fully comply with all obligations imposed by the legislation of each country in which it operates, including the implementation of the EU Equality Directive, in relation to the recruitment and employment of its employees. The Company is committed to compliance with the Americans with Disabilities Act, including the provision of reasonable accommodations, when appropriate, to assist employees or applicants to perform the essential functions of the job." This is legal boilerplate; remove. Thus we keep: - About the role: intro paragraphs about Syneos Health and the role. - Responsibilities: list of duties. - Qualifications: list of required qualifications. - Benefits: list of benefits. - Pay: paragraph about salary range. We must not repeat job title as heading. So no

          Sr Project Manager - Full Service

          . We need to output only HTML fragment. Let's craft content. About the role: combine the first two paragraphs: "Sr Project Manager - Full Service Syneos Health® is a leading fully integrated biopharmaceutical solutions organization built to accelerate customer success. We translate unique clinical, medical affairs and commercial insights into outcomes to address modern market realities. Our Clinical Development model brings the customer and the patient to the center of everything that we do. We are continuously looking for ways to simplify and streamline our work to not only make Syneos Health easier to work with, but to make us easier to work for. Whether you join us in a Functional Service Provider partnership or a Full-Service environment, you’ll collaborate with passionate problem solvers, innovating as a team to help our customers achieve their goals. We are agile and driven to accelerate the delivery of therapies, because we are passionate to change lives. Discover what our 29,000 employees, across 110 countries already know: WORK HERE MATTERS EVERYWHERE Why Syneos Health We are passionate about developing our people, through career development and progression; supportive and engaged line management; technical and therapeutic area training; peer recognition and total rewards program.We are committed to our Total Self culture – where you can authentically be yourself. Our Total Self culture is what unites us globally, and we are dedicated to taking care of our people.We are continuously building the company we all want to work for and our customers want to work with. Why? Because when we bring together diversity of thoughts, backgrounds, cultures, and perspectives – we’re able to create a place where everyone feels like they belong." That's a bit long but we can keep as prose in

          . Might be okay. Responsibilities: we need to list duties. Let's extract bullet points from the "Key Responsibilities" sections. Project Leadership & Delivery: - Independently manage clinical studies from startup through closeout. - Lead the operational and financial execution of Phase II and III clinical trials, including global and multi-protocol studies. - Act as the primary liaison between sponsors and internal project teams. - Ensure studies are conducted in accordance with GCP, ICH guidelines, regulatory requirements, and company SOPs. - Oversee project timelines, budgets, resources, risks, and deliverables. - Drive day-to-day study execution and proactively identify and resolve project issues. - Coordinate activities across functional teams and external partners to ensure successful project delivery. - Maintain accountability for project quality, financial performance, and customer satisfaction. Client & Stakeholder Management: - Build and maintain strong relationships with sponsors and key stakeholders. - Lead client meetings and provide regular project updates. - Independently prepare and present project materials for internal and external meetings. - Participate in bid defense meetings and business development activities as the designated Project Manager. - Support client growth opportunities through exceptional project delivery and relationship management. Financial & Operational Oversight: - Manage project budgets, forecasting, and financial performance. - Monitor project progress through timelines, metrics, tracking tools, and reporting systems. - Develop risk mitigation and contingency plans to ensure successful project outcomes. - Ensure inspection readiness, including oversight of Trial Master Files and project documentation. - Prepare project reports for sponsors and senior leadership. Team Leadership & Mentoring: - Lead and motivate cross-functional project teams. - Mentor and support junior Project Managers and Project Support staff. - Facilitate project-specific and therapeutic area training as needed. - Promote collaboration, communication, and accountability across teams. We'll combine into a single

          with
          • items. Qualifications: list from "Required Qualifications": - Minimum Bachelor's degree in Life Sciences, Medicine, Nursing, Pharmacy, or a related discipline, or equivalent combination of Bachelor’s degree and experience. - Clinical Research Organization (CRO) experience required. - Proven experience independently managing clinical trials from initiation through closeout. - Strong hands-on cross-functional project management experience with direct involvement in study execution. - Experience independently managing project budgets, timelines, resources, and client relationships.