Founding Marketing Lead

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. Use

for headings. Use

• for lists. Use

  for prose. No job title heading. No Job ID. Remove boilerplate. We need to parse the posting. First, there is an intro paragraph: "Meet Network Right Network Right is on a mission...". That's about company. Could be part of About the role? Actually "About The Role" heading appears later. The intro before that is company description. Could be considered part of 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 create sections accordingly. The "About The Role" heading appears in the posting. We'll output

  About the role

  and then content under it (prose). Then responsibilities: list of duties under "What You’ll Do". Then requirements/qualifications/skills: there is "What We Look For" and "Nice to Have". We need to separate into Requirements, Qualifications, Skills maybe. But we can combine? The instruction: prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements (including qualifications and skills), Benefits, Pay, Schedule. Possibly also Qualifications separate? But we can combine. We need to preserve all substantive information. Let's extract. Company intro: "Meet Network Right Network Right is on a mission to create a human-centric, innovative, next-generation world of IT. We are disrupting the IT service industry by offering custom solutions to each individual client. At Network Right, we're bridging the gap between IT and People by offering unique support based on the needs of growing businesses, and making employee lives easier through technology." That's substantive. Could go under About the role? Actually About the role should describe the role. The company description could be placed before About the role as a paragraph, but we need to follow headings. There's no heading for company overview. Could we include it as a paragraph before the first heading? The instruction: output ONLY the HTML fragment. It didn't forbid having a leading paragraph before any heading. It said use

  for section headings (e.g. About the role...). It didn't say we must start with a heading. So we can have a

  for company overview, then

  About the role

  etc. Now About the role content: after "About The Role" heading, there is paragraph: "You'll get exposure to a fast-moving, high-growth environment where your work directly drives pipeline and revenue. You'll have access to the CTO to build AI-powered marketing infrastructure, a strong existing brand foundation to build on, and a real opportunity to make inbound outpace outbound. We're a close-knit team working together to build something exceptional, and we move fast. The foundation is already here. We have brand assets, an active SEO program, a design agency relationship, and two years of SEO vendor history. What we do not have is a dedicated marketing owner to take all of it to the next level. This is not a zero-to-one role. It is a one-to-ten role. You will walk in, assess what is working, cut what is not, and build the inbound engine that consistently feeds the sales team. You will use data to make every decision, have the confidence to declare when a channel is exhausted and move on, and use AI as core infrastructure for drafting, research, production, and analysis, not as a tool you reach for occasionally. You are equal parts strategic brand architect and hands-on growth marketer. As comfortable in an analytics dashboard as you are writing a positioning doc or briefing a design agency. Focused on SQLs, not impressions. Obsessed with pipeline, not vanity metrics." That's substantive. We'll put that in

  under About the role. Now Responsibilities: under "What You’ll Do". List bullet points. We'll extract each bullet as

