Vice President, Digital Experience

We need to output HTML fragment with sections: About the role? Actually description includes "About TelyRx Healthcare." That's about company. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We need to parse the posting for content. We have description: "Description About TelyRx Healthcare. Simplified. Delivered...." That's about company. Could map to "About the role"? Actually "About the role" is typical heading for role description. The posting includes "The role" section describing remote role, must sit in Seattle Area, authoring experience brief etc. So we can put that under

About the role

with paragraphs. Then "What you’ll own" and "What you’ll do" could be responsibilities. So

Responsibilities

with list items. Then "How Success Is Measured" maybe could be under Responsibilities or separate? Could be "Qualifications"? Not exactly. There's "Requirements" section later with MUST-HAVES and NICE-TO-HAVES. So we can put that under

Requirements

(or Qualifications). The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have "Compensation And Benefits" section with some bullet: Compensation Bonus or equity, if applicable Health, dental, vision PTO, parental leave, and other benefits. That's benefits info. So we can include

Benefits

with list. Pay: Not specific numbers, just "Compensation Bonus or equity, if applicable". That's vague; we should not create Pay section unless posting actually states them. It mentions compensation but no specific salary. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specifics: Health, dental, vision PTO, parental leave, and other benefits. That's enough for Benefits. Pay: we have only "Compensation Bonus or equity, if applicable" which is vague but still mentions compensation. However it's not a specific number or range; but it's still stating compensation exists. The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation (bonus or equity). Might be considered stating them. However they also say prefer a few substantive sections over many thin ones. Could combine compensation into Benefits? But we have separate Benefits heading allowed. Could we put compensation under Benefits? Probably better to have Benefits section include health etc and also mention compensation bonus/equity. But the instruction says use headings exactly those names; we can have Benefits and maybe not Pay if not specific. We'll omit Pay. Schedule: Not mentioned (remote role but must sit in Seattle Area). No schedule details. So omit Schedule. Skills: Not explicitly listed; maybe we could infer from requirements but better not to invent. So omit Skills. Qualifications: Could be separate from Requirements? The posting has Requirements (MUST-HAVES, NICE-TO-HAVES). Could map to Requirements heading. Qualifications maybe not needed. We'll include Requirements. We also have "How We Work" section describing Tely 5 etc. Could be part of Responsibilities or maybe a separate section like "How We Work" but not in allowed headings. Could fold into Responsibilities or About the role. Probably incorporate into Responsibilities as prose. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "Equal opportunity TelyRx is an equal opportunity employer..." That's boilerplate; we should remove. Also "Compensation And Benefits" includes "Equal opportunity" line after benefits; we need to drop that. We need to output only HTML fragment. Let's extract substantive content: Company description: About TelyRx Healthcare... (first paragraph). Could be part of About the role? Actually About the role should describe the role, not company. But we have no separate "About the company" heading allowed. Could we put company description under About the role? Might be odd but allowed as it's substantive. However the instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Likely they expect we use those headings for sections. We could have About the role includes both role and company context? Might be okay. Alternatively we could treat the initial description as "About the role" (the role at TelyRx). We'll include that. Now role details: "The role While this is a remote role, this candidate must sit in the Seattle Area You author the experience brief for every patient-facing surface: acquisition-to-conversion, PDP and checkout, refill and win-back, personalization, content, and the martech. You turn the persona of record into a built experience, commission the build from Engineering, and stand behind conversion and retention. You own the capability and the surface, not the revenue number, and you build the capability once so Commercial never rebuilds it. This is the seat every patient meets TelyRx through." We'll put that in About the role paragraph(s). Responsibilities: combine "What you’ll own" and "What you’ll do" and "How Success Is Measured" maybe. Let's list responsibilities bullet points: - Author the experience brief for every patient-facing surface: acquisition, PDP and checkout, refill and win-back, personalization, content, and the martech. - Turn the persona of record into a built experience and commission the build from Engineering. - Own conversion rate and lift by surface, and run the experimentation program through the Manager, CRO and Experimentation. - Own PDP, checkout, refill, and win-back surfaces, and the personalization and content that lift them. - Own the martech, tags, and conversion tracking the paid and organic engines run on. - Lead Content Experience, SEO and Organic Growth, UX, and the Personalization and Lifecycle Lead. - Partner with BI on the measurement truth that judges each surface, and with Commercial on the briefs. - Keep the capability built once and reusable, so Commercial pulls it rather than rebuilding it. - Grow the experimentation muscle and the team, so win rate and bench both compound. - Set experience OKRs and run the experiment review off conversion and win rate. - Influence acquisition and retention numbers (owned by Commercial) via surfaces you build. - In first 90 days: establish one conversion baseline and target by surface, agreed with BI; maintain experiment backlog with win-rate view; agree refill and win-back surface roadmap with Commercial and Lifecycle. - Metrics to own: conversion rate and lift by surface, refill and win-back completion, experiment velocity and win rate, brief-to-ship time. We need to ensure we don't invent. All these are from text. Now Requirements: MUST-HAVES and NICE-TO-HAVES. MUST-HAVES: - Led digital experience, conversion, or product for a DTC or consumer platform. - Ran a CRO or experimentation program and moved a conversion metric. - Owned PDP, checkout, or lifecycle surfaces end to end. - Built and led a team across UX, content, SEO, and experimentation. NICE-TO-HAVES: - Healthcare, pharmacy, or regulated consumer experience. - Worked in a capability-versus-outcome model, serving outcome owners from a shared capability. We'll put these under Requirements as

