GTM Partner Acquisition & Development

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, etc. Must preserve all substantive info. Must not invent or summarize away detail. Must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Pay: estimated base salary range $255,000 - $296,100, plus mention of equity, sales incentive pay, benefits. So we can include Pay section with that info. Schedule: mentions office-centric hybrid schedule: standard in-office days Monday, Tuesday, Thursday; option to work from home Wednesdays; Friday depends. So we can include Schedule section. Benefits: they list mental health, wellness & fitness benefits, career coaching & support, inclusive family building benefits, long-term savings or retirement plans, in-office culinary options. So we can include Benefits section. Now we need sections: About the role (maybe "About the role" corresponds to first paragraph describing role). Responsibilities: list of what you'll achieve (bullet points). Requirements/Qualifications/Skills: The posting has "About You" which includes qualifications, skills, etc. We need to decide how to split. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include multiple of those if content exists. We must not create thin sections. We have content for About the role, Responsibilities, Requirements (maybe combine About You into Requirements and Qualifications and Skills). Could separate: Requirements (mandatory), Qualifications (preferred), Skills (specific). But we need to avoid filler. The posting's "About You" includes bullet-like sentences: Demonstrates curiosity about AI tools..., Track record in channel partnerships..., Demonstrated success recruiting..., Deep familiarity..., Strong executive presence..., Strong grasp..., Collaborative mindset..., Data-driven approach... These could be considered Requirements or Qualifications. We could put them under Requirements (or Qualifications). Since we need to avoid thin sections, maybe we just have one section "Requirements" that includes all those. Or we could have "Qualifications" and "Skills". But we need to decide based on content: The posting doesn't explicitly separate required vs preferred; it's all "About You". So we could put them under "Requirements". Or we could split into "Qualifications" (track record, deep familiarity, strong executive presence, strong grasp) and "Skills" (curiosity about AI tools, collaborative mindset, data-driven approach). But that might be arbitrary. Safer to have a single "Requirements" section with all points. Then we don't need Qualifications or Skills sections (to avoid thin). The instruction says prefer a few substantive sections over many thin ones. So we will include About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's six sections. Now we need to format:

About the role

then

with prose from first paragraph(s) describing role. Then

Responsibilities

then

