Software Alliances Director, Americas

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as needed. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also must not create sections with placeholder text like "commensurate with experience". Must include only sections where posting has real specific content. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "The Software Alliances team at Canonical works with leading software companies to optimize and enable their products with Ubuntu and other Canonical software. We develop joint product roadmaps, drive delivery, and formulate go-to-market plans, content and processes, enabling differentiated offerings and robust product life-cycle support anchored to best-in-class Canonical products." Then: "The successful candidate is someone who has demonstrated success in business development or product management, both as a leader and an individual contributor with major partners. If you are someone who is passionate about open source, can navigate complex new technical challenges, learn quickly, and architect solutions and strategies across global teams, this challenging role is for you. This role is ideal for professionals with 7+ years of experience." Location: "Location: This role will be based remotely in the Americas region." Then "The role entails" bullet list: - Working with major partners to positively impact their technology strategies - Collaborating with partners' Product, Engineering, Alliance and Marketing teams - Identifying partner requirements, evaluating gaps, and identifying opportunities for strategic growth at Canonical - Coordinating with Marketing and Product on messaging, content creation, and launch plans. - Creating partner- and customer-facing materials such as reference architectures, joint blueprints, webinars, presentations, videos, and white papers. - Up to 25% travel, including internationally, for internal conferences and to drive partnerships in person. Then "What we are looking for in you" list: - Exceptional academic track record from both high school and university, or a compelling narrative about your alternative chosen path. - Bachelor's degree in science, technology and/or engineering. - Experience in software development or product management. - Demonstrated cross-functional leadership and influence - Excellent communication skills across all levels of stakeholders - from individual contributors to the C-suite - Ability to grasp complex technology and concepts, whilst synthesizing key points. - Ability to think and work at both strategic and tactical levels. - Disciplined and self motivated for a remote-first workplace environment. Then "Nice-to-have Skills And Experience": - Post-graduate degree in science, technology or engineering field. - Experience with open source software and open source business models. - Understanding of marketing and go-to-market strategy. - Working knowledge of OEM and Software vendor go-to-market motions. Then "What We Offer Colleagues" paragraph: includes compensation, benefits, etc. We need to decide sections: About the role (intro), Responsibilities (the role entails list), Requirements (what we are looking for in you), Qualifications (maybe education?), Skills (nice-to-have?), Benefits (What We Offer Colleagues), Pay (maybe mention compensation?), Schedule (maybe location/remote? travel?). We must not create sections with placeholder text. We need actual content. Let's map: - About the role: first paragraph(s) describing team and role overview. Could include location? Location maybe separate but could be part of About the role. But we have a specific location line; we could include it in About the role as a sentence. - Responsibilities: the bullet list under "The role entails". That's clear. - Requirements: the list under "What we are looking for in you". That's required qualifications. - Qualifications: maybe the education bullet (Bachelor's degree) and exceptional academic track record? But those are already in requirements. Could separate: Qualifications: Bachelor's degree, exceptional academic track record. But we already have them in requirements; we could keep them there. However we need to avoid duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." We can keep them in Requirements; we could also have a Qualifications section for education and nice-to-have? But we have Nice-to-have Skills And Experience separate. Better to follow typical sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Let's extract: About the role: description of team and what they do, plus location and ideal experience. Responsibilities: bullet list of role entails. Requirements: maybe the mandatory requirements: Exceptional academic track record, Bachelor's degree, Experience in software development or product management, Demonstrated cross-functional leadership and influence, Excellent communication skills, Ability to grasp complex technology, Ability to think strategic/tactical, Disciplined self-motivated remote-first. Qualifications: maybe the education? But we already have Bachelor's degree in requirements. Could treat Qualifications as education and experience? But we might duplicate. Perhaps we can put Qualifications as the education (Bachelor's degree) and maybe the 7+ years experience. However the 7+ years experience is mentioned earlier: "This role is ideal for professionals with 7+ years of experience." That could be a qualification. Skills: Nice-to-have skills and experience. Benefits: What We Offer Colleagues paragraph. Pay: The posting mentions compensation: "We consider geographical location, experience, and performance in shaping compensation worldwide. We revisit compensation annually (and more often for graduates and associates) to ensure we recognize outstanding performance. In addition to base pay, we offer a performance-driven annual bonus or commission." That's specific content about pay. So we can create a Pay section with that. Schedule: maybe location/remote and travel? The posting mentions location remote in Americas, up to 25% travel. That could be Schedule (remote work, travel). Could also be part of About the role. But we need to decide if we have enough content for Schedule section: we have location remote, up to 25% travel. That's specific. So we can create Schedule section with that. We must avoid creating sections with placeholder text like "commensurate with experience". We have actual content. Now we need to output HTML fragment with

headings for each section we include, and

• for lists,

  for prose. We must not include any other tags like or . Just the fragment. We must not include boilerplate like EEO etc. At the end there is "Canonical is an equal opportunity employer..." which is boilerplate; we must remove it. Also remove duplicated lines (maybe none). Remove application instructions (none present). Remove cookie/navigation/legal etc. Now craft sections:

  About the role

  The Software Alliances team at Canonical works with leading software companies to optimize and enable their products with Ubuntu and other Canonical software. We develop joint product roadmaps, drive delivery, and formulate go-to-market plans, content and processes, enabling differentiated offerings and robust product life-cycle support anchored to best-in-class Canonical products. The successful candidate is someone who has demonstrated success in business development or product management, both as a leader and an individual contributor with major partners. If you are someone who is passionate about open source, can navigate complex new technical challenges, learn quickly, and architect solutions and strategies across global teams, this challenging role is for you. This role is ideal for professionals with 7+ years of experience. Location: This role will be based remotely in the Americas region.

  That seems fine.

  Responsibilities

  • Working with major partners to positively impact their technology strategies
  • Collaborating with partners' Product, Engineering, Alliance and Marketing teams
  • Identifying partner requirements, evaluating gaps, and identifying opportunities for strategic growth at Canonical
  • Coordinating with Marketing and Product on messaging, content creation, and launch plans.
  • Creating partner- and customer-facing materials such as reference architectures, joint blueprints, webinars, presentations, videos, and white papers.
  • Up to 25% travel, including internationally, for internal conferences and to drive partnerships in person.
  Note: travel appears also in Schedule but we included in Responsibilities; maybe better to move travel to Schedule. But we can keep travel in Responsibilities as it's part of role entails. However we also need Schedule section for location/remote and travel? Could duplicate. Better to keep travel in Responsibilities and Schedule only for location/remote? But Schedule section should reflect schedule specifics like remote work, travel percentage. Since we already have travel in Responsibilities, we could still have Schedule for remote work location. But we might duplicate travel. Let's think: The role entails list includes travel bullet. That's a responsibility (travel). Schedule could be about remote work and maybe travel expectation. But we can keep travel in Responsibilities and Schedule just mention remote work location. However the location sentence is already in About the role. So maybe we don't need a separate Schedule section; we could omit Schedule if no distinct content beyond what's already covered. The instruction: "Prefer a few substantive sections over many thin ones." So we might skip Schedule if not needed. But we need to decide if we have enough content for Schedule separate from About the role. The location sentence is already in About the role; we could keep it there. So we may not need Schedule. Pay: we have content. Benefits: we have content. Skills: Nice-to-have. Qualifications: maybe we can combine education and experience? But we already have 7+ years experience in About the role. Could put that in Qualifications. Let's think. We have About the role includes ideal experience 7+ years. Could move that to Qualifications. But we already have it in About the role; it's okay to have it there. However we might want to avoid duplication. But it's not duplicated elsewhere. It's fine. Qualifications section could contain: Bachelor's degree in science, technology and/or engineering; Exceptional academic track record from both high school and university, or a compelling narrative about your alternative chosen path. That's two items. But we already have those in Requirements list. If we move them to Qualifications, we need to adjust Requirements to not include them. Let's see: Requirements list currently includes those plus experience, leadership, communication, ability to grasp tech, strategic/tactical, disciplined self-motivated. If we move education items to Qualifications, Requirements would be: Experience in software development or product management; Demonstrated cross-functional leadership and influence; Excellent communication skills across all levels of stakeholders; Ability to grasp complex technology and concepts, whilst synthesizing key points; Ability to think and work at both strategic and tactical levels; Disciplined and self motivated for a remote-first workplace environment. That seems reasonable. Thus we have: - About the role: team description, location, maybe mention 7+ years experience? We could keep 7+ years experience in Qualifications instead. Let's move 7+ years experience to Qualifications as well (maybe as a qualification). But the posting says "This role is ideal for professionals with 7+ years of experience." That's a qualification/experience requirement. So we can put that in Qualifications. Thus About the role will be just the team description and maybe location? Location we could keep in About the role or Schedule. Since we are not making Schedule, we can keep location in About the role. Thus About the role paragraph: "The Software Alliances team at Canonical works with leading software companies to optimize and enable their products with Ubuntu and other Canonical software. We develop joint product roadmaps, drive delivery, and formulate go-to-market plans, content and processes, enabling differentiated offerings and robust product life-cycle support anchored to best-in-class Canonical products. Location: This role will be based remotely in the Americas region." We could also include the statement about successful candidate etc? That seems more like requirements. Actually the paragraph after team description: "The successful candidate is someone who has demonstrated success in business development or product management, both as a leader and an individual contributor with major partners. If you are someone who is passionate about open source