Vice President, Content Director (Freelance)

We need to output HTML fragment with sections: About the role? The posting includes Company Description, Overview, What you will do, Responsibilities, Qualifications, Additional Information (benefits, compensation). We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some EEO lines: "All your information will be kept confidential according to EEO guidelines." That's boilerplate; remove. Also "If you require accommodation..." is maybe not boilerplate but could be considered application instruction? It's about accommodation request; maybe keep? The instruction says remove application instructions. That line is about accommodation request for application/onboarding; could be considered application instruction. Safer to remove. Also "Our Publicis Groupe motto..." is about benefits and culture; keep as part of Additional Information maybe under Benefits? It's not exactly benefits but could be under About the role? Might be considered company description. We'll keep as a paragraph under maybe "About the role" or separate? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have: - Company Description: description of GroupeConnect, role purpose. Could go under About the role. - Overview: part-time 20hrs/week. Could be under About the role or maybe Schedule? Actually schedule is part-time 20hrs/week, so we could put Schedule section with that detail. But we need to only include Schedule if posting actually states it. It does: "Overview **This role is a part-time position, approximately 20hrs/week**". So we can have a Schedule section with that. - What you will do: list of duties. That's Responsibilities? Actually they have a separate Responsibilities section later with bullet list of traits. The "What you will do" is more like duties/responsibilities. We'll treat that as Responsibilities (duties). Then later "Responsibilities A few things we want to see in you" is more like qualifications/skills? Actually that list is about desired traits/skills. Could be under Skills or Qualifications. The posting already has a Qualifications section. So we need to decide mapping. We have: - What you will do: list of duties (write/edit, translate, collaborate, adapt, fill gaps, present, balance, incorporate feedback, sweat details). That's responsibilities. - Responsibilities (the heading in posting) actually lists: Exceptional writing and editing skills, ability to make complex ideas feel approachable, clear understanding of how content and design work together, comfort working in ambiguous environments, editorial rigor, versatility across..., comfort collaborating, ability to organize..., curiosity..., low-ego..., creative skill I would not have thought to list here. That's more like skills/qualities. - Qualifications: list of ideal candidate requirements: portfolio, 10 years experience, experience writing for websites/digital products, experience working with UX/design/product/digital teams, exceptional skills writing short- and long-form, experience simplifying highly technical/regulated/complex subject matter, financial services experience preferred, journalism etc a plus, awareness of trends, experience with tools such as Figma a plus. - Additional Information: includes motto Viva La Différence, benefits package details, accommodation request line (remove), compensation range, application deadline, etc. We need to output sections: About the role (maybe combine company description and overview?), Responsibilities (duties), Skills (maybe from Responsibilities heading?), Qualifications, Benefits, Pay, Schedule. We must not create sections with filler. Ensure we have real content. Let's extract content precisely. Company Description paragraph: "At GroupeConnect, we think content is more than words on a page. The best copy helps people understand, decide, act, and move forward with confidence. That is especially true when the subject matter is complex. We are looking for a Vice President Content Director to support digital experiences for a major financial services client. This person will write short and long-form content across a wide range of experiences, audiences, and products, from consumer banking and investing to small and midsize business, commercial, and institutional solutions. This is not a production, only writing role. We're looking for someone who can ask smart questions, synthesize information from multiple sources, identify content gaps, and help shape the story behind the experience. You will work closely with content strategists and designers to create copy that supports the broader experience. You will not be responsible for owning information architecture or user journeys, but you will have a seat at the table and a voice in the conversation. Your background might be in journalism, publishing, editorial, advertising, UX writing, or something we have not thought of yet. What matters most is that you are a talented writer, a thoughtful collaborator, and someone who can make complicated things feel simple. Sound good? Good." Overview: "**This role is a part-time position, approximately 20hrs/week**" (the asterisks maybe markdown bold). We'll keep as plain text. What you will do list (each line starts with a verb). We'll convert to

