Senior Manager, Brand Marketing

We need to output HTML fragment with sections: About the role (but the page already shows job title, we shouldn't repeat job title). The posting includes "About CertifyOS" (company description) and "About The Role". We need to include sections only when there is real specific content. We should include headings: About the role? Actually they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule if content exists. We need to parse the posting for content. The posting includes: - About CertifyOS (company description) – maybe we can treat as "About the company"? Not in list. But we could include as a

before sections? The instruction: "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 the company maybe as intro. But they want sections only when posting has real specific content. The posting includes many responsibilities under "What You'll Do" with subheadings: Brand Development & Identity, Content Strategy & Production, Owned Channels: Podcast, LinkedIn & Newsletter, Events & Sponsorships, Employer Brand & Internal Communications. Those are responsibilities. Also "What Success Looks Like" includes metrics – could be considered as "Requirements"? Actually it's success criteria, maybe we can treat as "Requirements" or "Qualifications"? There's also "What You'll Need" with Must-Have Experience and Preferred Experience – that's qualifications. Also benefits section: "Benefits Of Working At Certify" includes health insurance, unlimited PTO, etc. So we can create Benefits section. Pay and Schedule: not mentioned. So we should not include Pay or Schedule sections. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we can list each bullet under appropriate headings? The instruction: "Use
  • for any list of duties/requirements/benefits, and

    for prose." So we need to convert lists to

    • . For prose paragraphs, use

      . We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes an EEO statement at end: "We are an equal opportunity employer..." and accommodation request. That's boilerplate; we should remove it. Also the line about pay transparency maybe not boilerplate but it's part of benefits? It says "We are also committed to pay transparency and foster an open culture where compensation conversations are encouraged and respected." That's not a benefit per se but could be included in Benefits? It's more culture. Might keep as prose under Benefits? But it's not a benefit like insurance. Might be considered part of culture; but we can include as a

      under Benefits or maybe as a separate section? Not in list. Probably we can include as a

      under Benefits or as a general paragraph after Benefits. We must not include duplicated lines. Let's extract content: Company description (About CertifyOS): "CertifyOS is building the data infrastructure that powers modern healthcare. Today, healthcare organizations rely on fragmented and outdated provider data. This creates unnecessary administrative work, regulatory risk, and higher costs across the system. We’re solving that problem. Our API-first platform automates provider licensing, enrollment, credentialing, and network monitoring by connecting directly to hundreds of primary data sources. We help healthcare organizations maintain accurate, compliant, and reliable provider networks at scale. Our vision is simple: One API. One provider ID. Frictionless provider data. We’re backed by leading investors and built by a team with deep experience in provider data systems. At CertifyOS, we value authenticity, accountability, collaboration, results, and openness to feedback. We’re building a high-ownership team focused on solving real infrastructure problems that impact millions of patients." That's substantive; we can put as a

      maybe under a heading "About CertifyOS"? Not in list but we could just put as introductory paragraph before sections. Then "About The Role" heading: we can treat as a section heading "About the role". Under that we have description: "We are seeking a Senior Manager of Brand Marketing to own Certify's brand presence, content output, and audience-building channels end-to-end. This is a high-impact, creative-meets- strategic role for someone who can simultaneously build a cohesive brand identity and operate the full content engine that brings it to life — from thought leadership to LinkedIn, events, podcasts, employer brand, and corporate communications. You will help define how Certify shows up in the market — shaping perception among healthplan buyers, potential hires, and industry stakeholders. This role requires equal parts brand vision and content discipline. You will own the editorial calendar, manage all owned channels, and ensure every piece of content is consistent, compelling, and connected to business objectives." We can put that as prose under

      About the role

      . Then "What You'll Do" with subheadings. We can treat each subheading as a subsection? But we only have h3 for section headings; we could use

      for each major section like Responsibilities, and then inside we can have

      ? Not allowed? The instruction only mentions using

      for section headings (list). It doesn't forbid other headings, but to be safe we can just use

      for each major section and use

      • for lists. For subheadings we could use or

        with bold. But we need to preserve content. Simplify: Create a section

        Responsibilities

        and under it list all duties as
        • items, preserving the details. We can break down each bullet into separate
        • items, each containing the detailed description. Similarly,

          Qualifications

          (or Requirements) for "What You'll Need" with Must-Have Experience and Preferred Experience. Benefits section:

          Benefits

          with list. We should not include Pay or Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. Now extract responsibilities details: Under "What You'll Do": Brand Development & Identity: - Steward Certify's brand identity — including voice, tone, visual language, and positioning ensuring consistency across all internal and external touchpoints. - Maintain and help evolve the living brand guidelines system — covering written style, design standards, messaging hierarchies, and channel-specific adaptations. - Lead periodic brand audits to evaluate consistency, resonance, and market perception, using findings to evolve the brand as Certify grows. - Partner with Product Marketing and leadership to ensure brand positioning is tightly integrated with Certify's market strategy and competitive narrative. Content Strategy & Production: - Own the master content strategy and editorial calendar, ensuring all content reinforces CertifyOS’ brand narrative, category POV, campaign priorities, and audience insights across channels. - Develop distinctive thought leadership that translates market trends, customer pain points, regulatory pressure, and product strategy into compelling content for health plan executives and provider operations leaders. - Lead the creation of high-quality content across articles, blogs, LinkedIn, newsletters, video scripts, webinars, event presentations, white papers, contributed industry pieces, and sales enablement assets. - Build a repeatable content production engine using AI tools, internal SMEs, customer insights, and external partners to scale output without sacrificing quality, originality, or editorial rigor. - Partner with Marketing, BD, Product, Customer Success, and the executive team to ensure content directly supports pipeline creation, customer education, product launches, events, and market authority. Owned Channels: Podcast, LinkedIn & Newsletter: - Own and operate Certify's podcast — from guest strategy and topic selection to production workflow, episode publishing, and audience growth. - Drive Certify's LinkedIn presence as a brand-building channel — developing a content cadence, growing follower engagement, and managing both company page and executive ghostwriting programs. - Build and grow Certify's owned newsletter — developing the editorial voice, subscriber growth strategy, and content rhythm that turns subscribers into advocates. - Track channel-level performance metrics and use data to continuously optimize content type, frequency, and distribution strategy. Events & Sponsorships: - Own Certify's events strategy — identifying, evaluating, and executing on industry conferences, roundtables, webinars, and proprietary events that build brand visibility and pipeline. - Manage event logistics end-to-end: booth presence, speaker submissions, session content, on-site materials, and post-event follow-up campaigns. - Build Certify's own event programming — from customer advisory board meetings to hosted industry roundtables — that positions Certify as a convener in the PDM space. Employer Brand & Internal Communications: - Develop and execute Certify's employer brand strategy — defining what it means to work at Certify and translating that into recruiting content, Glassdoor presence, careers page, and social storytelling. - Partner with People & Talent to build a talent marketing program that attracts mission- driven candidates who align with Certify's culture and values. - Own corporate communications — drafting executive announcements, company updates, investor communications, and press releases in Certify's voice. - Build internal brand engagement programs that reinforce culture and ensure employees are proud ambassadors of the Certify brand externally. What Success Looks Like: - Brand Consistency: A documented brand guidelines system live within 60 days; 100% of external content passing brand review within 90 days. - Content Velocity: Weekly content output across LinkedIn, blog, and newsletter sustained at scale; editorial calendar planned 4+ weeks ahead. - Podcast Growth: Podcast launched within 90 days; 10+ episodes published within 6 months with measurable audience growth quarter over quarter. - Channel Performance: LinkedIn follower growth ≥20% quarter over quarter; newsletter open rates above industry benchmark; event ROI tracked and reported. - Employer Brand: Certify employer brand presence established on LinkedIn and Glassdoor within 60 days; measurable improvement in qualified inbound applications. We could treat Success Looks Like as part of Responsibilities or maybe as a separate section "Goals". But not in list. Could include under Responsibilities as additional bullets. Now Qualifications: Must-Have Experience: - 6–10+ years in brand marketing, content strategy, or editorial leadership — with a track record of building or transforming a brand at a healthcare or technology company. - Demonstrated experience owning content operations at scale — building editorial systems, managing production workflows, and maintaining quality across high-volume output. - Hands-on experience managing owned media channels: LinkedIn company presence, newsletters, podcasts, or video programs. - Strong writing and editorial skills — able to produce excellent content yourself and set the standard for others. - Proven ability to translate business goals into brand narratives and content strategies that resonate with B2B buyers and talent audiences alike. Preferred Experience: - Background in healthtech, health plan operations, or B2B enterprise SaaS with complex buyer audiences. - Experience with AI-driven content workflows — using tools like LLMs, automation platforms, or content intelligence software to scale output efficiently. - Experience managing or contributing to executive thought leadership programs and ghostwriting programs. - Familiarity with demand generation and ABM — understanding how brand content feeds pipeline and measuring brand's contribution to revenue. Also there is "Our Research & Culture Principles" which is more about company values; could be omitted as boilerplate? It's not exactly boilerplate but it's about culture. Might be considered part of "About CertifyOS"? Could include as a

          under About CertifyOS? But it's not in the list of sections; we could just include as a paragraph after About CertifyOS. But we need to preserve ALL