Senior Director, Product Design, Patient Experience
maybe. Also salary ranges and benefits are present. So we need sections: maybe "About the Company", "About the Team", "Responsibilities", "Qualifications", "Pay", "Benefits". Also maybe "Location". The instructions: 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 (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.
We need to include location info as a short
maybe before sections. The location line: "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." That's location info. We'll put a
.
Then "About our Company": we can make heading
About the Company
and then paragraph(s). The content: "Medidata is powering smarter treatments and healthier people through digital solutions to support clinical trials. Celebrating over 25 years of ground-breaking technological innovation across more than 38,000 trials and 12 million patients, Medidata offers industry-leading expertise, analytics-powered insights, and one of the largest clinical trial data sets in the industry. More than 1 million registered users across approximately 2,300 customers trust Medidata's seamless, end-to-end platform to improve patient experiences, accelerate clinical breakthroughs, and bring therapies to market faster. A Dassault Systèmes brand (Euronext Paris: FR0014003TT8, DSY.PA), Medidata is headquartered in New York City and has been recognized as a Leader by Everest Group and IDC. Discover more at www.medidata.com. Listen to our latest podcast, from Dreamers to Disruptors, and follow us at @Medidata."
We should keep all that.
Then "About the Team": heading About the Team
and paragraph(s). The content: "As Senior Director of Product Design for Patient Experience, you will lead a team of product designers to define and execute the user experience across our patient ecosystem. Reporting to the SVP of Design & Experience and serving on the Design Leadership Team, you will partner closely with Product, Engineering, and peer design leaders across our core platform pillars, including data analytics, study management, and foundational design systems, to drive end-to-end experience excellence."
Then "Responsibilities": heading Responsibilities
and then list items as - . The responsibilities list is a long paragraph with many sentences separated by periods. We need to break into list items. The instruction: Use
- for any list of duties/requirements/benefits. So we should convert each duty into a list item. The responsibilities block includes many sentences. We'll split by sentences that start with capital letters after a period. Let's extract:
"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 ensure each is a list item.
Now "Qualifications": heading
Qualifications
and list items.
Qualifications block:
"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 could keep the last sentence as a list item or maybe as a paragraph? It's more of a call to action; but it's part of qualifications. We'll treat as list item.
Now Pay: we have salary ranges for different locations. The posting includes salary ranges. So we need a Pay section. According to instruction: include Pay section only if posting actually states them. Yes it does. So we create Pay
and then maybe a with the ranges. Could also list as
- but it's not a list of items; it's prose. We'll use
.
Content: "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. 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 should keep all that.
Benefits: posting includes 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."
We'll make
Benefits
and then a with that sentence.
We also need to include location info as a short
maybe before sections. The location line: "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." We'll output as
.
We must not include EEO, scam warning, etc. Also we should not include "Note: Please be on the lookout for job scams." etc. Also not include "Equal Employment Opportunity :" etc. Also not include "We will accept applications on an ongoing basis until we fill the position." That's application instruction; drop.
Also we should not repeat job title as heading; we aren't.
Now output only HTML fragment, no /, no markdown fences.
Let's construct:
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.
About the Company
Medidata is powering smarter treatments and healthier people through digital solutions to support clinical trials. Celebrating over 25 years of ground-breaking technological innovation across more than 38,000 trials and 12 million patients, Medidata offers industry-leading expertise, analytics-powered insights, and one of the largest clinical trial data sets in the industry. More than 1 million registered users across approximately 2,300 customers trust Medidata's seamless, end-to-end platform to improve patient experiences, accelerate clinical breakthroughs, and bring therapies to market faster. A Dassault Systèmes brand (Euronext Paris: FR0014003TT8, DSY.PA), Medidata is headquartered in New York City and has been recognized as a Leader by Everest Group and IDC. Discover more at www.medidata.com. Listen to our latest podcast, from Dreamers to Disruptors, and follow us at @Medidata.
About the Team
As Senior Director of Product Design for Patient Experience, you will lead a team of product designers to define and execute the user experience across our patient ecosystem. Reporting to the SVP of Design & Experience and serving on the Design Leadership Team, you will partner closely with Product, Engineering, and peer design leaders across our core platform pillars, including data analytics, study management, and foundational design systems, to drive end-to-end experience excellence.
Responsibilities
- 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
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. We need to include location info as a short
maybe before sections. The location line: "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." That's location info. We'll put a
. Then "About our Company": we can make heading
About the Company
and then paragraph(s). The content: "Medidata is powering smarter treatments and healthier people through digital solutions to support clinical trials. Celebrating over 25 years of ground-breaking technological innovation across more than 38,000 trials and 12 million patients, Medidata offers industry-leading expertise, analytics-powered insights, and one of the largest clinical trial data sets in the industry. More than 1 million registered users across approximately 2,300 customers trust Medidata's seamless, end-to-end platform to improve patient experiences, accelerate clinical breakthroughs, and bring therapies to market faster. A Dassault Systèmes brand (Euronext Paris: FR0014003TT8, DSY.PA), Medidata is headquartered in New York City and has been recognized as a Leader by Everest Group and IDC. Discover more at www.medidata.com. Listen to our latest podcast, from Dreamers to Disruptors, and follow us at @Medidata." We should keep all that. Then "About the Team": headingAbout the Team
and paragraph(s). The content: "As Senior Director of Product Design for Patient Experience, you will lead a team of product designers to define and execute the user experience across our patient ecosystem. Reporting to the SVP of Design & Experience and serving on the Design Leadership Team, you will partner closely with Product, Engineering, and peer design leaders across our core platform pillars, including data analytics, study management, and foundational design systems, to drive end-to-end experience excellence." Then "Responsibilities": headingResponsibilities
and then list items as- . The responsibilities list is a long paragraph with many sentences separated by periods. We need to break into list items. The instruction: Use
- for any list of duties/requirements/benefits. So we should convert each duty into a list item. The responsibilities block includes many sentences. We'll split by sentences that start with capital letters after a period. Let's extract:
"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 ensure each is a list item.
Now "Qualifications": heading
Qualifications
and list items. Qualifications block: "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 could keep the last sentence as a list item or maybe as a paragraph? It's more of a call to action; but it's part of qualifications. We'll treat as list item. Now Pay: we have salary ranges for different locations. The posting includes salary ranges. So we need a Pay section. According to instruction: include Pay section only if posting actually states them. Yes it does. So we createPay
and then maybe awith the ranges. Could also list as
- but it's not a list of items; it's prose. We'll use
. Content: "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. 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 should keep all that. Benefits: posting includes 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." We'll make
Benefits
and then awith that sentence. We also need to include location info as a short
maybe before sections. The location line: "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." We'll output as
. We must not include EEO, scam warning, etc. Also we should not include "Note: Please be on the lookout for job scams." etc. Also not include "Equal Employment Opportunity :" etc. Also not include "We will accept applications on an ongoing basis until we fill the position." That's application instruction; drop. Also we should not repeat job title as heading; we aren't. Now output only HTML fragment, no /, no markdown fences. Let's construct:
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.
About the Company
Medidata is powering smarter treatments and healthier people through digital solutions to support clinical trials. Celebrating over 25 years of ground-breaking technological innovation across more than 38,000 trials and 12 million patients, Medidata offers industry-leading expertise, analytics-powered insights, and one of the largest clinical trial data sets in the industry. More than 1 million registered users across approximately 2,300 customers trust Medidata's seamless, end-to-end platform to improve patient experiences, accelerate clinical breakthroughs, and bring therapies to market faster. A Dassault Systèmes brand (Euronext Paris: FR0014003TT8, DSY.PA), Medidata is headquartered in New York City and has been recognized as a Leader by Everest Group and IDC. Discover more at www.medidata.com. Listen to our latest podcast, from Dreamers to Disruptors, and follow us at @Medidata.
About the Team
As Senior Director of Product Design for Patient Experience, you will lead a team of product designers to define and execute the user experience across our patient ecosystem. Reporting to the SVP of Design & Experience and serving on the Design Leadership Team, you will partner closely with Product, Engineering, and peer design leaders across our core platform pillars, including data analytics, study management, and foundational design systems, to drive end-to-end experience excellence.
Responsibilities
- 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
- but it's not a list of items; it's prose. We'll use
- for any list of duties/requirements/benefits. So we should convert each duty into a list item. The responsibilities block includes many sentences. We'll split by sentences that start with capital letters after a period. Let's extract:
"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 ensure each is a list item.
Now "Qualifications": heading