• . Responsibilities (the heading in posting) list: each line starts with a trait. We'll treat as Skills maybe. Qualifications list: each line starts with a bullet? Actually they are sentences. We'll convert to
  • . Additional Information: includes motto paragraph, benefits description, compensation range, application deadline. Also includes line about accommodation request (remove). Also includes line about EEO (remove). Also includes line about temporary roles medical plan etc. Keep benefits description. We need to output HTML fragment only, no /. Use

    for each section heading. We need to decide sections: - About the role: could combine Company Description and Overview? Or we could have About the role (company description) and Schedule separate. Since we have Schedule section for part-time, we can put Overview in Schedule. About the role could be company description only. - Responsibilities: duties from "What you will do". - Skills: traits from "Responsibilities" heading. - Qualifications: qualifications list. - Benefits: benefits description from Additional Information. - Pay: compensation range. - Schedule: part-time 20hrs/week. We must not create sections with filler like "not specified". All have content. Now we need to preserve all substantive info, not invent or summarize away detail. So we need to keep each bullet exactly as in posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the wording as close as possible, but we can convert to list items. We should not omit any detail. Let's extract each piece exactly. Company Description paragraph: we need to keep it as a

    . Ensure we keep all sentences. Overview: part-time 20hrs/week. We'll put in Schedule section as a

    . What you will do: list: - Write and edit original content for websites, landing pages, digital products, tools, resource centers, and customer experiences - Translate complex financial topics into clear, compelling, customer-friendly language - Create content for audiences ranging from individual consumers to small businesses and large organizations - Collaborate closely with designers, content strategists, experience strategists, technologists, and client partners - Adapt content for different audiences, channels, and stages of the customer journey - Independently fill information gaps through research, synthesis, SMEs, etc. - Present and defend content recommendations with clients and internal teams - Balance customer needs, business goals, brand standards, accessibility requirements, and regulatory considerations - Incorporate feedback while maintaining content quality and strategic intent - Sweat the details while never losing sight of the bigger picture We need to keep each as

    . Responsibilities (skills) list: - Exceptional writing and editing skills - The ability to make complex ideas feel approachable and easy to understand - A clear understanding of how content and design work together - Comfort working in ambiguous environments where designs, requirements, and information are still evolving - Editorial rigor, attention to detail, and responsibility for maintaining accuracy, consistency, legal compliance, and quality - Versatility across long-form thought leadership, resource guides, landing pages, product content, and digital experiences - Comfort collaborating with multidisciplinary teams - The ability to organize, execute, and defend the work - Curiosity, empathy, and informed opinions - A low-ego, collaborative approach to problem solving - A creative skill I would not have thought to list here Note the last item is a bit weird: "A creative skill I would not have thought to list here". We'll keep as is. Qualifications list: - A portfolio of relevant work showcasing exceptional digital writing and content development - At least 10 years of professional writing experience - Experience writing for websites, digital products, or customer experiences - Experience working closely with UX, design, product, or digital teams - Exceptional skills writing both short- and long-form content - Experience simplifying highly technical, regulated, or complex subject matter - Financial services, banking, investing, fintech, or B2B experience preferred - Journalism, editorial, publishing, or newsroom experience a plus - Awareness of current digital experience, content, and technology trends - Experience with tools such as Figma a plus We need to keep each as

    . Benefits: from Additional Information: "Our Publicis Groupe motto “Viva La Différence” means we’re better together, and we believe that our differences make us stronger. It means we honor and celebrate all identities, across all facets of intersectionality, and it underpins all that we do as an organization. We are focused on fostering belonging and creating equitable & inclusive experiences for all talent. Publicis Groupe provides robust and inclusive benefit programs and policies to support the evolving and diverse needs of our talent and enable every person to grow and thrive. 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." We need to keep that as a

    under Benefits section. Also maybe include the line about temporary roles medical plan? That is also part of Additional Information: "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. For regular roles, the Company will offer medical coverage, dental, vision, disability, 401k, and paid time off." This is also benefits info. Should we include? It's substantive. We'll include it as part of Benefits section. We must remove the accommodation request line and EEO line. Also remove line about application deadline? Actually we might keep application deadline under maybe a separate section? Not listed as heading; we could put under Additional Information? But we have no heading for that. Could we add a section like "Application deadline"? Not in allowed headings list. The instruction says 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. It might be okay to add other headings but better to stick to those. The deadline is not covered by those headings; we could maybe put it under About the role? Not appropriate. Could we put it under Additional Information as a paragraph without heading? The instruction says use those headings for sections; but we can still have paragraphs without heading? The output is just HTML fragment; we can have

    not under any heading? Probably they expect sections with headings; but we can have stray

    before first heading? Might be okay but safer to include deadline under maybe "About the role" or "Additional Information" but we don't have that heading. Could we