Director, Internal Communications & Employer Brand

We need to output HTML fragment with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the posting. The posting includes: - Intro about Circle (company description) maybe "About the role"? Actually "What You'll Be Part Of" is about company culture. Could be considered "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: description of role, what you'll be part of, what you'll be responsible for, what you'll work on (maybe responsibilities). But we need separate sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content for each. Let's parse: Company description: "Circle (NYSE: CRCL) is one of the world’s leading internet financial platform companies..." This is about company, not role. Could be placed under "About the role"? Probably not. 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. So we can include a short paragraph about company maybe under "About the role"? But "About the role" is more about the role itself, not company. However we have no explicit "About the role" section in posting. The posting includes "What You'll Be Part Of" describing company culture and values. That could be considered "About the role"? Might be okay. But we need to include sections only when posting has real specific content. Let's see each: - Responsibilities: The posting has "What you'll be responsible for" and then bullet-like paragraphs describing responsibilities. Also "What you'll work on" with subcategories: Internal Communications, Employer Brand, Content & Cross-Functional Partnership, AI-First Operations. Those are responsibilities. So we can put those under Responsibilities. - Requirements: The posting has "What you'll bring to Circle Core Requirements" with a list of bullet points (numbered). Those are core requirements. Also "Preferred Background" maybe qualifications? Actually "Preferred Background" is preferred qualifications. So we can separate: Requirements (core) and Qualifications (preferred). Or we could treat "Core Requirements" as Requirements, and "Preferred Background" as Qualifications. - Skills: Not explicitly listed; maybe we can infer from requirements: writing, strategic instincts, operational discipline, data, influencing, people management, AI fluency. Those could be skills. But we need to only include Skills section if posting has real specific content for it. The posting does not have a dedicated "Skills" heading, but we could extract skills from the core requirements. However the instruction: "Prefer a few substantive sections over many thin ones." Might be better to not create a Skills section if not explicitly present. But we could include Skills as part of Requirements? The instruction says use headings for those categories if content exists. Since there is no explicit Skills section, we might omit it. - Benefits: Not mentioned in posting. No benefits details. So omit Benefits. - Pay: The posting includes "Base Pay Range: $200,000 - $257,500". Also mentions compensation ranges may differ for candidates in other locations. So we have pay info. So we can include Pay section with that. - Schedule: Not mentioned. Omit. - Qualifications: Could be the "Preferred Background" section. That's qualifications (preferred). So we can include Qualifications. - Requirements: Core Requirements list. - About the role: Could be the "What You'll Be Part Of" paragraph describing company culture and values. Also the initial company description. We'll combine into About the role. We must not include boilerplate like EEO, E-Verify, accommodations, privacy, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as written, but we can format into HTML. We need to use

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to avoid repeating job title as heading. We need to output only HTML fragment. Let's craft:

  About the role

  Circle (NYSE: CRCL) is one of the world’s leading internet financial platform companies, building the foundation of a more open, global economy through digital assets, payment applications, and programmable blockchain infrastructure. Circle’s platform includes the world’s largest regulated stablecoin network anchored by USDC, Circle Payments Network for global money movement, and Arc, an enterprise-grade blockchain designed to become the Economic OS for the internet. Enterprises, financial institutions, and developers use Circle to power trusted, internet-scale financial innovation. Learn more at circle.com. What You’ll Be Part Of Circle is committed to visibility and stability in everything we do. As we grow as an organization, we're expanding into some of the world's strongest jurisdictions. Speed and efficiency are motivators for our success and our employees live by our company values: High Integrity, Future Forward, Multistakeholder, Mindful, and Driven by Excellence. We have built a flexible work environment where new ideas are encouraged and everyone is a stakeholder.

  But note: 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. The company description is not job title, it's fine. Now Responsibilities: We need to capture the responsibilities described under "What you'll be responsible for" and the sub-sections. We can create a

  with each responsibility as
  • . However the responsibilities are paragraphs; we could keep them as

    inside

  • ? The rule: Use
    • for any list of duties/requirements/benefits. So we should convert each duty into list items. We need to preserve all substantive information; we can break into items. Let's extract responsibilities: From "What you'll be responsible for": - Drive two of our most visible functions shaping how Circle is understood — by employees, by candidates, and by the world. This is a highly cross-functional role for a strategic builder, operator, and storyteller who can shape programs, elevate standards, and partner across the business to deliver clear, credible, and compelling communications. - Play a central role in advancing Circle's internal communications approach across a distributed, global, remote-first workforce — helping employees stay informed, aligned, and connected to the company's strategy, priorities, and culture. - Advance Circle's employer brand, translating the employee experience into a strong, differentiated presence in the talent market. Then "What you'll work on" with subheadings: Internal Communications: - Partner with senior leaders and cross-functional stakeholders, including HR and Corporate Communications, to develop internal communications plans for major initiatives, organizational moments, and company priorities – not reactive support, but proactive counsel on what to say, when, and how. - Help shape how Circle communicates company strategy and OKRs internally, translating priorities into messaging that feels relevant and actionable for employees across functions and regions. - Build and scale internal communications programs in partnership with the Employee Experience Director and other cross-functional partners to support engagement, connection, and understanding across a distributed workforce. - Evolve and maintain the operational infrastructure that makes communications effective and scalable, including: editorial planning, channel governance, distribution practices, and measurement frameworks. - Support Circle's intranet strategy and evolution, serving as the business owner steering this work in partnership with IT. - Support sensitive, high-stakes, and change-related communications with sound judgment, strong stakeholder partnership, and attention to timing, tone, and employee impact. Employer Brand: - Drive the ongoing evolution of Circle's employee value proposition (EVP) in partnership with Talent Acquisition, People leadership, and Marketing, ensuring it reflects real employee experience and talent priorities. - Lead employer brand storytelling and content strategy across priority channels — careers content, employee stories, social content, recruiting campaigns, and talent-facing moments. - Partner with Talent Acquisition to strengthen candidate experience as a brand touchpoint, using survey insights, feedback, and market signals to identify opportunities for improvement. - Build and maintain employer brand intelligence infrastructure — including LLM/AI sentiment monitoring across major platforms and competitive benchmarking against talent peers. - Drive Circle's presence in employer awards, recognition programs, and talent-focused external opportunities that reinforce the company's reputation as a destination employer. - Build and own Circle's alumni network — selecting and launching the right platform, developing community strategy, and creating engagement touchpoints that keep former Circlers connected to the brand as advocates, referral sources, and potential boomerangs. - Ensure alignment between employer brand, people narrative, and broader corporate story so candidates and employees experience a consistent, authentic picture of Circle. Content & Cross-Functional Partnership: - Oversee the development of high-quality content across internal and talent-facing audiences — executive messaging, employee features, onboarding communications, event content, and campaign materials. - Partner closely with Corporate Communications, Talent Acquisition, Employee Experience, and the broader People & Workplace team to ensure messaging is coordinated, timely, and mutually reinforcing. - Drive key communications moments in the employee lifecycle, especially new hire and onboarding communications, in partnership with program owners. - Serve as a trusted thought partner and communications advisor to People & Workplace leadership, Corporate Communications and cross-functional stakeholders. - Bring a change-management lens to communications planning, helping teams communicate in ways that build understanding, reduce ambiguity, and support adoption. AI-First Operations: - Build repeatable, AI-enabled workflows across internal communications and employer brand that improve speed, consistency, and scale while preserving quality and editorial judgment. - Use AI tools across the communications lifecycle — research, synthesis, drafting, localization, content adaptation, measurement, and workflow design. - Contribute reusable prompts, templates, and automations to Circle's shared AI ecosystem so the function benefits from scalable ways of working. - Identify where automation can improve the operating model — recurring content workflows, campaign support, insights generation, and process coordination. - Model strong judgment around where AI should accelerate work and where human voice, sensitivity, or relationship context should remain central. We need to put these as list items under Responsibilities. Could group by subheadings? But we only have

      for section headings; we could include

      subheadings? Not allowed? The instruction only mentions using

      for section headings (e.g., About the role, Responsibilities, etc.). It doesn't forbid other headings, but to be safe we could just list all responsibilities as flat list items, preserving the content. However that may lose some grouping but still preserve all info. The instruction says preserve ALL substantive information; not necessarily grouping. So we can list each bullet as

      . That will be many items but okay. Alternatively we could keep the subheadings as

      inside

      ? But that would break the rule of using

      • for any list of duties/requirements/benefits. If we put a

        inside

      • , it's still a list item; that's okay. We could have

      • ...

      . That's fine. Simplify: We'll create
      and each responsibility bullet as
      • with the text. Now Requirements: Core Requirements list (numbered). We'll convert to
        • . List: - 12+ years of progressive experience in internal communications, marketing, HR communications, content strategy, or a related field, including meaningful experience operating in complex, cross-functional environments. - Exceptional writing and editorial judgment across formats, with the ability to adapt voice and messaging for executives, employees, candidates, and cross-functional audiences. - Strong strategic instincts paired with operational discipline — able to move between big-picture program design and the details required to make systems run well. - Strong track record driving internal communications programs at a fast-moving, global company — including