International Partnerships Manager

We need to output HTML fragment with headings

for 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 preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not invent or summarize away detail. We need to parse the posting. Let's extract sections: - About Onebrief (company description) maybe "About the role"? Actually "About Onebrief" is company description. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. The posting includes: "Consequential Work. Dedicated People. About Onebrief ..." then "Why This Role Exists", "What You’ll Do", "Minimum Qualifications", "Preferred Qualifications", "Indicators of Success", "Tools, Systems & Technologies", "Notice to Third Party Recruitment Agencies". Also "Willingness and ability to travel" etc. We need to decide which sections to include: About the role (maybe combine "Why This Role Exists" and "What You’ll Do"? Actually "About the role" could be description of role. We have "Why This Role Exists" and "What You’ll Do". Could combine into About the role. Responsibilities: from "What You’ll Do" bullet points. Requirements: Minimum Qualifications. Qualifications: Preferred Qualifications? Or maybe Qualifications includes both minimum and preferred? Usually Requirements = minimum qualifications, Qualifications = preferred. We'll follow that. Skills: maybe from "Tools, Systems & Technologies" or from "Indicators of Success"? Could also include "Executive Communication" etc. But we need to decide. Benefits: Not mentioned explicitly. No benefits listed. So we should NOT include Benefits section. Pay: Not mentioned. So no Pay. Schedule: Travel requirement 50-75% travel. That's schedule? Could be considered schedule (travel). The instruction: include Schedule section only if posting actually states them. It does state travel requirement. So we can include Schedule with travel % and passport requirement. We also have "Security Clearance" etc. That could be part of Requirements or Qualifications? It's under Minimum Qualifications? Actually it's after Minimum Qualifications bullet list: "Willingness and ability to travel: ... Security Clearance: Willingness and ability to obtain and maintain a security clearance if required for the role." This is part of Minimum Qualifications? It appears after the bullet list but still under Minimum Qualifications heading? The text: "Minimum Qualifications Domain Expertise: ... Zero to One Partnership Strategy: ... Functional Thought Leadership: ... Interpretive Problem-Solving: ... Cross-Functional Leadership: ... Rigorous Execution & Validation: ... Executive Communication: ... Willingness and ability to travel: ... Security Clearance: ..." So these are all part of Minimum Qualifications. So we include them under Requirements. Preferred Qualifications: list. Indicators of Success: maybe could be under Responsibilities? But it's separate. Could be considered "What success looks like". Could be a separate section maybe "Indicators of Success" but not in allowed headings. Allowed headings are limited to those list. We could incorporate Indicators of Success into Responsibilities or maybe into Requirements? But better to include as part of Responsibilities? However the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples but we should use those headings. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we must only use those headings. So we cannot add a heading like "Indicators of Success". We need to map that content somewhere else, maybe under Responsibilities or Requirements? The Indicators of Success are outcomes expected; could be considered part of Responsibilities (what you’ll do) or maybe under Requirements? I'd put them under Responsibilities as they describe expected outcomes. Tools, Systems & Technologies: could be under Skills. Now we need to produce HTML with

headings and appropriate

or

• . We must not repeat job title. The job title is International Partnerships Manager. Not to be used as heading. We must not include boilerplate like "Notice to Third Party Recruitment Agencies". That's legal/recruiter notice; we should remove. Also remove "Consequential Work. Dedicated People." maybe that's tagline; could be part of About the role? It's not substantive? Might be considered fluff but it's part of company description. We could include in About the role? But we have no explicit "About the role" content besides "Why This Role Exists" and "What You’ll Do". The tagline could be considered part of About the role? Might be okay to include as a short paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep details like percentages, years, etc. Let's extract content for each section. About the role: combine "Why This Role Exists" and maybe tagline. Why This Role Exists paragraph: "Onebrief is expanding its global footprint across international defense and operational sectors, requiring a disciplined, high-impact partner ecosystem to unlock strategic commercial, technical, and delivery capabilities. As an International Partnerships Manager, you will take ownership of making priority partnerships productive across assigned international markets, translating strategic alliances into measurable customer outcomes. In this role, you will establish accountable partner execution in close lockstep with International Growth and regional Sales teams. You will focus on building repeatable, high-value partner models that directly support regional opportunity targets, drive customer adoption, and enhance product delivery across diverse international defense landscapes. Operating as a deep functional individual contributor expert, you will guide our international partnership strategy through a structured validation model: proving initial value through verified deal contributions, demonstrating cross-customer repeatability through standardized processes, and building data-driven business cases to invest against operational constraints. You will directly shape how Onebrief scales globally alongside our international allies and partners." We can keep that as paragraph(s). Could split into multiple

  but okay. What You’ll Do (Responsibilities): bullet points: - Establish Accountable Regional Execution: Lead the end-to-end execution of priority international partnerships across assigned regions, aligning closely with International Growth and regional Sales leadership to achieve agreed opportunity and revenue targets. - Activate Partner Capabilities: Identify, activate, and integrate commercial, technical, and delivery capabilities from priority partners into live customer opportunities and Onebrief deployment workflows, ensuring contributions are validated by Sales and technical owners. - Build Repeatable Partnership Models: Design and implement scalable, standardized partnership frameworks and operational processes from scratch that replace one-off solutions and ensure consistent, efficient execution across multiple customer accounts. - Drive Constraint-Based Scaling & Strategy: Perform in-depth analysis of partner performance and market friction, collaborating with cross-functional leadership and Finance at key review milestones (6- and 12-month marks) to build rigorous business cases for scaling, holding, adjusting, or expanding market coverage. We can make each as