• . Benefits: from "Compensation And Benefits": Compensation Bonus or equity, if applicable; Health, dental, vision; PTO, parental leave, and other benefits. We'll list as bullet points. We must not include EEO line. Now produce HTML:

  About the role

  ... paragraphs ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Benefits

  • ...
  ...
  Check for any duplicated lines: ensure we didn't repeat. Now craft paragraphs. About the role paragraph: combine company description and role specifics. Company description: "TelyRx is a technology-enabled healthcare and pharmacy services company on a mission to make getting everyday medications simple, affordable, and fast. Our digital pharmacy platform connects patients with independent, state-licensed providers, then fulfills and ships prescriptions through our own licensed retail pharmacies. We call it the You era of healthcare: no waiting rooms, no appointments, no insurance required. We’ve filled more than 1,000,000 prescriptions, earned over 10,000 five-star reviews, and now offer 450+ everyday medications across 48 U.S. states and territories. A licensed provider reviews each request, within 24 hours, and approved orders ship quickly and discreetly to the patient’s door. Clear pricing, no surprises. We’re a publicly traded company (TSX: TELY, OTCQX: TELYF) growing fast, with teams across Dallas, Tampa, Boulder, and Seattle. If you want your work to reach real people on the day they need it most, you’ll feel at home here." Then role specifics: "While this is a remote role, this candidate must sit in the Seattle Area. You author the experience brief for every patient-facing surface: acquisition-to-conversion, PDP and checkout, refill and win-back, personalization, content, and the martech. You turn the persona of record into a built experience, commission the build from Engineering, and stand behind conversion and retention. You own the capability and the surface, not the revenue number, and you build the capability once so Commercial never rebuilds it. This is the seat every patient meets TelyRx through." We can combine into one or two paragraphs. Now Responsibilities list. Let's craft bullet points precisely as per text. From "What you’ll own": - The experience brief for every patient-facing surface: acquisition, PDP and checkout, refill and win-back, personalization, content, and the martech. - The authored experience that turns the persona of record into something built and measured. - Conversion rate and lift by surface, experiment velocity and win rate, and brief-to-ship time. - The seam with Engineering: you author and commission, they build, and you hold the surface to the number. - The team: Content Experience, SEO and Organic Growth, UX, Manager CRO and Experimentation, and the Personalization and Lifecycle Lead. From "What you’ll do": - Author the experience brief from the persona of record, and commission the build from Engineering. - Own conversion rate and lift by surface, and run the experimentation program through the Manager, CRO and Experimentation. - Own PDP, checkout, refill, and win-back surfaces, and the personalization and content that lift them. - Own the martech, tags, and conversion tracking the paid and organic engines run on. - Lead Content Experience, SEO and Organic Growth, UX, and the Personalization and Lifecycle Lead. - Partner with BI on the measurement truth that judges each surface, and with Commercial on the briefs. - Keep the capability built once and reusable, so Commercial pulls it rather than rebuilding it. - Grow the experimentation muscle and the team, so win rate and bench both compound. From "How Success Is Measured": - You run experience from a small set of conversion numbers and set the objectives for the surface team. - FIRST 90 DAYS: One conversion baseline and target by surface, agreed with BI. An experiment backlog running with a win-rate view. The refill and win-back surface roadmap agreed with Commercial and L