Head of Product Marketing
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They gave examples but we can include other headings if they exist? The posting includes "About Loop" and "About The Role". The instruction says 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. It doesn't forbid other headings like "About Loop". However they gave examples of headings we may use. Likely we should include sections: About the role (maybe combine About Loop and About The Role?), Responsibilities (What You'll Do), Requirements/Qualifications/Skills (About You), Compensation And Benefits (Pay and Benefits), Schedule (in-person role expectation). Also maybe "Benefits" separate from Pay. We need to preserve all substantive info: company description, role description, responsibilities list, requirements list, compensation range, benefits list, schedule expectation (in-person 4+ days per week, travel 5-15%). Also mention location (San Francisco or Chicago). Also mention reporting to Head of Marketing, team size, potential to expand. We must not include boilerplate like Equal Opportunity, cookie/navigation/legal/EEO etc. So drop the Equal Opportunity paragraph. We must not invent or summarize away detail. Must preserve all substantive info. So we need to include everything from the posting except boilerplate. Let's extract: Company description (About Loop): - Loop is industrializing services through AI, starting with global supply chain. - AI-native company solving systemic data problem in logistics. - Logistics Data Platform turns fragmented, unstructured data into trusted foundation for automation, financial clarity, decision intelligence at scale. - Serves >20% of Fortune 100, manages over $30B in supply chain spend, helps clients save hundreds of millions each year. - Recently closed $95M Series C, backed by Valor Equity Partners, Founders Fund, 8VC, Index Ventures, J.P. Morgan, >50 industry-leading angel investors. - Team expertise from Uber, Google, Microsoft, Meta, Amazon, Flexport, C3 AI, VMware, Box, UPS, C.H. Robinson. - Looking for builders. About The Role: - Head of Product Marketing to usher in next wave of innovations and growth. - Early stages establishing Loop as leader in new category Supply Chain AI, pushing past boundaries, still writing story. - Own messaging, positioning, buyer insight end to end; turn product/engineering into story a buyer can follow. - Run competitive intelligence, lead sales enablement, establish effective product launches in dynamic AI-driven world, build best-in-class practices with AI to balance efficiency with human voice. - Someone used to chaos and context-switching of product marketing will thrive. - Might be deep in spreadsheet of win-loss data, arguing with designer over one-pager layout, then sitting with product manager to understand feature. - Always more worth doing than time; deciding what to skip matters as much as deciding what to build. - Report directly to Head of Marketing on small team spanning product marketing, growth and ABM, and customer marketing, with design and brand support as needed. - Potential opportunity to expand team over time. - This is an in-person role based in San Francisco or Chicago, expectation of being in office 4+ days per week. - Ability to travel 5-15% of time for customer visits, industry events, team onsites. What You'll Do (Responsibilities): - Own positioning, messaging, buyer insight for Loop; build frameworks, personas, value propositions that sales, marketing, CS work from. - Convert technical product work into story anyone can follow; pull important pieces out of specs/roadmaps into decks, one-pagers, sales narratives that read cleanly and look like Loop. - Lead competitive intelligence; turn learnings into positioning calls, GTM strategy, input product team actually uses. - Support analyst and press relations engagements with thought leadership content; help decide how Loop can leverage these channels to grow mindshare at shippers. - Run product launches end to end, from first internal briefing through sales enablement and content that carries message into field. - Lead Loop's AI benchmark program; work with engineering to define what to test and how to run it; ensure results establish Loop as AI leader in supply chain. - Own Loop's core marketing collateral and assets; keep finding better ways to get that information in front of people who need it. - Build out vertical marketing story that feeds ABM campaigns, drawing on real customer insight to show Loop's value in each market we sell into. - Own Loop's value story; capture real customer results and turn features/solutions into outcomes buyers actually care about. - Figure out how product marketing itself should use AI and modern tools, so function keeps up as Loop's customer base and product line grow. About You (Requirements/Qualifications/Skills): - 8+ years in B2B product marketing, ideally at technical or data-heavy company, with work you've owned and can walk through in detail. - Curious about how things actually work. You don't need a technical degree, but you want to understand product well enough to explain it, and what AI can unlock genuinely excites you. - Writer and storyteller who can take something dense and technical and make it simple without making it generic. Notice when a sentence is doing real work and when it's AI-shaped filler, and care about how a deck or one-pager actually looks. - Comfortable holding a dozen threads at once, in a job where a morning in a spreadsheet can turn into an afternoon reviewing a designer's draft and then a call with a product manager about one specific feature. You'd rather make a fast, informed call than wait for certainty. - Experience building messaging frameworks and positioning from a blank page, not just maintaining what someone else already set up. - Hands-on experience with analyst relations, and comfortable turning outside perception into an internal point of view. - Familiarity with marketing and CRM systems, HubSpot preferred. - Strong communicator in writing and in person, who acts like an owner rather than waiting to be told what's next. - Big plus if you've marketed a technical, AI, or data product into enterprise buyers, or have supply chain, logistics, or fintech experience. Compensation And Benefits: - Base pay range $190,000-$230,000. This range reflects base pay Loop reasonably expects to pay for the position at time of hire. Actual compensation will depend on job-related factors, including experience, skills, qualifications, location, and business needs. - In addition to base salary, this role may be eligible for an annual performance bonus and equity. - This role is also eligible for Loop's benefits, including health, dental, and vision insurance, 401(k) match, paid time off, paid holidays, and parental leave. We should not include Equal Opportunity paragraph. We need to output HTML fragment only, no markdown fences. We need headings: About the role (maybe combine About Loop and About The Role?), Responsibilities (What You'll Do), Requirements (About You), Benefits, Pay, Schedule. But we also have location and reporting info; could be part of About the role section. We need to decide which headings to use. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings where applicable. We can also include other headings if needed? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings for those sections. We can also include other headings like "About Loop" maybe not needed. But we need to preserve all substantive info; we can put company description under About the role heading (maybe as a paragraph). Or we could have a separate "About Loop" heading but not in the list; but they didn't forbid other headings, just gave examples. However they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for those sections; we could also add other headings if needed, but better to stick to those.
Thus we can structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for those sections; we could also add other headings if needed, but better to stick to those.
Thus we can structure:
About the role
Company description + role overview (including reporting, location, schedule, travel).
Responsibilities
- ... each responsibility
Requirements
- ... each requirement
About the role
Loop is industrializing services through AI, starting with one of the world's most complex industries: the global supply chain. We're an AI-native company built to solve the systemic data problem that's held logistics back for decades. Our Logistics Data Platform turns fragmented, unstructured data into a trusted foundation that fuels automation, financial clarity, and decision intelligence at scale. Today, Loop serves >20% of the Fortune 100, manages over $30B in supply chain spend, and helps its clients save hundreds of millions of dollars each year. We recently closed a $95M Series C and are backed by leading investors including Valor Equity Partners, Founders Fund, 8VC, Index Ventures, J.P. Morgan,