• . Indicators of Success (maybe incorporate into Responsibilities as additional bullets or separate

  after responsibilities). The Indicators of Success list: - Establish accountable partnership execution plans across assigned international markets, fully aligned with International Growth and regional Sales pipeline targets. - Successfully activate initial priority partners to deliver verified commercial, technical, or delivery capabilities accepted by regional Sales and technical owners on live opportunities. - Codify a repeatable partner engagement model across multiple customer opportunities, eliminating one-off deal mechanics and establishing standardized workflows. - Conduct a thorough 6-month partnership review with cross-functional leadership and Finance, delivering clear data on partner productivity and actionable strategy adjustments. - Identify specific operational constraints across target international markets and build data-backed recommendations for where and when to allocate future partnership capacity. We could add these as additional responsibilities bullets. Minimum Qualifications (Requirements): list each bullet: - Domain Expertise: 8+ years of professional experience in partnership management, alliance development, or strategic Go-To-Market (GTM) execution, with deep expertise operating within international markets, defense technology, enterprise SaaS, or complex government sectors. - Zero to One Partnership Strategy: Proven experience building partnership strategies from the ground up, including identifying priority markets and partners, securing initial partnerships, and creating a repeatable approach to scale. - Functional Thought Leadership: Proven track record of leveraging subject matter expertise to set functional direction and design advanced, scalable solutions for highly complex, multi-variable international GTM challenges. - Interpretive Problem-Solving: Demonstrated capability to perform in-depth analysis and use interpretive thinking to define ambiguous operational challenges, evaluate complex alternatives, and deploy innovative partnership frameworks. - Cross-Functional Leadership: Exceptional ability to lead through expertise and influence across distributed teams, including International Growth, Sales, Product, Technical, and Finance, shaping strategy across organizational boundaries without direct authority. - Rigorous Execution & Validation: Track record of establishing metric-driven partnership models that deliver verified commercial pipeline, specialized technical capabilities, or customer delivery success. - Executive Communication: Excellent written and verbal communication skills, with the presence and clarity required to represent Onebrief to senior international military, government, enterprise, and coalition leaders. - Willingness and ability to travel: This role requires domestic and international travel 50% to 75% of the time to meet with prospective customers. Candidates must have a valid passport or be able to obtain one promptly. - Security Clearance: Willingness and ability to obtain and maintain a security clearance if required for the role. We could split travel and security clearance maybe into Schedule section? But they are under Minimum Qualifications. However we have a Schedule section for travel %; we could still keep travel mention under Requirements but also include Schedule. The instruction: include Schedule section only if posting actually states them. It does state travel 50-75%. So we should include Schedule section with that detail. We could still keep travel mention in Requirements but that would duplicate. Better to move travel detail to Schedule and keep only the willingness to travel as a requirement? But the requirement includes travel and passport. If we move to Schedule, we might lose that detail from Requirements. However we could keep a brief statement like "Willingness and ability to travel" as a requirement, and then Schedule gives specifics. That's okay not duplicating too much. Security Clearance: could be under Requirements as a bullet. Preferred Qualifications (Qualifications): list: - Experience working within defense technology ecosystems, military planning workflows, or international allied frameworks (e.g., NATO, FVEY, or regional defense alliances). - Proven success building and scaling international channel, technical integration, or co-selling partner models from early growth phases into scalable global programs. - Direct experience managing international business development across target regions in Europe, Asia-Pacific, or the Middle East, including knowledge of regional procurement processes. - Background operating within high-growth, venture-backed technology environments scaling complex GTM and partner organizations. Skills: maybe from Tools, Systems & Technologies: list: - CRM & Pipeline Tools (Salesforce, HubSpot) - Partner Relationship Management (PRM) platforms - Onebrief Platform - Modern Collaboration Suites (Slack, Notion, Jira, Confluence) We could also include skills like "Executive Communication" but that's already in Requirements. We'll create Skills section with those tools. Now we need to output HTML fragment only, no or . Use

  for each section heading. Order: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. (We omit Benefits, Pay). Ensure we don't create empty sections. Let's craft. About the role: maybe include tagline "Consequential Work. Dedicated People." plus the Why This Role Exists paragraph. Could be two

  elements. Responsibilities: combine What You’ll Do and Indicators of Success as

  • . Requirements: Minimum Qualifications bullets (excluding travel details maybe keep willingness to travel).