Senior Director, Product Design, Patient Experience
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.
We need to decide which sections to include based on content.
We have:
- Location: hybrid remote/in-office role. Medidata follows a hybrid office policy... This is location info. Could be part of "About the role"? Not a heading but we could include a short paragraph about location.
- About our Company: paragraph.
- About the Team: description of role responsibilities and leadership.
- Responsibilities: a long list of bullet-like sentences (but not bullet list). We need to turn into
- for any list of duties/requirements/benefits. So we need to parse responsibilities into list items.
- Qualifications: list of bullet-like sentences.
- Pay: salary ranges for different locations. This is specific content, so we should include a Pay section.
- Benefits: description of benefits (medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year). Also mention base pay part of total rewards, bonuses, etc. So we can include Benefits section.
- Schedule: Not explicitly given; only hybrid policy mentions expected on-site days per week following company policy. Not specific number. So we should not create Schedule section because it's not specific.
- Skills: Not explicit separate; qualifications cover skills.
We need to avoid boilerplate: EEO, equal opportunity, inclusion statement, etc. Remove those.
Also remove duplicated lines: there are two EEO sections (Medidata and 3DS). Remove both.
Also remove application instructions: "We will accept applications on an ongoing basis until we fill the position." That's application instruction; remove.
Also remove "As with all roles, Medidata sets ranges based on a number of factors..." maybe part of Pay? It's about salary ranges; we can keep as part of Pay section prose.
Also remove "Base pay is one part of the Total Rewards that Medidata provides to compensate and recognize employees for their work. Most sales positions are eligible for a commission on the terms of applicable plan documents, and many of Medidata's non-sales positions are eligible for annual bonuses." That's benefits/compensation; could go into Benefits or Pay. We'll include in Benefits.
Also remove "Medidata believes that benefits should connect you to the support you need when it matters most and provides benefits, including medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year." That's benefits.
Also remove "Equal Employment Opportunity: ..." and the inclusion statement.
Also remove "Qualified applicants with arrest or conviction records will be considered for employment..." etc.
Also remove "Salary Pay Transparency Compensation for the role will be commensurate with experience. The total expected compensation range will be between $184000 and $246000, representing the base salary (or annualized salary based on estimated hourly compensation) and target bonus." This is somewhat redundant with Pay ranges; but it's also filler? It says "commensurate with experience" which is placeholder; we should not include a section with just that. However we already have specific salary ranges for locations; we can keep Pay section with those ranges. The statement about commensurate with experience is filler; we should not include it as separate content. We can ignore it.
Now structure:
We need headings: About the Team? Actually we have "About the Team:" as a heading in original. Could map to "About the role"? But instructions list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the Team or About the Company. However we can still use headings for those sections if they have content; but they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those standard headings where applicable. But we can also use other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the allowed headings; we should not create other headings like About the Team or About the Company unless they map to one of those. However we could treat "About our Company" as "About the role"? Not exactly. Maybe we can incorporate company description into a brief paragraph under "About the role" or just as a
without heading. The instruction says: "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." It doesn't forbid other headings, but the examples suggest we should use those standard headings. However we need to preserve all substantive information; we can include company info as a
without heading, or under a heading like "About the Company" but that is not in the list. Safer to avoid extra headings; just include paragraphs.
Thus we can have:
Location: This is a hybrid remote/in-office role. Medidata follows a hybrid office policy in which employees who are hired for an in-person position are expected to work on site a certain number of days per week following Company policy.
Then maybe a paragraph about company: About our Company: Medidata is powering smarter treatments...
Then maybe a paragraph about the team: About the Team: As Senior Director of Product Design for Patient Experience, you will lead a team...
Then Responsibilities heading Responsibilities
with - items.
Then Qualifications heading
Qualifications
with - items.
Then Benefits heading
Benefits
with - items (or
if not list). Benefits are list: medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year. Also mention base pay part of total rewards, bonuses. Could make list items.
Then Pay heading
Pay
with - items for each location salary range.
We should not include Schedule.
We need to ensure we don't include filler like "commensurate with experience". So ignore that line.
Now extract responsibilities text:
"Own and execute the strategic design roadmap for Patient Experience, applying systems-level thinking to translate enterprise workflows into intuitive products across native iOS, Android, and web platforms.
Partner with Product and Engineering leadership to align vision, strategy, and current roadmap execution for patient capabilities, ensuring the roadmap maintains a user-centered focus.
Build active, open collaboration channels between your product design team and the dedicated Design Systems team. Partner on the Design Systems roadmap to ensure system updates are prioritized and successfully ingested into product releases.
Partner seamlessly with design leaders across the platform to activate shared capabilities, ensure cross-product coherence, and build unified platform experiences.
Partner deeply with Design Leadership, Product, Engineering, Strategy, Professional Services, and other key organizations across Medidata to understand operational challenges, identify high-leverage opportunities, and directly shape overarching product strategies.
Operates fluently on both sides of the Patient Experience. Brings consumer product skill in acquisition, onboarding, and retention, with a track record of moving people through a funnel and keeping them engaged past the drop-off points. Pairs that with systems mastery in enterprise environments built on multi-persona ecosystems and heavy operational workflows. Ideally the candidate thinks holistically by treating these as two sides of the same coin, not two separate challenges.
Architect holistic product ecosystems that bridge iOS, Android, and web modalities. Demonstrate high systems literacy to simplify complex interactions into scalable, coherent experience frameworks.
Elevate the quality and maturity of the design practice across interaction, visual, service, and additional soft skills. Guide the use of vision stories, journey maps, and high-fidelity prototypes.
Cultivate a thriving design team. Set strategic direction, provide active mentorship, orchestrate research collaborations, and build clear career growth pathways for your team members.
Build decision-making frameworks for complex regulatory, technical, or operational trade-offs, driving alignment across executive stakeholders and accelerating cross-functional execution."
We need to split into list items. Each sentence or clause could be an item. We'll make each bullet a separate
- . Ensure we keep all info.
Now qualifications:
"8+ years of product design leadership experience within medium to large-scale enterprise software platforms, complex systems, or multi-sided SaaS environments.
Proven track record of managing teams designing across native iOS, Android, and web modalities for complex, multi-persona platforms.
Exceptional executive communication, storytelling, and relationship-building capabilities across complex, matrixed organizations.
Deep experience partnering with executive design leadership, Product, and Engineering to shape roadmaps, address operational friction, and influence strategic investments.
Demonstrated experience fostering structured collaboration with dedicated Design System teams and influencing design system roadmaps for multi-product rollouts.
Proficiency with modern design tools (such as Figma), design system integration, and emerging AI-assisted workflows or patterns.
Experience in Life Sciences, Digital Health, or Clinical Research is helpful, but not required.
If you're a strategic thinker and expert craftsperson, we'd love to hear from you!"
We can make each line a
- . The last sentence is more of a closing; we can include as
- .
Now benefits:
"Medidata believes that benefits should connect you to the support you need when it matters most and provides benefits, including medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year.
Base pay is one part of the Total Rewards that Medidata provides to compensate and recognize employees for their work. Most sales positions are eligible for a commission on the terms of applicable plan documents, and many of Medidata's non-sales positions are eligible for annual bonuses."
We can make list items: medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off, 10 paid holidays per year, base pay part of total rewards, commission eligibility for sales positions, annual bonuses for many non-sales positions.
Now Pay:
"The salary range for positions that will be physically based in the NYC Metro Area is $184,500-246,000.
The salary range for positions that will be physically based in the California Bay Area is $194,250-259,000.
The salary range for positions that will be physically based in all other locations within the United States is $165,000-220,000."
Make list items.
Now location
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. We need to decide which sections to include based on content. We have: - Location: hybrid remote/in-office role. Medidata follows a hybrid office policy... This is location info. Could be part of "About the role"? Not a heading but we could include a short paragraph about location. - About our Company: paragraph. - About the Team: description of role responsibilities and leadership. - Responsibilities: a long list of bullet-like sentences (but not bullet list). We need to turn into
- for any list of duties/requirements/benefits. So we need to parse responsibilities into list items.
- Qualifications: list of bullet-like sentences.
- Pay: salary ranges for different locations. This is specific content, so we should include a Pay section.
- Benefits: description of benefits (medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year). Also mention base pay part of total rewards, bonuses, etc. So we can include Benefits section.
- Schedule: Not explicitly given; only hybrid policy mentions expected on-site days per week following company policy. Not specific number. So we should not create Schedule section because it's not specific.
- Skills: Not explicit separate; qualifications cover skills.
We need to avoid boilerplate: EEO, equal opportunity, inclusion statement, etc. Remove those.
Also remove duplicated lines: there are two EEO sections (Medidata and 3DS). Remove both.
Also remove application instructions: "We will accept applications on an ongoing basis until we fill the position." That's application instruction; remove.
Also remove "As with all roles, Medidata sets ranges based on a number of factors..." maybe part of Pay? It's about salary ranges; we can keep as part of Pay section prose.
Also remove "Base pay is one part of the Total Rewards that Medidata provides to compensate and recognize employees for their work. Most sales positions are eligible for a commission on the terms of applicable plan documents, and many of Medidata's non-sales positions are eligible for annual bonuses." That's benefits/compensation; could go into Benefits or Pay. We'll include in Benefits.
Also remove "Medidata believes that benefits should connect you to the support you need when it matters most and provides benefits, including medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year." That's benefits.
Also remove "Equal Employment Opportunity: ..." and the inclusion statement.
Also remove "Qualified applicants with arrest or conviction records will be considered for employment..." etc.
Also remove "Salary Pay Transparency Compensation for the role will be commensurate with experience. The total expected compensation range will be between $184000 and $246000, representing the base salary (or annualized salary based on estimated hourly compensation) and target bonus." This is somewhat redundant with Pay ranges; but it's also filler? It says "commensurate with experience" which is placeholder; we should not include a section with just that. However we already have specific salary ranges for locations; we can keep Pay section with those ranges. The statement about commensurate with experience is filler; we should not include it as separate content. We can ignore it.
Now structure:
We need headings: About the Team? Actually we have "About the Team:" as a heading in original. Could map to "About the role"? But instructions list example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list About the Team or About the Company. However we can still use headings for those sections if they have content; but they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should use those standard headings where applicable. But we can also use other headings if needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the allowed headings; we should not create other headings like About the Team or About the Company unless they map to one of those. However we could treat "About our Company" as "About the role"? Not exactly. Maybe we can incorporate company description into a brief paragraph under "About the role" or just as a
without heading. The instruction says: "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." It doesn't forbid other headings, but the examples suggest we should use those standard headings. However we need to preserve all substantive information; we can include company info as a
without heading, or under a heading like "About the Company" but that is not in the list. Safer to avoid extra headings; just include paragraphs. Thus we can have:
Location: This is a hybrid remote/in-office role. Medidata follows a hybrid office policy in which employees who are hired for an in-person position are expected to work on site a certain number of days per week following Company policy.
Then maybe a paragraph about company:About our Company: Medidata is powering smarter treatments...
Then maybe a paragraph about the team:About the Team: As Senior Director of Product Design for Patient Experience, you will lead a team...
Then Responsibilities headingResponsibilities
with- items.
Then Qualifications heading
Qualifications
with- items.
Then Benefits heading
Benefits
with- items (or
if not list). Benefits are list: medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year. Also mention base pay part of total rewards, bonuses. Could make list items. Then Pay heading
Pay
with- items for each location salary range. We should not include Schedule. We need to ensure we don't include filler like "commensurate with experience". So ignore that line. Now extract responsibilities text: "Own and execute the strategic design roadmap for Patient Experience, applying systems-level thinking to translate enterprise workflows into intuitive products across native iOS, Android, and web platforms. Partner with Product and Engineering leadership to align vision, strategy, and current roadmap execution for patient capabilities, ensuring the roadmap maintains a user-centered focus. Build active, open collaboration channels between your product design team and the dedicated Design Systems team. Partner on the Design Systems roadmap to ensure system updates are prioritized and successfully ingested into product releases. Partner seamlessly with design leaders across the platform to activate shared capabilities, ensure cross-product coherence, and build unified platform experiences. Partner deeply with Design Leadership, Product, Engineering, Strategy, Professional Services, and other key organizations across Medidata to understand operational challenges, identify high-leverage opportunities, and directly shape overarching product strategies. Operates fluently on both sides of the Patient Experience. Brings consumer product skill in acquisition, onboarding, and retention, with a track record of moving people through a funnel and keeping them engaged past the drop-off points. Pairs that with systems mastery in enterprise environments built on multi-persona ecosystems and heavy operational workflows. Ideally the candidate thinks holistically by treating these as two sides of the same coin, not two separate challenges. Architect holistic product ecosystems that bridge iOS, Android, and web modalities. Demonstrate high systems literacy to simplify complex interactions into scalable, coherent experience frameworks. Elevate the quality and maturity of the design practice across interaction, visual, service, and additional soft skills. Guide the use of vision stories, journey maps, and high-fidelity prototypes. Cultivate a thriving design team. Set strategic direction, provide active mentorship, orchestrate research collaborations, and build clear career growth pathways for your team members. Build decision-making frameworks for complex regulatory, technical, or operational trade-offs, driving alignment across executive stakeholders and accelerating cross-functional execution." We need to split into list items. Each sentence or clause could be an item. We'll make each bullet a separate
- . Ensure we keep all info. Now qualifications: "8+ years of product design leadership experience within medium to large-scale enterprise software platforms, complex systems, or multi-sided SaaS environments. Proven track record of managing teams designing across native iOS, Android, and web modalities for complex, multi-persona platforms. Exceptional executive communication, storytelling, and relationship-building capabilities across complex, matrixed organizations. Deep experience partnering with executive design leadership, Product, and Engineering to shape roadmaps, address operational friction, and influence strategic investments. Demonstrated experience fostering structured collaboration with dedicated Design System teams and influencing design system roadmaps for multi-product rollouts. Proficiency with modern design tools (such as Figma), design system integration, and emerging AI-assisted workflows or patterns. Experience in Life Sciences, Digital Health, or Clinical Research is helpful, but not required. If you're a strategic thinker and expert craftsperson, we'd love to hear from you!" We can make each line a
- . The last sentence is more of a closing; we can include as
- . Now benefits: "Medidata believes that benefits should connect you to the support you need when it matters most and provides benefits, including medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off; and 10 paid holidays per year. Base pay is one part of the Total Rewards that Medidata provides to compensate and recognize employees for their work. Most sales positions are eligible for a commission on the terms of applicable plan documents, and many of Medidata's non-sales positions are eligible for annual bonuses." We can make list items: medical, dental, life and disability insurance, 401(k) matching, family leave, flexible paid time off, 10 paid holidays per year, base pay part of total rewards, commission eligibility for sales positions, annual bonuses for many non-sales positions. Now Pay: "The salary range for positions that will be physically based in the NYC Metro Area is $184,500-246,000. The salary range for positions that will be physically based in the California Bay Area is $194,250-259,000. The salary range for positions that will be physically based in all other locations within the United States is $165,000-220,000." Make list items. Now location
- items (or
- items.
Then Benefits heading
- items.
Then Qualifications heading