Director - Demand Generation

We need to output HTML fragment with sections: About the role? The posting includes a description before "Job Description". We need to reformat into semantic HTML using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to extract content. Let's parse the posting. First paragraph: "Organizations everywhere struggle..." This is introductory fluff about Freshworks. Could be considered "About the role"? Actually it's about company. The job description starts after "Job Description". The "About the role" could be the paragraph describing the role: "Freshworks is looking for a senior demand generation leader to help build and modernize our scaled demand engine across our product portfolio. This role is for a hands-on operator and builder. ..." So we can put that under About the role. Responsibilities: The bullet list under "Key Responsibilities". We'll need to convert each line into

. Requirements: The posting has "Qualifications" section with bullet list. Also "What Success Looks Like" maybe could be considered part of Responsibilities? But we have sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have Qualifications: bullet list of required qualifications. Also "Preferred:" bullet list. We have Skills: maybe we can extract from qualifications: strong analytical skills, partnership skills, etc. But we could treat Qualifications as the qualifications section and maybe Skills as separate if there is explicit skills list. The posting does not have a separate "Skills" heading; but we could infer skills from qualifications. However instruction: include a section ONLY when posting has real, specific content for it. So we should not create a Skills section if not explicitly present. The posting does not have a "Skills" heading; but we could still create a Skills section if we have content like "Strong analytical skills..." but that is part of qualifications. Safer to not create Skills section unless there is explicit list. We'll omit Skills. Benefits: The posting mentions "Bonus/equity may be available." Also mentions inclusive teams, flexible thinking, opportunities to grow your career. That's somewhat benefits. But we need specific content: "Bonus/equity may be available." Also "At Freshworks, we have fostered an environment..." That's more EEO. We should not include boilerplate EEO. Benefits: we have "Bonus/equity may be available." Also maybe "flexible thinking, opportunities to grow your career". That's somewhat benefit. However we need to avoid boilerplate. The line "We're committed to building a workplace that reflects the diverse world we serve. At Freshworks, you'll find inclusive teams, flexible thinking, and opportunities to grow your career - while making work better for millions." That's a benefit-ish statement. Could be considered Benefits. But we need to see if it's specific enough. It's somewhat generic but still a benefit. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The inclusive teams line is not exactly EEO but could be considered culture/benefit. I'd include a Benefits section with that content. Pay: The posting includes "The annual base salary range for this position is $200,000 - $245,000 Base Salary. Compensation is based on a variety of factors including but not limited to location, experience, job-related skills, and level. Bonus/equity may be available." So we have Pay info. We'll include Pay section. Schedule: No mention of schedule (remote, full-time, etc). Not present, so omit Schedule. Now we need to output HTML fragment with

headings and appropriate

or

