Strategic Alliance Manager - Mission Infrastructure

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, scam warning, etc. Must not include placeholder text like "commensurate with experience". Must not create sections unless posting actually states them. We need to parse the posting. Key sections: - About The Role: paragraph description. - Key Responsibilities: list of responsibilities. - Key Knowledge And Skills: list of skills/knowledge. - Key Education Requirements: list of education/experience requirements. - Expected Outcomes: maybe could be considered as part of responsibilities? But we have no specific heading for outcomes; we could put under Responsibilities or maybe a separate section? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate. It doesn't say we cannot add other headings, but likely we should stick to those. Expected Outcomes could be considered part of Responsibilities or maybe a separate section like "Outcomes". But not in list; maybe we can incorporate into Responsibilities. - Pay: The posting includes "A reasonable estimate of the on-target earnings ("OTE") for this role is between: $305,600.00-366,400.00 USD". That's pay info. So we need a Pay section. - Benefits: "In addition to the OTE, Everfox offers a generous benefits package including flexible PTO, a 401k match, and contribution to healthcare coverages." So Benefits section. - Schedule: The posting mentions hybrid role: "You’ll work on-site with your team several days each week (typically 2–3), with the specific days set by your manager. Because regular in-person collaboration is central to this job, we look for candidates who live within about 50 miles of the office." That's schedule info. So Schedule section. - Requirements: Could be education requirements? The instruction distinguishes Requirements vs Qualifications vs Skills. We have "Key Education Requirements" and "Key Knowledge And Skills". Possibly map Education Requirements to Requirements or Qualifications? The headings list includes Requirements, Qualifications, Skills. We need to decide mapping. We have: - Key Knowledge And Skills: skills. - Key Education Requirements: education/experience requirements. Thus we can put Skills under

Skills

. Requirements under

Requirements

(education/experience). Qualifications maybe not present; we could omit if no specific content. The posting also mentions "An active or previously held U.S. Government security clearance is desirable." That could be a qualification. Could be placed under Qualifications. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not include empty sections. Ensure each has content. Now we need to strip boilerplate: EEO, scam warning, accommodation request, etc. Also remove duplicated lines, navigation, cookie, legal. Also remove the "Trusted Connectivity for AI-Powered Dominance..." intro? That's marketing fluff but maybe considered substantive? It's about company description; not directly about the job. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description may be considered substantive? It's not about the role but maybe part of posting. However typical job posting includes company overview; we might keep it? 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 say to drop company overview. But we might keep it as a paragraph before About the role? However the instruction says "Output ONLY the HTML fragment". It didn't say we must include company overview. The sections we need to output are based on headings; we could include a

before first heading for general description. That seems acceptable. We need to preserve all substantive information: that includes the hybrid work details, location, travel %, etc. Also the "Location: Based on partner and customer requirements, travel is approximately 25–40%." That's location/travel info; could be placed under About the role or maybe a separate section? Not in headings list; we could incorporate into About the role paragraph. Also "We’re hiring for a hybrid role. You’ll work on-site with your team several days each week (typically 2–3), with the specific days set by your manager. Because regular in-person collaboration is central to this job, we look for candidates who live within about 50 miles of the office. Everfox will consider reasonable accommodation as required by law." That's schedule/hybrid info; we will put under Schedule section. Now we need to format lists: Use

