Senior Marketing Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About Nametag (company description) maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include sections like About the role (maybe "About the role" corresponds to role overview). Responsibilities (What you’ll do). Requirements/Qualifications/Skills (What You Bring). Benefits (We Offer). Pay and Schedule only if present: they mention Competitive salary, but not specific numbers; "Competitive salary" is vague but it's a statement of pay. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "We Offer Competitive salary". That's a statement about pay, albeit not specific. Is that enough? It says "Competitive salary" is a phrase; it's not placeholder like "commensurate with experience". It's a statement that they offer competitive salary. So we can include Pay section with that content. Schedule: they mention Flexible schedules: Work in your own time zone; we align key meetings across a shared window. That's schedule info. So we can include Schedule section. Benefits: they list Comprehensive health benefits, Flexible paid time off, Quarterly team off-sites and travel support, New computer hardware and equipment, Inclusive environment. So Benefits section. We must not repeat job title as heading. The page already shows it, so we don't add a heading for Senior Marketing Manager. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. There's no explicit application instructions besides maybe "We encourage candidates..." but that's part of qualifications. Keep. We need to use

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

  for prose. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  maybe include a short paragraph describing role overview. But we have "Role Overview As Senior Marketing Manager, you will own a meaningful share..." That's prose. We could combine About the role and Role Overview. We need to avoid duplication. Let's extract sections: - About the role: maybe a brief description: "Nametag is building the future of secure digital identity..." That's about company, not role. But we could still have About the role: maybe "The Role Nametag is hiring a Senior Marketing Manager to be one of the primary hands on our content engine..." That's description. We'll put that as

  . - Responsibilities: list of duties from "What you’ll do". That's a list of bullet points. We'll create

  • for each bullet. - Requirements / Qualifications / Skills: Could combine into one section "What You Bring". We'll list bullet points. - Benefits: list from "We Offer". We'll bullet. - Pay: mention Competitive salary. - Schedule: mention Flexible schedules: Work in your own time zone; we align key meetings across a shared window. Also mention Off-sites: quarterly in-person. But schedule section maybe include both flexible schedules and off-sites. We need to ensure we don't create sections with filler like "not specified". We have actual content. Let's craft. We'll need to ensure we don't repeat content unnecessarily. Let's draft HTML:

    About the role

    Nametag is hiring a Senior Marketing Manager to be one of the primary hands on our content engine; the person who can take a product update, a customer story, or an industry trend and turn it into a blog post, an email, a one‑pager, and a social thread. This role leans content: you should be, first and foremost, an excellent writer who's comfortable in a technical B2B space. It's also a generalist role where you'll move across channels and formats rather than owning one lane, which suits someone who wants breadth over deep specialization in any single channel.

    Responsibilities

    • Write and edit the majority of Nametag's recurring content: blog posts, thought‑leadership articles, email newsletters, and website copy updates.
    • Maintain a consistent voice and terminology across everything you touch, using Nametag's messaging and style guide as the working standard.
    • Turn technical product detail into copy a security, IT, or HR buyer will want to read, without losing accuracy.
    • Write and refresh customer‑facing collateral: one‑pagers, solution briefs, and customer stories.
    • Turn customer conversations and Customer Success input into concrete proof points and case studies.
    • Keep collateral current as messaging and product details change.
    • Write copy supporting Growth Marketing's campaigns across email, social, paid, and landing pages.
    • Adapt a single core message across formats and channels so campaigns feel coordinated.
    • Support A/B testing of messaging and creative with fresh copy variants.
    • Produce content supporting Nametag's conference presence and field events: talk‑track material, dinner and panel briefs, and pre‑ and post‑event follow‑up content.
    • Partner with Channel Partnerships on content for partner‑facing events and co‑marketing moments.
    • Own and maintain the marketing content calendar, coordinating inputs from Growth Marketing, Product Marketing, Design, and Sales.
    • Flag gaps and inconsistencies in existing content and messaging, and drive them to resolution.
    • Track content performance: engagement, email metrics, content‑influenced pipeline, in partnership with Growth Marketing, and use it to prioritize what to write next.

    What You Bring

    • ~8 years in B2B marketing, with some of that time in a content‑heavy role: content marketing, editorial, communications, or a marketing generalist role centered on writing.
    • Genuine comfort as a generalist – preferring to move across several channels well rather than owning one channel deeply.
    • Experience marketing to technical or security‑conscious B2B audiences; cybersecurity, IAM, or enterprise IT experience is a strong plus.
    • Ability to turn a customer conversation, a product spec, or a conference talk into content without losing what mattered in translation.
    • Working familiarity with marketing tools such as HubSpot, Google Analytics, and a CMS (Webflow or similar); light design‑tool comfort (e.g., Canva) is useful.
    • Strong organizational and project management skills.
    • A strong sense of ownership and a bias toward shipping.
    • Intellectual horsepower – quickly grasping complex technical and business concepts.
    • Kindness and integrity – earning trust is central to how we build relationships.
    • Bias for action – moving quickly to deliver impact and protect customers against fast‑moving threats.
    • Ownership mindset – caring about uptime and stability the way a founder cares about the product.

    Benefits

    • Competitive salary
    • Meaningful equity ownership
    • Comprehensive health benefits (medical, dental, vision)
    • Flexible paid time off
    • Quarterly team off‑sites and travel support
    • New computer hardware and equipment
    • An inclusive environment where your voice has impact and your work drives change

    Pay

    Competitive salary

    Schedule

    Flexible schedules: work in your own time zone; we align key meetings across a shared window. Quarterly team off‑sites for in‑person collaboration.

    We need to ensure we didn't duplicate "Competitive salary" both in Benefits and Pay. Benefits list includes Competitive salary as first bullet; Pay section repeats it. Might be considered duplication. The instruction: remove duplicated lines. So we should avoid duplicating the same content. We could either keep Competitive salary only in Benefits and not have a separate Pay section, or keep Pay but not duplicate in Benefits. Since Benefits section already includes Competitive salary, we could drop Pay section. However the rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Competitive salary, so we need a Pay section. But we should not duplicate the same line. We could keep Pay section with the statement, and Benefits section without the Competitive salary line (or we could keep both but it's duplication). Better to remove Competitive salary from Benefits list and keep it only under Pay. However Benefits section expects list of benefits; we can still list other benefits. Let's adjust. Benefits list: Meaningful equity ownership, Comprehensive health benefits, Flexible paid time off, Quarterly team off‑sites and travel support, New computer hardware and equipment, An inclusive environment where your voice has impact and your work drives change. Pay section: Competitive salary. Schedule section: Flexible schedules: work in your own time zone; we align key meetings across a shared window. Quarterly team off‑sites for in‑person collaboration. Now ensure we haven't missed any substantive info: The posting also mentions "Remote-first: Work from anywhere in the US. Our team spans Seattle, San Francisco, Ann Arbor, Denver, New York City, and beyond." That's location info; could be part of Schedule or maybe a separate section? Not required headings but we could include under Schedule or maybe a note. Since we have Schedule section, we could add that location info there. Also "Off-sites: We bring the team together once per quarter for in-person collaboration, often off-site in new places." Already covered. Also "Flexible schedules: Work in your own time zone; we align key meetings across a shared window." Already. Thus schedule section can include both. Now check for any other substantive info: "We Offer Competitive salaryMeaningful equity ownershipComprehensive health benefits (medical, dental, vision)Flexible paid time offQuarterly team off-sites and travel supportNew computer hardware and equipmentAn inclusive environment where your voice has impact and your work drives change" That's the benefits list we captured. Now ensure we didn't include boilerplate: The text includes "We encourage candidates from diverse backgrounds to apply, even if you don't meet every listed qualification." That's part of What You Bring; we kept it as a bullet? Actually we didn't include that explicitly. It's a statement encouraging diverse candidates. Should we preserve? It's substantive. Could add as a bullet under What You Bring: "We encourage candidates from diverse backgrounds to apply, even if you don't meet every listed qualification." Let's add. Also there is a line: "+ What We Value Intellectual horsepower. Quickly grasping complex technical and business concepts.Kindness and integrity. Earning trust is central to how we build relationships with customers and colleagues.Bias for action. We move quickly to deliver impact and protect our customers against fast-moving threats.Ownership mindset. You care about uptime and stability the way a founder cares about the product." We already captured those as bullets under What You Bring (intellectual horsepower, kindness and integrity, bias for action, ownership mindset). Good. Now check for any duplicated lines: We have not duplicated. Now ensure we used

    for section headings only. We have headings: About the role, Responsibilities, What You Bring, Benefits, Pay, Schedule. Good. We used

    • for lists. For About the role we used

      . For Responsibilities we used

      . For What You Bring we used
      . For Benefits we used
      . For Pay we used