• for each bullet from "What You’ll Achieve". Then

  Requirements

  then
  • for each bullet from "About You". Then

    Benefits

    then
    • for each benefit listed. Then

      Pay

      then

      with salary range and note about equity, incentive pay. Then

      Schedule

      then

      with schedule details. We must not include boilerplate like EEO, etc. Also must not include "About Us" etc. The "About Us" section is boilerplate? It's about company but could be considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" is not explicitly listed as boilerplate but might be considered generic company description. However it's not EEO etc. It might be considered okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Us" is substantive about Asana. But the instruction also says prefer a few substantive sections over many thin ones. We already have many sections; adding another "About Us" would be another section. However the instruction list of possible headings does not include "About Us". It only lists those specific headings. So we should not add a heading not in list. So we omit "About Us". Also we must not repeat job title as heading. Good. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML fragment. Let's extract exact text. About the role paragraph: "The Channel and Ecosystems team is dedicated to accelerating Asana's growth and market reach through partnerships and fostering a thriving partner network. We build and nurture relationships with Channel Partners, Technology Partners, and Strategic Alliances to support Asana customers across geographies. In this GTM Partner Acquisition & Development role, you will be Asana's tip of the spear for identifying, recruiting, and activating a new generation of partners to drive our platform evolution from work management to an AI-powered operating system. You will turn promising strategic relationships into high-performing, revenue-generating partnerships across our global ecosystem. This role is based in our San Francisco office with an office-centric hybrid schedule. The standard in-office days are Monday, Tuesday, and Thursday. Most Asanas have the option to work from home on Wednesdays. Working from home on Fridays depends on the type of work you do and the teams with which you partner. If you're interviewing for this role, your recruiter will share more about the in-office requirements." But note schedule details are also in schedule section; we might want to avoid duplication. The About the role paragraph includes schedule details; but we will also have a Schedule section. To avoid duplication, we could keep the schedule details only in Schedule section and not repeat in About the role. However the instruction says preserve ALL substantive information; do not invent or summarize away detail. If we remove schedule details from About the role, we are omitting that info. But we could keep it in About the role and also have Schedule section; that would duplicate. Better to keep schedule details only in Schedule section and adjust About the role to exclude schedule sentences. But then we are removing some info from About the role. However we could keep the schedule details in About the role and not have a separate Schedule section; but we have schedule info, so we should include Schedule section. The instruction says include a section ONLY when the posting has real, specific content for it. It does not forbid duplication across sections, but we should avoid unnecessary duplication. However we must preserve all substantive information; duplication is not loss, it's okay but maybe considered redundant. I'd rather keep schedule details in Schedule section and keep About the role without schedule sentences. Let's see if we can rewrite About the role to exclude schedule sentences while preserving other info. Original About the role sentences: 1. The Channel and Ecosystems team is dedicated to accelerating Asana's growth and market reach through partnerships and fostering a thriving partner network. 2. We build and nurture relationships with Channel Partners, Technology Partners, and Strategic Alliances to support Asana customers across geographies. 3. In this GTM Partner Acquisition & Development role, you will be Asana's tip of the spear for identifying, recruiting, and activating a new generation of partners to drive our platform evolution from work management to an AI-powered operating system. 4. You will turn promising strategic relationships into high-performing, revenue-generating partnerships across our global ecosystem. 5. This role is based in our San Francisco office with an office-centric hybrid schedule. 6. The standard in-office days are Monday, Tuesday, and Thursday. 7. Most Asanas have the option to work from home on Wednesdays. 8. Working from home on Fridays depends on the type of work you do and the teams with which you partner. 9. If you're interviewing for this role, your recruiter will share more about the in-office requirements. We could keep sentences 1-4 and maybe 9? Sentence 9 is about recruiter sharing more about in-office requirements; that's also schedule-related but could be kept. However it's about interview process; maybe we keep it as it's not schedule specifics. But it's still about in-office requirements. Might be okay to keep. Thus About the role paragraph: combine sentences 1-4 and 9. Let's craft: "The Channel and Ecosystems team is dedicated to accelerating Asana's growth and market reach through partnerships and fostering a thriving partner network. We build and nurture relationships with Channel Partners, Technology Partners, and Strategic Alliances to support Asana customers across geographies. In this GTM Partner Acquisition & Development role, you will be Asana's tip of the spear for identifying, recruiting, and activating a new generation of partners to drive our platform evolution from work management to an AI-powered operating system. You will turn promising strategic relationships into high-performing, revenue-generating partnerships across our global ecosystem. If you're interviewing for this role, your recruiter will share more about the in-office requirements." That preserves substantive info except schedule specifics, which we will put in Schedule section. Now Responsibilities: from "What You’ll Achieve" bullet points: - Develop and execute a strategic partner recruitment plan targeting a new generation of GTM partners aligned to Asana's platform evolution. - Identify, evaluate, and recruit partners with proven capabilities in sales, technical solutioning, consulting, change management, and professional services. - Establish, grow, and advise C-level and VP-level relationships at target partner organizations to position Asana's platform vision. - Architect joint business plans defining shared revenue goals, go-to-market strategy, pipeline targets, and comprehensive enablement plans. - Drive tight field alignment between partner sellers and Asana's direct sales team for seamless co-selling and opportunity management. - Work cross-functionally with marketing, partner programs, customer success, and solutions engineering to build a surround-support model for partners. - Establish clear KPIs, performance scorecards, and QBR frameworks to track partner health, pipeline contribution, and partner-sourced/influenced revenue. We'll put each as

    • . Now Requirements: from "About You" bullet points (converted to sentences): - Demonstrates curiosity about AI tools and emerging technologies, with a willingness to learn and leverage them to enhance productivity, collaboration, or decision-making. - Track record in channel partnerships, partner development, or strategic alliances within SaaS or enterprise software. - Demonstrated success recruiting and activating new partners from scratch. - Deep familiarity with the GTM partner ecosystem (SIs, consultancies, technology advisors) and adjacent technology ecosystems (e.g., Atlassian, Salesforce, ServiceNow, Microsoft). - Strong executive presence with the ability to engage, advise, and present effectively to partner C-suites and senior leadership. - Strong grasp of AI-powered SaaS platforms and the ability to internalize and evangelize Asana’s Work Graph® and platform capabilities. - Collaborative mindset with experience working across marketing, sales, product, and customer success teams to drive growth. - Data-driven approach with experience building partner scorecards, QBR frameworks, and performance dashboards. Also note: "At Asana, we're committed to building teams that include a variety of backgrounds, perspectives, and skills, as this is critical to helping us achieve our mission. If you're interested in this role and don't meet every listed requirement, we still encourage you to apply." This is encouraging statement; we could include as a

      after the list maybe. It's substantive. We'll include as a paragraph after the list. Now Benefits: list: - Mental health, wellness & fitness benefits - Career coaching & support - Inclusive family building benefits - Long-term savings or retirement plans - In-office culinary options to cater to your dietary preferences Also note: "We strive to provide equitable and competitive benefits packages that support our employees