• . We must not repeat job title as heading. Not include Job ID. We must preserve all substantive information; do not invent or summarize away detail. We need to include About the role: the paragraph(s) describing role. Let's extract About the role text: Starting after "Job Description". The text: "Freshworks is looking for a senior demand generation leader to help build and modernize our scaled demand engine across our product portfolio. This role is for a hands-on operator and builder. You will own the day-to-day demand generation engine across channels, work closely with Revenue Marketing leadership on strategy and prioritization, and help rethink how demand generation should operate in an AI-forward company. We are not looking for someone to simply run the traditional demand gen playbook faster. We want someone who can question what is working, identify what is not, build better systems, and use AI and automation to fundamentally improve how we generate, qualify, nurture, and convert demand. You will partner closely with Sales, RevOps, Product Marketing, Analytics, and regional marketing teams to create an integrated demand engine that drives measurable pipeline and revenue impact." That's a good block. Now Responsibilities: list under "Key Responsibilities". Let's capture each bullet: - Own and execute the scaled demand generation roadmap across our product portfolio, balancing pipeline goals, audience priorities, channel performance, and budget. - Build and optimize always-on demand programs across SEM, SEO, AI search/GEO, content syndication, webinars, conversational marketing, lifecycle, nurture, and emerging channels. - Build AI-native and agentic workflows into the demand engine, including audience identification, campaign orchestration, lead qualification, personalization, optimization, and reporting. - Own performance across key demand generation metrics including MQCs/MQLs, SAOs, conversion rates, pipeline contribution, pipeline velocity, CAC, CPL, and channel efficiency. - Manage and continuously optimize multi-million-dollar budgets across channels and campaigns based on incremental pipeline impact and ROI. - Partner with Sales and RevOps on lead scoring, qualification, routing, SLAs, and handoff processes to improve conversion from demand through pipeline. - Partner with Product Marketing to ensure campaigns, messaging, and audience strategies are coordinated across product lines rather than fragmented. - Build a rigorous testing and experimentation culture, with clear hypotheses, measurement frameworks, and decisions on where to scale, optimize, or stop investment. - Lead and develop a high-performing demand generation team while remaining close enough to the work to diagnose problems and drive execution. - Evaluate and help evolve the demand generation martech stack, including marketing automation, intent data, conversational marketing, AI tools, and orchestration platforms. Also there is "What Success Looks Like:" which could be considered part of Responsibilities or maybe a separate section but we don't have a heading for that. Could incorporate into Responsibilities as a paragraph? But we should preserve all substantive information. The "What Success Looks Like:" block: "In this role, success means building a demand engine that is: Predictable in generating qualified pipeline Efficient in how budget is deployed Stronger at converting demand into sales opportunities Integrated across products, regions, and channels Increasingly automated and AI-native Measured on business outcomes, not activity volume" We could treat that as part of Responsibilities (maybe as a sub-section). Since we don't have a separate heading for success metrics, we can include it as a

  after the list or as part of Responsibilities. Probably best to add a

  after the list describing success. Now Requirements: The posting has "Qualifications" section with bullet list. Also "Preferred:" bullet list. We could treat "Qualifications" as Requirements section. The heading "Qualifications" is present; we could map that to Requirements heading. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Requirements and Qualifications as possible headings. But we should not duplicate; we need to decide which to use. The posting has a "Qualifications" heading with bullet list. It also has "Preferred:" under that. There's no separate "Requirements" heading. However we could treat the qualifications as Requirements. The instruction says we can use those headings; we should include a section only when posting has real specific content for it. Since there is a Qualifications heading, we can use that heading. But we also have a Requirements heading possible; we could omit Requirements if not present. However the posting does have a "Qualifications" section; we could map that to Requirements (since they are similar). But we have both headings available; we need to decide which to use to avoid duplication. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use all. We should include sections that match the content. Since the posting explicitly has a "Qualifications" heading, we should use that heading. We could also include a Requirements section if there is content like "You are equally comfortable..." but that's more profile. The "The Profile We Are Looking For" could be considered Requirements. Indeed after Qualifications there is "The Profile We Are Looking For". That is a paragraph describing desired traits. That could be considered Requirements. So we could have both Requirements and Qualifications sections. Let's see: The posting includes: "The Profile We Are Looking For You are equally comfortable looking at a pipeline dashboard, challenging a channel strategy, designing a new operating system, and getting into the details with the team.You are not overly attached to legacy marketing playbooks. You care about what actually creates an incremental pipeline and are willing to stop programs that no longer perform.Most importantly, you are a builder. You see demand generation as a system to continuously redesign and improve, not simply a collection of campaigns to run." That's more like personal attributes/requirements. Then "Qualifications Qualifications: 10+ years of experience..." So we could treat "The Profile We Are Looking For" as Requirements, and the bullet list as Qualifications. That seems appropriate. Thus we will have:

  About the role

  ...

  Responsibilities

  • ...
  ...

  What Success Looks Like: ...

  maybe as a

  after list.

  Requirements

  The Profile We Are Looking For: ...

  (maybe as a

  ).

  Qualifications

  • ...
  ...
  plus maybe Preferred as sublist? We could include Preferred as a separate
  under Qualifications with a note "Preferred:" but we need to preserve all detail. We could include Preferred items as separate
  with a preceding

  Preferred:

  or just include them in same list but maybe differentiate. Simpler: after the required qualifications list, add a

  Preferred:

  then another
  with preferred items. We must not invent or summarize away detail. So we need to copy the bullet points exactly. Let's extract required qualifications bullet points: - 10+ years of experience in B2B demand generation, growth marketing, or performance marketing, ideally in enterprise SaaS. - Significant experience owning scaled demand generation programs and measurable pipeline targets. - Experience managing multi-million-dollar marketing budgets and making channel allocation decisions based on performance and ROI. - Strong understanding of demand generation economics, including CPL, CAC, conversion rates, pipeline coverage, velocity, and incremental return. - Demonstrated experience building or implementing AI-enabled or agentic workflows within a marketing or demand generation environment. - Hands-on experience with marketing automation platforms such as Marketo, HubSpot, or Pardot and CRM platforms such as Salesforce. - Experience with intent and account intelligence platforms such as 6sense or Demandbase and conversational marketing platforms such as Qualified or Drift. - Strong analytical skills and the ability to independently diagnose performance issues using data. - Strong partnership skills across Sales, RevOps, Product Marketing, Analytics, and executive stakeholders. - Experience leading and developing demand generation teams. Now Preferred bullet points: - Experience in a scaled, sales-led enterprise SaaS company with a multi-product portfolio. - Experience operating in both enterprise and SMB/mid-market motions. - Experience at an AI-native company or building AI-native