Associate, Regulatory Operations
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 (the page already shows it) and 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.
Thus we need to decide which sections to include. The posting includes Company Description, Overview, Responsibilities, Qualifications (with SKILLS & EXPERIENCE: Required, Preferred, Desirable), Additional Information (benefits, pay range, accommodation contact, EEO, compensation range, etc). We need to remove EEO boilerplate etc. Also remove application instructions (like contact for accommodation? Actually that is not application instruction but accommodation contact; maybe keep? It's not application instruction, it's accommodation contact. Might keep as part of Additional Information. But we need to remove EEO guidelines etc. Also remove duplicated lines.
We need to decide headings: Could use "About the role" for Overview? Or "Overview". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate ones. The posting has "Overview" which describes role. Could map to "About the role". Could also keep "Overview" but they said use those examples; not mandatory but likely they expect those headings. We'll use "About the role" for overview, "Responsibilities" for duties, "Qualifications" for skills & experience (maybe split into Required, Preferred, Desirable as lists). For benefits, we have benefits listed: medical coverage, dental, vision, disability, 401K, parental and family care leave, family forming assistance, tuition reimbursement, flexible time off. Also mention freelancer/temporary employee medical plan etc. Also compensation range: USD $25.94 - USD $34.43/Hourly. That's pay. So we need a Pay section with that range. Also maybe a Benefits section for benefits. Schedule not mentioned, so omit.
We also have Company Description at top; could be part of About the role? Or we could have a separate "Company Description" but not in list; but we could incorporate into About the role? The instruction says prefer a few substantive sections over many thin ones. Could combine Company Description and Overview into About the role. But we need to preserve all substantive information; we can include company description as a paragraph under About the role.
Thus structure:
About the role
Company Description paragraph(s) + Overview paragraph(s).
Responsibilities
- ...
Qualifications
Maybe we can have subheadings? Not allowed? Only h3 for section headings. Could we have nested? Probably not. We could just list all qualifications as bullet points under Qualifications, marking required vs preferred vs desirable maybe within bullet text. Or we could have separate sections: Required Skills, Preferred Skills, Desirable Experience. But those are not in the list; but we could still use h3 for each? 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 prefer a few substantive sections over many thin ones. So better to have one Qualifications section with bullet points that include required, preferred, desirable. We'll embed that info.
Thus:
Qualifications
- Required: Minimum of a bachelor's degree; Technical competency in Adobe Acrobat and the Microsoft Office Suite; Excellent communication skills and diligent attention to detail; Top notch organizational skills.
- Preferred: Related internship, co-op, or professional experience; Experience in the preparation of complex submission deliverables under tight deadline constraints; Clear, concise technical writing ability; Working knowledge of Adobe InDesign and Photoshop.
- Desirable: Experience in Pharmaceutical Industry, Healthcare, or similar environment; Agency and/or project management experience; Experience working on cross-functional teams.
Benefits
- Medical coverage
- Dental
- Vision
- Disability
- 401K
- Parental and family care leave
- Family forming assistance
- Tuition reimbursement
- Flexible time off
- For temporary roles: eligibility to participate in freelancer/temporary employee medical plan via third‑party benefits administration system once certain criteria are met.
Pay
Compensation Range: USD $25.94 - USD $34.43/Hourly.
We should also include the accommodation contact? That's under Additional Information: "If you require accommodation or assistance with the application or onboarding process specifically, please contact USMTTACompliance@publicis.com." That's not boilerplate; it's specific contact. Should we keep? It's not application instructions per se, it's accommodation contact. Might keep as a paragraph under Additional Information or maybe under a separate heading like "Accommodation". But we don't have a heading for that; we could add a short paragraph under Benefits or under a generic "Additional Information". However instruction says prefer few substantive sections; we could add a paragraph under Benefits or under Pay? Better to add a small paragraph under a heading like "Additional Information". But that heading is not in the list; but we could still use h3 for Additional Information? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are typical but not exhaustive. However they also say "Prefer a few substantive sections over many thin ones." Adding an Additional Information section may be thin. Could we fold the accommodation contact into Benefits or Pay? It's not really benefits or pay. Could put under a paragraph after Pay as a note. That would be extra content but not a heading. That's allowed: we can have
for prose anywhere. So we can add a
after Pay section with that accommodation sentence.
Also we need to remove EEO boilerplate: "All your information will be kept confidential according to EEO guidelines." Remove. Also remove "Publicis Groupe provides robust and inclusive benefit programs..." we already captured benefits. Also remove "Our Publicis Groupe motto “Viva La Différence”..." maybe we can keep as part of company description? It's part of company description but maybe not essential? It's substantive about culture. Could keep in About the role paragraph.
We need to preserve all substantive information; we should not omit the motto etc. It's part of company description. So include it.
Let's craft About the role paragraph(s):
We have Company Description: "Digitas Health is the modern creative agency that takes on the biggest moments in healthcare, raises the standard of creative, and connects people, partners, and ideas to create work that earns its place in culture. Purpose-built for today’s complex and evolving landscape, we partner with some of the world’s largest healthcare brands to do big things by moving faster, connecting deeper, and unlocking new possibilities at the intersection of creativity, data, technology, and empathy. Guided by our purpose, Connected for Good, and fueled by a vibrant, magnetic culture—we deliver meaningful work that drives relevance, changes behavior, and creates lasting impact, always grounded in humanity, not just technology. As part of Publicis Health and Publicis Groupe, we bring together entrepreneurial energy with the scale, stability, and depth of one of the world’s leading communications networks. At Digitas Health, what sets us apart isn’t just who we work with, it’s how we work and how it feels to be here. Our culture attracts curious, driven people who want to make a difference and be part of something bigger. Our teams are intentionally crafted across disciplines, perspectives, and experience levels, bringing strategy, creativity, data, and technology together from the start. We believe the best ideas come from curiosity, collaboration, and healthy debate and we expect people here to be thoughtful, engaged, and eager to shape what’s next. If you’re energized by complexity, motivated by impact, and excited to help redefine how healthcare connects with people, we’d love to meet you!"
Then Overview: "The Associate, Regulatory Promotional Operations works closely with the internal Regulatory team to assist in the preparation of promotional materials for submission to our pharmaceutical clients’ Medical, Legal, Regulatory (MLR) review. The Associate is responsible for utilizing client-specific submission tools and software in order to create components of the submission package while ensuring adherence to client specific standards and requirements, as well as internal guidelines. Additionally, the Associate is responsible for facilitating communication among team members about the status of projects currently underway, as well as assisting in accurately maintaining the departmental archive."
We can combine into one or two paragraphs.
Now Responsibilities: list from "DUTIES & RESPONSIBILITIES:" bullet points:
- Assemble submission packages through taking screenshots, annotating pertinent information, and attaching references and other ancillary documentation.
- Ensure components conform to both client and Digitas Health guidelines and requirements.
- Comfortably balance multiple assignments simultaneously.
- Directly communicate in a clear and concise manner with internal stakeholders.
- Assist in maintaining departmental archive.
We need to ensure we keep the exact phrasing.
Now Qualifications: we have "SKILLS & EXPERIENCE:" then Required, Preferred, Desirable.
We need to capture each bullet.
Required:
- Minimum of a bachelor's degree
- Technical competency in Adobe Acrobat and the Microsoft Office Suite
- Excellent communication skills and diligent attention to detail
- Top notch organizational skills
Preferred:
- Related internship, co-op, or professional experience
- Experience in the preparation of complex submission deliverables under tight deadline constraints
- Clear, concise technical writing ability
- Working knowledge of Adobe InDesign and Photoshop
Desirable:
- Experience in Pharmaceutical Industry, Healthcare, or similar environment
- Agency and/or project management experience
- Experience working on cross-functional teams
Now Benefits: from Additional Information: "Our benefits package includes medical coverage, dental, vision, disability, 401K, as well as parental and family care leave, family forming assistance, tuition reimbursement, and flexible time off." Also "Temporary roles may be eligible to participate in our freelancer/temporary employee medical plan through a third-party benefits administration system once certain criteria have been met." Also "For regular roles, the Company will offer medical coverage, dental, vision, disability, 401k, and paid time off." There's some duplication. We'll combine unique items.
List:
- Medical coverage
- Dental
- Vision
- Disability
- 401K
- Parental and family care leave
- Family forming assistance
for prose. Do NOT repeat the job title as a heading (the page already shows it) and 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. Thus we need to decide which sections to include. The posting includes Company Description, Overview, Responsibilities, Qualifications (with SKILLS & EXPERIENCE: Required, Preferred, Desirable), Additional Information (benefits, pay range, accommodation contact, EEO, compensation range, etc). We need to remove EEO boilerplate etc. Also remove application instructions (like contact for accommodation? Actually that is not application instruction but accommodation contact; maybe keep? It's not application instruction, it's accommodation contact. Might keep as part of Additional Information. But we need to remove EEO guidelines etc. Also remove duplicated lines. We need to decide headings: Could use "About the role" for Overview? Or "Overview". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate ones. The posting has "Overview" which describes role. Could map to "About the role". Could also keep "Overview" but they said use those examples; not mandatory but likely they expect those headings. We'll use "About the role" for overview, "Responsibilities" for duties, "Qualifications" for skills & experience (maybe split into Required, Preferred, Desirable as lists). For benefits, we have benefits listed: medical coverage, dental, vision, disability, 401K, parental and family care leave, family forming assistance, tuition reimbursement, flexible time off. Also mention freelancer/temporary employee medical plan etc. Also compensation range: USD $25.94 - USD $34.43/Hourly. That's pay. So we need a Pay section with that range. Also maybe a Benefits section for benefits. Schedule not mentioned, so omit. We also have Company Description at top; could be part of About the role? Or we could have a separate "Company Description" but not in list; but we could incorporate into About the role? The instruction says prefer a few substantive sections over many thin ones. Could combine Company Description and Overview into About the role. But we need to preserve all substantive information; we can include company description as a paragraph under About the role. Thus structure:
About the role
Company Description paragraph(s) + Overview paragraph(s).
Responsibilities
- ...
Qualifications
Maybe we can have subheadings? Not allowed? Only h3 for section headings. Could we have nested? Probably not. We could just list all qualifications as bullet points under Qualifications, marking required vs preferred vs desirable maybe within bullet text. Or we could have separate sections: Required Skills, Preferred Skills, Desirable Experience. But those are not in the list; but we could still use h3 for each? 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 prefer a few substantive sections over many thin ones. So better to have one Qualifications section with bullet points that include required, preferred, desirable. We'll embed that info. Thus:Qualifications
- Required: Minimum of a bachelor's degree; Technical competency in Adobe Acrobat and the Microsoft Office Suite; Excellent communication skills and diligent attention to detail; Top notch organizational skills.
- Preferred: Related internship, co-op, or professional experience; Experience in the preparation of complex submission deliverables under tight deadline constraints; Clear, concise technical writing ability; Working knowledge of Adobe InDesign and Photoshop.
- Desirable: Experience in Pharmaceutical Industry, Healthcare, or similar environment; Agency and/or project management experience; Experience working on cross-functional teams.
Benefits
- Medical coverage
- Dental
- Vision
- Disability
- 401K
- Parental and family care leave
- Family forming assistance
- Tuition reimbursement
- Flexible time off
- For temporary roles: eligibility to participate in freelancer/temporary employee medical plan via third‑party benefits administration system once certain criteria are met.
Pay
Compensation Range: USD $25.94 - USD $34.43/Hourly.
We should also include the accommodation contact? That's under Additional Information: "If you require accommodation or assistance with the application or onboarding process specifically, please contact USMTTACompliance@publicis.com." That's not boilerplate; it's specific contact. Should we keep? It's not application instructions per se, it's accommodation contact. Might keep as a paragraph under Additional Information or maybe under a separate heading like "Accommodation". But we don't have a heading for that; we could add a short paragraph under Benefits or under a generic "Additional Information". However instruction says prefer few substantive sections; we could add a paragraph under Benefits or under Pay? Better to add a small paragraph under a heading like "Additional Information". But that heading is not in the list; but we could still use h3 for Additional Information? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are typical but not exhaustive. However they also say "Prefer a few substantive sections over many thin ones." Adding an Additional Information section may be thin. Could we fold the accommodation contact into Benefits or Pay? It's not really benefits or pay. Could put under a paragraph after Pay as a note. That would be extra content but not a heading. That's allowed: we can have
for prose anywhere. So we can add a
after Pay section with that accommodation sentence. Also we need to remove EEO boilerplate: "All your information will be kept confidential according to EEO guidelines." Remove. Also remove "Publicis Groupe provides robust and inclusive benefit programs..." we already captured benefits. Also remove "Our Publicis Groupe motto “Viva La Différence”..." maybe we can keep as part of company description? It's part of company description but maybe not essential? It's substantive about culture. Could keep in About the role paragraph. We need to preserve all substantive information; we should not omit the motto etc. It's part of company description. So include it. Let's craft About the role paragraph(s): We have Company Description: "Digitas Health is the modern creative agency that takes on the biggest moments in healthcare, raises the standard of creative, and connects people, partners, and ideas to create work that earns its place in culture. Purpose-built for today’s complex and evolving landscape, we partner with some of the world’s largest healthcare brands to do big things by moving faster, connecting deeper, and unlocking new possibilities at the intersection of creativity, data, technology, and empathy. Guided by our purpose, Connected for Good, and fueled by a vibrant, magnetic culture—we deliver meaningful work that drives relevance, changes behavior, and creates lasting impact, always grounded in humanity, not just technology. As part of Publicis Health and Publicis Groupe, we bring together entrepreneurial energy with the scale, stability, and depth of one of the world’s leading communications networks. At Digitas Health, what sets us apart isn’t just who we work with, it’s how we work and how it feels to be here. Our culture attracts curious, driven people who want to make a difference and be part of something bigger. Our teams are intentionally crafted across disciplines, perspectives, and experience levels, bringing strategy, creativity, data, and technology together from the start. We believe the best ideas come from curiosity, collaboration, and healthy debate and we expect people here to be thoughtful, engaged, and eager to shape what’s next. If you’re energized by complexity, motivated by impact, and excited to help redefine how healthcare connects with people, we’d love to meet you!" Then Overview: "The Associate, Regulatory Promotional Operations works closely with the internal Regulatory team to assist in the preparation of promotional materials for submission to our pharmaceutical clients’ Medical, Legal, Regulatory (MLR) review. The Associate is responsible for utilizing client-specific submission tools and software in order to create components of the submission package while ensuring adherence to client specific standards and requirements, as well as internal guidelines. Additionally, the Associate is responsible for facilitating communication among team members about the status of projects currently underway, as well as assisting in accurately maintaining the departmental archive." We can combine into one or two paragraphs. Now Responsibilities: list from "DUTIES & RESPONSIBILITIES:" bullet points: - Assemble submission packages through taking screenshots, annotating pertinent information, and attaching references and other ancillary documentation. - Ensure components conform to both client and Digitas Health guidelines and requirements. - Comfortably balance multiple assignments simultaneously. - Directly communicate in a clear and concise manner with internal stakeholders. - Assist in maintaining departmental archive. We need to ensure we keep the exact phrasing. Now Qualifications: we have "SKILLS & EXPERIENCE:" then Required, Preferred, Desirable. We need to capture each bullet. Required: - Minimum of a bachelor's degree - Technical competency in Adobe Acrobat and the Microsoft Office Suite - Excellent communication skills and diligent attention to detail - Top notch organizational skills Preferred: - Related internship, co-op, or professional experience - Experience in the preparation of complex submission deliverables under tight deadline constraints - Clear, concise technical writing ability - Working knowledge of Adobe InDesign and Photoshop Desirable: - Experience in Pharmaceutical Industry, Healthcare, or similar environment - Agency and/or project management experience - Experience working on cross-functional teams Now Benefits: from Additional Information: "Our benefits package includes medical coverage, dental, vision, disability, 401K, as well as parental and family care leave, family forming assistance, tuition reimbursement, and flexible time off." Also "Temporary roles may be eligible to participate in our freelancer/temporary employee medical plan through a third-party benefits administration system once certain criteria have been met." Also "For regular roles, the Company will offer medical coverage, dental, vision, disability, 401k, and paid time off." There's some duplication. We'll combine unique items. List: - Medical coverage - Dental - Vision - Disability - 401K - Parental and family care leave - Family forming assistance