Senior Manager, Clinical Operations - GI
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We need to parse the posting.
We have:
- Intro about company (Iterative Health ...) maybe "About the role" or "About the company"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Schedule not present (no schedule details). So we omit Schedule.
We must not repeat job title as heading. The job title is "Senior Manager, Clinical Operations- GI". Not to be used as heading.
We must not include Job ID/requisition numbers.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes an accommodation line at end: "If you require any accommodations..." That's likely EEO/accommodation boilerplate; we should remove it. Also the line about diversity and inclusive culture maybe considered EEO? It's about diversity but could be considered part of company description; but it's more of EEO statement. The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove the paragraph about diversity and accommodations. Also the line "At Iterative Health, we’re actively working towards creating an environment that is representative of the diversity..." and the accommodation request line. Remove those.
Also remove any duplicated lines.
Now we need to extract sections.
Let's parse the posting:
First paragraph: "Iterative Health is a healthcare technology and services company powering the acceleration of clinical research to transform patient outcomes.We built a leading performance-driven network of 100+ sites across the US, Europe, India, and Australia, conducting research directly in the communities where care is delivered across gastrointestinal, hepatology, obesity, and cardiology. By combining deep clinical trial expertise with cutting-edge AI, we connect sponsors' scientific ambitions with high-performing research teams that expedite and expand access to novel therapeutics for patients in need. Today, Iterative Health is headquartered in Cambridge, Massachusetts, and New York City with 250+ employees world-wide."
That's company overview. Could go under "About the role" maybe? Actually "About the role" would be description of the role. But we have a separate "As the Senior Manager, Clinical Operations- GI at Iterative Health you will serve as a strategic advisor..." That's role description. So we could put that under "About the role". The earlier company overview could be part of "About the role" as context, but maybe better to put under "About the role" a summary of role and company. However we must not invent content; we can include that company overview as part of About the role.
Next: "As Iterative Health continues to expand its Site Network and partnerships with sponsors and CROs, operational excellence has become a critical differentiator. This role sits at the center of those relationships, helping ensure studies are launched efficiently, sites are set up for success, and sponsors receive the insights and partnership needed to achieve their clinical development goals. In particular, this role will own and scale the site activation process across the organization. This role is responsible for driving on-time site activations within SLAs, proactively identifying and resolving blockers, and improving activation workflows to increase speed, predictability, and efficiency.This is a highly visible, customer-facing role with the opportunity to influence study strategy, shape operational best practices, and drive measurable impact across a growing portfolio of clinical trials."
That's more responsibilities.
Then a heading: "Where You’ll Drive Impact Study Activation Ownership & Execution" then bullet list (though not using markdown bullet but lines). Then "Sponsor & CRO Partnership", "Study Performance & Operational Excellence". Those are subheadings within responsibilities. We can combine into a Responsibilities section with - items.
Then "What You Bring to the Team" includes requirements: Bachelor's degree..., 8+ years experience..., etc. Then "Preferred Qualifications". Those can go under Requirements and Qualifications sections.
Then "How We Work" is culture; could be part of About the role or maybe separate but not a standard heading; we could incorporate into About the role or maybe omit as not matching headings. The instruction: prefer a few substantive sections over many thin ones. So we could include How We Work as part of About the role or maybe as a separate section like "Culture" but not in allowed headings. Since allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put How We Work under About the role or maybe under Skills? Not appropriate. Better to incorporate into About the role.
Then "Benefits That Support You" is benefits.
Then "New York pay range: $140,000 USD - $165,000 USD" is pay.
No schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to decide what goes into Skills. The posting includes skills like "Strong analytical, communication, and stakeholder management skills.", "Comfort adopting and leveraging new technologies and operational tools.", "Willingness to travel up to 30%." Also maybe "Experience with CTMS platforms, with RealTime CTMS strongly preferred." That could be skills or qualifications. We'll treat as Skills.
Requirements: Bachelor's degree or equivalent combination of education and experience. 8+ years of experience supporting Phase II-IV sponsor-funded clinical trials. Deep understanding of clinical trial operations, including study startup, feasibility, regulatory processes, protocol execution, and GCP requirements. Experience working directly with sponsors, CROs, investigative sites, and cross-functional stakeholders. Demonstrated ability to manage multiple priorities, navigate ambiguity, and drive projects to successful completion. Strong analytical, communication, and stakeholder management skills. Comfort adopting and leveraging new technologies and operational tools. Willingness to travel up to 30%.
Preferred Qualifications: Experience in GI clinical research. Prior project or program management experience. 5+ years of experience as a Clinical Research Associate (CRA) or Clinical Research Coordinator (CRC), or 3+ years leading clinical operations teams. Experience with CTMS platforms, with RealTime CTMS strongly preferred. Experience working in a high-growth or startup environment. Experience presenting to sponsors, CRO leadership, and executive stakeholders.
We could split: Requirements = mandatory; Qualifications = preferred.
Skills: maybe we can list specific skills like analytical, communication, stakeholder management, technology adoption, travel willingness. But those are already in requirements. Could also include "Experience with CTMS platforms" as skill. But to avoid duplication, we could put those under Skills. However we must preserve all substantive information; duplication is okay if we keep it but we should avoid repeating same content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should avoid unnecessary duplication. Better to allocate each piece to appropriate section without duplication.
Let's design:
About the role: includes company overview and role description summary (the first two paragraphs plus the "As Iterative Health continues..." paragraph plus the "This is a highly visible..." paragraph). Could also include the "Where You’ll Drive Impact" heading as part of responsibilities.
Responsibilities: list items from the three sub-sections: Study Activation Ownership & Execution, Sponsor & CRO Partnership, Study Performance & Operational Excellence. Also maybe the "Performs related duties as requested" line (but that's generic; we could include but it's boilerplate? Might be okay). We'll include.
Requirements: Bachelor's degree..., 8+ years experience..., deep understanding..., experience working directly..., demonstrated ability..., strong analytical..., comfort adopting..., willingness to travel...
Qualifications: Preferred qualifications list.
Skills: maybe we can list "Strong analytical, communication, and stakeholder management skills." but that's already in requirements. Could also list "Experience with CTMS platforms, with RealTime CTMS strongly preferred." but that's in qualifications. Could list "Experience presenting to sponsors, CRO leadership, and executive stakeholders." also in qualifications. Might be better to not have a Skills section if it duplicates. But we need to include a Skills section only if there is real specific content not covered elsewhere. The posting does not have a separate skills list; skills are embedded in requirements and qualifications. So we could omit Skills section. However the instruction says we can use Skills heading if there is content. If we omit, that's fine.
Benefits: list all benefits.
Pay: New York pay range.
Now we need to format as HTML fragment: use
for each section heading, then content:
for prose,
- for lists.
We must not include or tags.
We must not include markdown code fences.
Let's craft.
First, About the role:
We need to combine company overview and role description.
Prose: maybe two paragraphs.
We'll write:
Iterative Health is a healthcare technology and services company powering the acceleration of clinical research to transform patient outcomes. We built a leading performance‑driven network of 100+ sites across the US, Europe, India, and Australia, conducting research directly in the communities where care is delivered across gastrointestinal, hepatology, obesity, and cardiology. By combining deep clinical trial expertise with cutting‑edge AI, we connect sponsors' scientific ambitions with high‑performing research teams that expedite and expand access to novel therapeutics for patients in need. Today, Iterative Health is headquartered in Cambridge, Massachusetts, and New York City with 250+ employees worldwide.
As the Senior Manager, Clinical Operations‑GI at Iterative Health you will serve as a strategic advisor to sponsors, CROs, and research sites, translating operational challenges into scalable solutions that improve study execution, accelerate activation timelines, and drive patient recruitment performance. By combining deep clinical research expertise with a consultative approach, this individual will help strengthen sponsor relationships, elevate site performance across the network, and contribute directly to Iterative Health's mission of bringing innovative therapies to patients faster.
As Iterative Health continues to expand its Site Network and partnerships with sponsors and CROs, operational excellence has become a critical differentiator. This role sits at the center of those relationships, helping ensure studies are launched efficiently, sites are set up for success, and sponsors receive the insights and partnership needed to achieve their clinical development goals. In particular, this role will own and scale the site activation process across the organization. This role is responsible for driving on‑time site activations within SLAs, proactively identifying and resolving blockers, and improving activation workflows to increase speed, predictability, and efficiency. This is a highly visible, customer‑facing role with the opportunity to influence study strategy, shape operational best practices, and drive measurable impact across a growing portfolio of clinical trials.
That seems good.
Now Responsibilities: we need to list items.
We'll create - for each bullet.
From "Where You’ll Drive Impact Study Activation Ownership & Execution":
- Own the end-to-end site activations, managing timelines, dependencies, and risks across multiple concurrent sites and trials
- Help teams prioritize tasks and ensure milestones are met within defined SLAs
- Maintain activation plans, status tracking, and documentation, escalating risks and delays proactively
From "Sponsor & CRO Partnership":
- Serve as the primary operational partner to sponsors, CROs, and sites throughout the trial lifecycle
- Lead and support sponsor, CRO, and partner meetings by providing clinical operations expertise, actionable insights, and strategic recommendations
- Build strong relationships with key stakeholders and ensure alignment on study goals, performance metrics, and operational priorities
- Proactively communicate study risks, mitigation plans, and escalation strategies
- Facilitate educational sessions, webinars, and
- items.
Then "What You Bring to the Team" includes requirements: Bachelor's degree..., 8+ years experience..., etc. Then "Preferred Qualifications". Those can go under Requirements and Qualifications sections.
Then "How We Work" is culture; could be part of About the role or maybe separate but not a standard heading; we could incorporate into About the role or maybe omit as not matching headings. The instruction: prefer a few substantive sections over many thin ones. So we could include How We Work as part of About the role or maybe as a separate section like "Culture" but not in allowed headings. Since allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put How We Work under About the role or maybe under Skills? Not appropriate. Better to incorporate into About the role.
Then "Benefits That Support You" is benefits.
Then "New York pay range: $140,000 USD - $165,000 USD" is pay.
No schedule.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to decide what goes into Skills. The posting includes skills like "Strong analytical, communication, and stakeholder management skills.", "Comfort adopting and leveraging new technologies and operational tools.", "Willingness to travel up to 30%." Also maybe "Experience with CTMS platforms, with RealTime CTMS strongly preferred." That could be skills or qualifications. We'll treat as Skills.
Requirements: Bachelor's degree or equivalent combination of education and experience. 8+ years of experience supporting Phase II-IV sponsor-funded clinical trials. Deep understanding of clinical trial operations, including study startup, feasibility, regulatory processes, protocol execution, and GCP requirements. Experience working directly with sponsors, CROs, investigative sites, and cross-functional stakeholders. Demonstrated ability to manage multiple priorities, navigate ambiguity, and drive projects to successful completion. Strong analytical, communication, and stakeholder management skills. Comfort adopting and leveraging new technologies and operational tools. Willingness to travel up to 30%.
Preferred Qualifications: Experience in GI clinical research. Prior project or program management experience. 5+ years of experience as a Clinical Research Associate (CRA) or Clinical Research Coordinator (CRC), or 3+ years leading clinical operations teams. Experience with CTMS platforms, with RealTime CTMS strongly preferred. Experience working in a high-growth or startup environment. Experience presenting to sponsors, CRO leadership, and executive stakeholders.
We could split: Requirements = mandatory; Qualifications = preferred.
Skills: maybe we can list specific skills like analytical, communication, stakeholder management, technology adoption, travel willingness. But those are already in requirements. Could also include "Experience with CTMS platforms" as skill. But to avoid duplication, we could put those under Skills. However we must preserve all substantive information; duplication is okay if we keep it but we should avoid repeating same content? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should avoid unnecessary duplication. Better to allocate each piece to appropriate section without duplication.
Let's design:
About the role: includes company overview and role description summary (the first two paragraphs plus the "As Iterative Health continues..." paragraph plus the "This is a highly visible..." paragraph). Could also include the "Where You’ll Drive Impact" heading as part of responsibilities.
Responsibilities: list items from the three sub-sections: Study Activation Ownership & Execution, Sponsor & CRO Partnership, Study Performance & Operational Excellence. Also maybe the "Performs related duties as requested" line (but that's generic; we could include but it's boilerplate? Might be okay). We'll include.
Requirements: Bachelor's degree..., 8+ years experience..., deep understanding..., experience working directly..., demonstrated ability..., strong analytical..., comfort adopting..., willingness to travel...
Qualifications: Preferred qualifications list.
Skills: maybe we can list "Strong analytical, communication, and stakeholder management skills." but that's already in requirements. Could also list "Experience with CTMS platforms, with RealTime CTMS strongly preferred." but that's in qualifications. Could list "Experience presenting to sponsors, CRO leadership, and executive stakeholders." also in qualifications. Might be better to not have a Skills section if it duplicates. But we need to include a Skills section only if there is real specific content not covered elsewhere. The posting does not have a separate skills list; skills are embedded in requirements and qualifications. So we could omit Skills section. However the instruction says we can use Skills heading if there is content. If we omit, that's fine.
Benefits: list all benefits.
Pay: New York pay range.
Now we need to format as HTML fragment: use
for each section heading, then content:
for prose,
- for lists.
We must not include or tags.
We must not include markdown code fences.
Let's craft.
First, About the role:
We need to combine company overview and role description.
Prose: maybe two paragraphs.
We'll write:
Iterative Health is a healthcare technology and services company powering the acceleration of clinical research to transform patient outcomes. We built a leading performance‑driven network of 100+ sites across the US, Europe, India, and Australia, conducting research directly in the communities where care is delivered across gastrointestinal, hepatology, obesity, and cardiology. By combining deep clinical trial expertise with cutting‑edge AI, we connect sponsors' scientific ambitions with high‑performing research teams that expedite and expand access to novel therapeutics for patients in need. Today, Iterative Health is headquartered in Cambridge, Massachusetts, and New York City with 250+ employees worldwide.
As the Senior Manager, Clinical Operations‑GI at Iterative Health you will serve as a strategic advisor to sponsors, CROs, and research sites, translating operational challenges into scalable solutions that improve study execution, accelerate activation timelines, and drive patient recruitment performance. By combining deep clinical research expertise with a consultative approach, this individual will help strengthen sponsor relationships, elevate site performance across the network, and contribute directly to Iterative Health's mission of bringing innovative therapies to patients faster.
As Iterative Health continues to expand its Site Network and partnerships with sponsors and CROs, operational excellence has become a critical differentiator. This role sits at the center of those relationships, helping ensure studies are launched efficiently, sites are set up for success, and sponsors receive the insights and partnership needed to achieve their clinical development goals. In particular, this role will own and scale the site activation process across the organization. This role is responsible for driving on‑time site activations within SLAs, proactively identifying and resolving blockers, and improving activation workflows to increase speed, predictability, and efficiency. This is a highly visible, customer‑facing role with the opportunity to influence study strategy, shape operational best practices, and drive measurable impact across a growing portfolio of clinical trials.
That seems good. Now Responsibilities: we need to list items. We'll create- for each bullet. From "Where You’ll Drive Impact Study Activation Ownership & Execution": - Own the end-to-end site activations, managing timelines, dependencies, and risks across multiple concurrent sites and trials - Help teams prioritize tasks and ensure milestones are met within defined SLAs - Maintain activation plans, status tracking, and documentation, escalating risks and delays proactively From "Sponsor & CRO Partnership": - Serve as the primary operational partner to sponsors, CROs, and sites throughout the trial lifecycle - Lead and support sponsor, CRO, and partner meetings by providing clinical operations expertise, actionable insights, and strategic recommendations - Build strong relationships with key stakeholders and ensure alignment on study goals, performance metrics, and operational priorities - Proactively communicate study risks, mitigation plans, and escalation strategies - Facilitate educational sessions, webinars, and
- for lists.
We must not include or tags.
We must not include markdown code fences.
Let's craft.
First, About the role:
We need to combine company overview and role description.
Prose: maybe two paragraphs.
We'll write: