Lead Marketer, AI Usage Automation
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines.
We need to preserve all substantive information.
We need to include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text.
We need to prefer few substantive sections over many thin ones.
Thus we can combine some sections: maybe "About the role" for role summary, "Responsibilities" for What You’ll Do, "Qualifications" for What You’ll Bring (required and nice-to-have), "Pay" for Pay & Benefits (cash compensation range), "Benefits" maybe separate if benefits described. The posting mentions benefits but not details; just says "Benefits are also an important piece... Explore the benefits and perks HubSpot offers". That's vague, not specific. So we should not create Benefits section if no specific benefits listed. The instruction: never create Benefits section unless posting actually states them. It mentions benefits but not specifics; it's generic. Likely we should not include Benefits section. Pay section: we have specific cash compensation range, so include Pay.
Schedule: not mentioned; no schedule details. So omit.
Skills: maybe not separate; could be part of Qualifications.
Thus sections: About the role (role summary), Responsibilities (What You’ll Do), Qualifications (What You’ll Bring), Pay (Annual Cash Compensation Range). Possibly also "About HubSpot" could be considered "About the company" but not in list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About HubSpot. So we should not create a heading for About HubSpot; maybe we can incorporate that into About the role? But it's about company, not role. The instruction: use those headings for section headings. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't say we cannot use other headings, but likely we should stick to those. The About HubSpot is generic company description; could be considered boilerplate? It's not navigation/legal/EEO but still maybe not required. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About HubSpot is not exactly boilerplate but could be considered generic marketing. However it's substantive info about company. Might be okay to keep as a paragraph without heading? The instruction: Output ONLY the HTML fragment. We could include a
about HubSpot without heading. But we need to preserve all substantive information. So we can include a paragraph about HubSpot after the sections. Thus final HTML:
About the role
... role summary ...
Responsibilities
- ... each bullet from What You’ll Do ...
Qualifications
- ... required qualifications ...
- ... nice-to-have qualifications ...
Pay
Annual Cash Compensation Range $122,400—$195,800 USD
... maybe also mention cash compensation includes base salary, on-target commission, annual bonus targets, eligibility for equity, overtime, etc. That's substantive. So include that paragraph. We should also include note about benefits? Not specific, so skip. We should also include note about remote/flexibility? That's under Pay & Benefits section after compensation. It mentions flexibility and connection, remote vs office, in-person onboarding requirements. That's about schedule/work arrangement. Could be considered Schedule? But we don't have a Schedule heading; we could include that info under Pay section or maybe under a separate "Schedule" heading if we treat it as schedule. The instruction: only create Schedule section if posting actually states them. It does state remote/flexibility and in-person requirements. So we could create a Schedule section with that info. However the allowed headings include Schedule. So we could create
Schedule
... details about remote/flexibility, in-person onboarding, etc.
. That seems appropriate. Thus we have sections: About the role, Responsibilities, Qualifications, Pay, Schedule. We need to avoid filler like "commensurate with experience". Not present. Now we need to extract the exact text. Role Summary: "Our mission at HubSpot is to help millions of organizations grow better. As Lead Marketer, AI Usage Automation, you’ll define how we use data, AI, and digital experiences to deliver timely, relevant guidance to customers at scale. You’ll own the strategy behind customer communications, from identifying the right customers and signals to designing the experience, experimentation approach, and measurement strategy. You’ll bring Marketing, Engineering, Analytics, and other partners together to turn that strategy into scalable customer experiences and communicate results and recommendations to senior leaders." We'll put that in a. Responsibilities: list each bullet from "What You’ll Do". Let's extract: - Define the strategy for AI-powered customer automation, including which customers to target, the signals that trigger outreach, the goal of each communication, and how each interaction fits into the broader customer journey. - Design the ideal customer experience and define the data inputs needed to deliver it, translating the strategy into clear briefs for engineering and technical partners and proposing improvements to the underlying architecture. - Bring technical and business stakeholders together to define requirements, establish ways of working, connect teams, and resolve competing priorities or points of friction. - Write and quality-assure email and in-app outputs, and review AI-generated prompt outputs to ensure experiences are clear, useful, accurate, and aligned with the intended customer outcome. - Own experiment design by defining hypotheses, partnering with Analytics to establish treatment and control groups, determining measurement windows, and defining how success will be evaluated. - Analyze program performance and experiment results to identify insights, recommend improvements, and determine the strategy for future iterations. - Build the executive narrative around program strategy, performance, and learnings through readout decks, QBR materials, and senior leadership briefings. - Develop repeatable approaches, frameworks, and learnings that help scale effective digital customer experiences across the organization. We'll put each as
- under same
- Define the strategy for AI-powered customer automation, including which customers to target, the signals that trigger outreach, the goal of each communication, and how each interaction fits into the broader customer journey.
- Design the ideal customer experience and define the data inputs needed to deliver it
Qualifications
? That's fine. Pay: The posting includes: "Pay & Benefits The cash compensation below includes base salary, on-target commission for employees in eligible roles, and annual bonus targets under HubSpot’s bonus plan for eligible roles. In addition to cash compensation, some roles are eligible to participate in HubSpot’s equity plan to receive restricted stock units (RSUs). Some roles may also be eligible for overtime pay. Individual compensation packages are tailored to your skills, experience, qualifications, and other job-related reasons. This resource will help guide how we recommend thinking about the range you see. Learn more about HubSpot’s compensation philosophy. Benefits are also an important piece of your total compensation package. Explore the benefits and perks HubSpot offers to help employees grow better. At HubSpot, fair compensation practices aren’t just about checking off the box for legal compliance. It’s about living out our value of transparency with our employees, candidates, and community. Annual Cash Compensation Range $122,400—$195,800 USD" We need to preserve all substantive information. So we can include a paragraph that includes all that info, but we should avoid fluff like "Learn more about HubSpot’s compensation philosophy." That's maybe boilerplate? It's a link suggestion; could be considered navigation? Might be considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Learn more about HubSpot’s compensation philosophy." is like a call to action; could be considered navigation? Might be considered boilerplate. Safer to omit that sentence. Also "Benefits are also an important piece..." is generic; we already decided not to create Benefits section; but we could keep that sentence in Pay paragraph? It's about benefits, but we are not making a Benefits section. Could keep as part of Pay paragraph? Might be okay. However the instruction: never create Benefits section unless posting actually states them. It does mention benefits generically; but we are not making a section. So we can keep that sentence in Pay paragraph as it's substantive about benefits being important. However it's vague. Might be considered filler? Not sure. Safer to include it as it's part of the posting. We also have "At HubSpot, fair compensation practices..." that's substantive. Thus Pay paragraph: combine all those sentences except the "Learn more..." and maybe the "Explore the benefits and perks HubSpot offers..."? That's also generic but could be kept. We'll keep it. Schedule: The posting includes: "At HubSpot, we value both flexibility and connection. Whether you’re a Remote employee or work from the Office, we want you to start your journey here by building strong connections with your team and peers. If you are joining our Engineering team, you will be required to attend a regional HubSpot office for in-person onboarding. If you join our broader Product team, you’ll also attend other in-person events, such as your Product Group Summit and other gatherings, to continue building on those connections. If you require an accommodation due to travel limitations or other reasons, please inform your recruiter during the hiring process. We are committed to supporting candidates who may need alternative arrangements" We should keep that as Schedule section. Now we need to output HTML fragment only, no markdown fences. Thus final output:About the role
Our mission at HubSpot is to help millions of organizations grow better. As Lead Marketer, AI Usage Automation, you’ll define how we use data, AI, and digital experiences to deliver timely, relevant guidance to customers at scale. You’ll own the strategy behind customer communications, from identifying the right customers and signals to designing the experience, experimentation approach, and measurement strategy. You’ll bring Marketing, Engineering, Analytics, and other partners together to turn that strategy into scalable customer experiences and communicate results and recommendations to senior leaders.