• . Let's list them: - Audit and evaluate existing vendor relationships including a design agency and a two-person SEO firm, determine whether they are delivering maximum value, and make the call on what to keep, optimize, or replace - Amplify existing SEO efforts and expand into new inbound channels that generate real pipeline for the sales team, not vanity metrics like impressions or MQLs - Run website experiments including pricing page layout, time-on-site optimization, and conversion rate improvements - Translate Network Right's story into clear, high-value narratives that speak directly to the pain points of IT decision makers, founders, and operations leaders at high-growth companies - Build and enforce brand consistency across every touchpoint: AI-generated content, email signatures, onboarding materials, sales collateral, and social - Enable the sales team to self-serve pre-approved, on-brand content using approved messaging trained on HubSpot data and recorded sales conversations - Own marketing KPIs and performance reporting; analyze the last two years of SEO and inbound data to surface the growth opportunities we have not acted on yet - Build reporting that clearly shows what is working, what is not, and where to invest next — not vanity dashboards, pipeline and revenue dashboards - Leverage AI tooling including Claude and ChatGPT as core infrastructure for content generation, traffic analysis, workflow automation, and performance optimization - Drive content strategy including case studies, client success stories, and social posting to build domain reputation and authority - Own demand gen strategy, messaging and positioning, growth infrastructure, content, experimentation, and performance reporting end to end - In your first 30 to 60 to 90 days: audit vendors, branding, and inbound performance; analyze two years of SEO progress; establish KPIs; begin identifying channel expansion opportunities; and measure success by workflows transformed, not just tasks completed That's a lot. We'll put them in
  • . Now Requirements/Qualifications/Skills: Under "What We Look For" and "Nice to Have". Let's extract. What We Look For: - 5 to 7 years of marketing experience in a services-oriented business; HR tech, PEOs, HRIS systems, or recruiting tools strongly preferred given the matching buyer persona of HR leaders, engineering leaders, and founders - You use data to make decisions and can prove channel performance before you scale it - You have managed or evaluated external vendors and know how to get more out of them or replace them when they are not delivering - Deep hands-on familiarity with SEMrush, Google Analytics, HubSpot, Webflow, Clay, Apollo, and Google My Business - You understand how SEO, content, social, and sales enablement connect and can own all of it without losing the thread - You are sales-led in your thinking: SQLs matter, impressions do not - You run marketing the way the best operators run their businesses: AI as core infrastructure for drafting, research, production, and analysis, not a tool you reach for when you have extra time - Intellectual curiosity and an analytical mindset that can fact-check messaging and understand the business well enough to ensure accuracy in everything that goes out - Comfortable being a one to two person function in the short term and owning the output personally before building the team around you Nice to Have, but don't let this stop you from applying!: - Background in HR tech, PEOs, HRIS systems, or recruiting tools where the primary buyer is HR or engineering leadership - Experience building sales enablement content and training a sales team to use it independently - Familiarity with building AI-powered marketing infrastructure from scratch - Experience managing a marketing function through a period of rapid company growth We need to decide sections. Could have Requirements (mandatory) and Qualifications (nice-to-have) or Skills. But we can combine into one section "Requirements" containing both required and nice-to-have, maybe split with headings? But we only allowed headings from list. Could we add a subsection? Not allowed. Better to have separate sections: Requirements (mandatory), Qualifications (nice-to-have), Skills (tools). But we have many skill mentions (tools). Could create Skills section for tools: SEMrush, Google Analytics, HubSpot, Webflow, Clay, Apollo, Google My Business. Also AI tooling familiarity. But the instruction: prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section "Requirements". And Skills maybe separate? But we could include skills within Requirements as bullet points. Let's think: The posting includes "What We Look For" (requirements) and "Nice to Have". Could treat both as requirements section with sub-bullets? But we need to preserve all info. We can have a section

    Requirements

    with a

    intro then

    • for each bullet, marking nice-to-have maybe with a note. But we must not invent or summarize away detail. We can include note "(Nice to have)" inside the li. Alternatively, we could have two sections: Requirements and Qualifications. That's two sections, still few. Let's do that: Requirements (mandatory) and Qualifications (nice-to-have). Skills maybe part of Requirements (tools). But we could also have Skills section for tools. However that may be many sections. Let's decide: We'll have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 6 sections. That's okay. Now Benefits: Under "What We Offer". List items with emojis but we need to preserve substance. Let's extract: - Health Benefits: 100% covered health, dental and vision insurance for you, 50% for dependents - Paid Parental Leave - HSA/FSA eligibility - Rewards & Recognition: 401(k) + 4% company matching, Annual Bonus Program - Balance: Flexible Time Off - Learning & Development: Flexible certification and learning stipends and reimbursements - Culture: Biannual company retreats, Social events, Wellbeing events and programs - Extras: Home internet and mobile reimbursement, Monthly meal stipend, Commuter benefits, Onsite meals and snacks, Dog-friendly office We'll put as
      • . Pay: "Compensation: $150,000-$180,000; we determine your starting salary based on location, the depth of your experience, and how closely your skillset aligns with our team's needs". That's substantive. We'll put in

        under Pay. Schedule: "Location: San Francisco preferred or New York City; must be within commuting distance to our hubs Schedule: Monday-Friday, onsite 4 days a week; this is not a remote/hybrid position Sponsorship: Network Right is not currently able to provide visa sponsorship Applicants must be authorized to work in the United States without sponsorship now or in the future". This includes location, schedule, sponsorship. We need to include Schedule section only if posting actually states them. It does state schedule: Monday-Friday, onsite 4 days a week; not remote/hybrid. Also location is given. Sponsorship is also there but maybe not needed. We'll include Schedule section with that info. Could also include location in Schedule? Might be better to have separate Location section but not in allowed headings. We could incorporate location into Schedule paragraph. Or we could put location in Schedule section as part of description. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have Schedule section with content: "Location: San Francisco preferred or New York City; must be within commuting distance to our hubs. Schedule: Monday-Friday, onsite 4 days a week; this is not a remote/hybrid position. Sponsorship: Network Right is not currently able to provide visa sponsorship; applicants must be authorized to work in the United States without sponsorship now or in the future." That's substantive