• for any list of duties/requirements/benefits. Thus: - About the role:

  About the role

  then

  with description. - Responsibilities:

  Responsibilities

  then
  with each responsibility. - Requirements:

  Requirements

  then
  with education/experience requirements. - Qualifications:

  Qualifications

  then
  with qualifications like security clearance desirable, maybe experience with DoD etc? Actually those are in Key Knowledge And Skills and Key Education Requirements. We'll need to parse. Let's extract details: From "Key Responsibilities" bullet points (each starts with a bold heading). We'll list each as
  • items. List: - Partner Engagement and Execution: Support day-to-day execution of assigned Mission Infrastructure partnerships. Maintain productive relationships with partner alliance, sales, technical, product, and public-sector organizations. Develop and maintain execution plans, action items, milestones, and follow-up activities for each relationship. - Joint Solution Development: Coordinate with Everfox Mission Engineering, Product Management, Engineering, Sales Engineering, and partner technical organizations to develop integrated mission solutions. Support development of reference architectures, integration plans, solution briefs, demonstrations, technical validations, and repeatable deployment models. - Go-to-Market Support: Translate partner technologies and integrated solutions into executable GTM activities. Support development of mission use cases, target customer profiles, value propositions, sales plays, partner enablement materials, and joint account strategies. - Opportunity and Pipeline Development: Identify and develop joint customer opportunities. Coordinate partner introductions, customer meetings, workshops, demonstrations, technical discussions, and follow-up actions to advance opportunities. - Strategic Pursuit Support: Support selected customer pursuits where Mission Infrastructure technologies can strengthen the Everfox solution, increase differentiation, expand deal value, or address specific customer requirements. - Solution Packaging and Commercialization: Assist in converting successful technical integrations into repeatable commercial offerings. Support development of solution packaging, SKUs, bundles, services, subscriptions, OEM relationships, and XaaS offerings. - Market and Technology Development: Research emerging infrastructure technologies, companies, mission requirements, and market developments. Develop initial assessments and recommendations for consideration. - Cross-SGO Collaboration: Work across Hyperscalers, Defense Tech, and Mission AI Towers to support multi-partner architectures and integrated mission solutions. - Program and Operating Discipline: Maintain accurate information regarding initiatives, partner activities, customer opportunities, pipeline, milestones, dependencies, and next actions within Salesforce and other SGO operating systems. Provide concise and timely reporting. Now "Key Knowledge And Skills" bullet points: - Strong organizational and project-management skills. - Effective written and verbal communication. - Ability to coordinate multiple organizations and initiatives simultaneously. - Understanding of enterprise infrastructure technologies (compute, networking, storage, data platforms, cybersecurity, cloud, edge computing, mission systems). - Experience supporting U.S. Department of Defense, Intelligence Community, federal civilian, or other national-security customers is desirable. - Comfortable working across multiple organizations without formal authority. - Ability to translate strategic objectives into practical execution plans with defined actions, owners, milestones, and measurable outcomes. - High-energy executor and problem solver; consistent follow-through from discussion to action and measurable business results. Now "Key Education Requirements" bullet points: - Approximately 5–8+ years of relevant experience in technology partnerships, business development, federal technology, cybersecurity, enterprise infrastructure, program management, solution development, sales support, or related discipline. - May require vocational qualifications; working toward a professional qualification is beneficial. - Experience with infrastructure and cybersecurity technology companies (e.g., Dell, HPE, Red Hat, Cisco, Palo Alto Networks, CrowdStrike, VAST Data, Virtru, Elastic, Splunk, or comparable providers) is preferred. - Experience with Cross Domain Solutions, Zero Trust, classified networks, mission systems, AI infrastructure, tactical-edge environments, government technology acquisition, or strategic technology alliances is beneficial. - An active or previously held U.S. Government security clearance is desirable. Now "Expected Outcomes" bullet points (we could incorporate into Responsibilities or maybe a separate section but not required). We'll maybe add them under Responsibilities as additional items? But they are outcomes, not responsibilities. However we could keep them under Responsibilities as they are still part of role expectations. But to avoid missing info, we could add a separate section "Outcomes" but not in allowed headings. Safer to incorporate them into Responsibilities as additional bullet points. But we must not invent or summarize away detail; we can just add them as list items under Responsibilities. List Expected Outcomes: - Advancement of strategic partnerships and initiatives. - Development of joint Everfox-partner solutions and reference architectures. - Creation and advancement of partner-enabled customer opportunities. - Development of qualified pipeline and influenced revenue. - Successful customer demonstrations, workshops, technical validations, and proofs of concept. - Development of repeatable GTM motions and sales plays. - Creation of partner and Everfox field enablement materials. - Effective coordination of partner resources against strategic customer pursuits. - Timely completion of initiative milestones and action items. - Accurate Salesforce and SGO reporting. - Transition of mature opportunities to Everfox Sales for execution and closure. Now Benefits: "In addition to the OTE, Everfox offers a generous benefits package including flexible PTO, a 401k match, and contribution to healthcare coverages." That's it. Pay: OTE range. Schedule: hybrid details. Now About the role paragraph: we need to combine the introductory description: "Strategic Mission Infrastructure Manager Hybrid: Herndon, VA About The Role The Strategic Mission Infrastructure Manager is an individual contributor within the Everfox Strategic Growth Office, responsible for supporting the development, execution, and growth of strategic technology partnerships and market initiatives within the Mission Infrastructure Tower. This role is execution-focused, working across partner ecosystems—including infrastructure, compute, networking, data, cybersecurity, storage, and platform technology companies—to convert strategic partner relationships into integrated solutions, customer opportunities, qualified pipeline, and measurable business outcomes. Location: Based on partner and customer requirements, travel is approximately 25–40%." We should also include maybe the earlier marketing fluff? Not needed. Thus About the role paragraph: combine those sentences. Now we need to ensure we don't include boilerplate like "We’re hiring for a hybrid role..." that's schedule; we will put under Schedule. Now we need to output HTML fragment only, no or . Use

    for headings. Use

    for prose. Use

    • for lists. We must not repeat job title as heading. The job title is "Strategic Mission Infrastructure Manager Hybrid". We'll not use it as heading. Now let's craft. Structure:

      Strategic Mission Infrastructure Manager Hybrid: Herndon, VA The Strategic Mission Infrastructure Manager is an individual contributor within the Everfox Strategic Growth Office, responsible for supporting the development, execution, and growth