Principal Product Marketing Manager, Atlas

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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not include sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes compensation: "starting base salary range for this role is $180,000– $210,000 USD annually. This role is also eligible for commission based on performance and participation in Gainsight’s equity program." Also benefits: "We offer a comprehensive benefits package including fully covered medical premiums (employee-only), flexible PTO, 401(k) plan, dental and vision coverage, and remote work options. Additional benefits include a $10,000 lifetime fertility stipend and access to coworking spaces around the globe. You'll also enjoy dedicated Recharge Holidays - one long weekend each quarter to relax and reset." So we have Pay and Benefits sections. Schedule? Not mentioned besides remote role based in USA, occasional travel up to 10% but not schedule. So no schedule. We need sections: About the role (maybe "About This Role" heading). Responsibilities (What You'll Do). Requirements/Qualifications (What We're Looking For). Skills (Nice-to-have Skills Or Experience). Benefits (Why You’ll Love It Here includes compensation and benefits). Pay (maybe separate but we could combine? The instruction: prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they said include Pay section only if posting actually states them. It does state compensation. Could have separate Pay and Benefits sections. However they said prefer few substantive sections over many thin ones. Could combine Pay and Benefits into a single "Compensation and Benefits" section, but headings list includes Benefits and Pay separate. Might be okay to have both but they'd be thin? Let's see content: Pay: salary range, commission, equity. Benefits: medical, PTO, 401k, dental/vision, remote work, fertility stipend, coworking, recharge holidays. That's substantive enough for both. Could keep both. Also need to include "About This Role" as heading

About the role

(they said use

for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we will use those exact headings. We must not repeat job title. Must not include boilerplate like "We’re building the AI-driven future..." etc. That's introductory fluff but maybe considered substantive? It's repetitive and maybe not needed. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The opening sentences are marketing fluff but not boilerplate; they might be considered part of description but could be considered duplicated? It says "We’re building the AI-driven future of customer success, from retention to growth!" repeated twice. Might be considered duplicated lines; we should remove duplicated lines. Keep only one instance? Probably remove that fluff entirely as it's not substantive about role. The substantive content starts after "About This Role". So we will start with that. We need to preserve all substantive information: responsibilities, requirements, nice-to-have, compensation, benefits, culture etc. The "Why You’ll Love It Here" includes culture description; we could include that under Benefits or maybe a separate section? Not in headings list. Could incorporate into Benefits section as part of culture? But they said only use those headings. Could add a section for "About the company" but not in list. Better to incorporate culture into Benefits or maybe a separate "Why You’ll Love It Here" not in headings list - but instruction says 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 for sections; we could also add other headings if needed but better to stick to list. The culture description could go under Benefits as part of "Why You’ll Love It Here". Or we could create a separate section "Culture" but not in list; risk. I'll include it under Benefits as a paragraph. Now structure:

About the role

... description of role: founding product marketer for Atlas, remote USA, etc. Must preserve all substantive info from that section. We'll need to condense but not lose detail. Must not invent or summarize away detail. We need to preserve all substantive information; we can't omit details. However we can rephrase but must keep all info. That's tricky: we need to keep all details from the "About This Role" section. Let's extract that paragraph: "We’re looking for a full-time Principal Product Marketing Manager, Atlas, to join our Marketing team reporting to the Director, Product Marketing. This role is a remote role based in the USA. In this role, you'll be the founding product marketer for Atlas, our new AI-native services offering — a software-plus-services business that owns the outcome and manages renewal motions end-to-end on behalf of customers. Atlas has the velocity of a startup with the backing, distribution, and investment of Gainsight, and there is no existing playbook to work from: no established analyst category, no competitor to compare notes with, no precedent inside SaaS to borrow from. You'll be writing the playbook, not just for how we market this, but for how the entire motion gets built — pricing, packaging, delivery narrative, and go-to-market all at once. This is a senior individual contributor role: you'll act as a trusted delegate to our GM and executive leaders on all things Atlas, and you will personally write the narratives, build the decks, and author the positioning documents. You’ll bring a strong point of view on AI, not just in how we take agentic innovation to market but in how we execute product marketing, and you enjoy building the systems and processes to build an AI-native PMM team. The ideal candidate brings exceptional commercial writing, deep fluency in AI products and the AI buyer, and a demonstrated track record of taking a new product from zero to one, thriving in ambiguity." We need to keep all that info. We'll put in

. Next responsibilities: "What You'll Do" bullet list. We'll convert to

• . List items: - Own positioning, messaging, and the category narrative for Atlas end to end — including thought leadership about AI native services — and evolve that narrative as the market moves. - Serve as the definitive expert on the Atlas buyer: run primary research, customer and prospect interviews, and win/loss analysis in a market where no established analyst coverage or buyer's guide exists yet. - Build the go-to-market motion from scratch: launch strategy and cadence, pricing and packaging input, first-call narrative, demo storyline, and the enablement assets a seller needs to run a credible first meeting. - Partner with Product and Engineering as the voice of the market, translating buyer signals into roadmap influence and translating roadmap into commercial value customers actually care about. - Partner with Demand Generation and Content to build the demand engine for a product with no existing search volume, no established keyword set, and no installed base to market into. - Pioneer AI-native ways of working inside the PMM function — building the agents, skills, and workflows that let a small team operate at a much larger scale — and document them so the rest of the org can adopt them. - This role may require occasional travel (up to 10%) for team meetings, training, or company events. - This is not a complete list of responsibilities, and the scope of the role may evolve with the needs of the team and business. We need to keep all. The last two sentences maybe considered boilerplate? They are part of responsibilities description; we keep. Next requirements: "What We're Looking For" list. Items: - 10+ years of product marketing experience in B2B tech (SaaS preferred) - Exceptional positioning, writing, and storytelling. You make sophisticated technology concrete and relevant to both executive buyers and the practitioners - Demonstrated 0→1 product marketing experience: you have launched a new product or created a new category, not just marketed an existing one, and you can speak specifically to what you decided and what you got wrong. - Deep, hands-on fluency with AI products and the AI-forward buyer, including how you personally use AI tools to do your own work, not just how you market them. - Demonstrated comfort operating with wide latitude: you set your own objectives, choose your own methods, and take clear positions on ambiguous questions without waiting for direction. - Experience influencing product direction and executive decision-making as a peer, including with founders, GMs, or C-level stakeholders. - High comfort toggling between big-picture strategy and detailed execution, with a strong bias to action. You operate as a credible peer to executives — including in a General Manager or BU model — taking clear positions and driving alignment. - Genuine energy for undefined territory: you're motivated, not anxious, when there's no playbook. We'll put as
  • . Next nice-to-have: "Nice-to-have Skills Or Experience" list: - A knack for design and the ability to work fluently in Figma and Canva. - Startup experience, particularly at seed through Series B stage. - Experience in a product line or business unit operating semi-independently inside a larger company. - Experience vibe coding prototypes, landing pages, and product imagery. We'll put under Skills heading. Next compensation and benefits: We have Pay and Benefits sections. Pay: "Our Compensation and Benefits: At Gainsight, we believe great work happens when teammates feel fully supported. The starting base salary range for this role is $180,000– $210,000 USD annually. This role is also eligible for commission based on performance and participation in Gainsight’s equity program. Actual compensation may vary based on factors such as skills, experience, and location." We'll put under

    Pay

    ...

    Benefits: "We offer a comprehensive benefits package including fully covered medical premiums (employee-only), flexible PTO, 401(k) plan, dental and vision coverage, and remote work options. Additional benefits include a $10,000 lifetime fertility stipend and access to coworking spaces around the globe. You'll also enjoy dedicated Recharge Holidays - one long weekend each quarter to relax and reset." Also culture description: "Gainsight is a place where innovation is shaped through collaboration, curiosity, and a shared focus on solving real-world problems. With a growing suite of products across customer success, product experience, community, education, and AI-powered relationship intelligence, we continue to evolve with the needs of our customers. When people with diverse strengths, a strong sense of community, and true passion for our mission come together, they drive greater impact and create lasting value. What underpins it all is a culture that offers the stability, trust, and support that people need - not just to do the job, but to show up as themselves and feel connected to the work they do. Gainsters love working here for several reasons. Here are a few: Our Compensation and Benefits: ... Our Core Values: We are guided by our values and our mission to be living proof you can win in business while being Human-First. Learn more here. Our Growth Opportunities: From mentoring to career development opportunities, we’re passionate about helping our teammates learn, grow, and thrive. Our Parody Videos: No explanation needed. Just watch them here!" We need to preserve substantive info; we can include culture description under Benefits or maybe a separate section but we only have Benefits heading. We'll include all that after benefits paragraph as part of same

    or separate

    . It's substantive. We must not