Partner Engagement Manager, 4th Infantry Division
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include. The posting includes:
- About Onebrief (company description) – could be "About the role"? Actually "About Onebrief" is company overview. Might be considered "About the role"? But we have "Why This Role Exists" which is like role purpose. Could map to "About the role". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings where appropriate.
We have:
- Why This Role Exists: description of role purpose. Could be "About the role".
- What You’ll Do: core responsibilities – map to "Responsibilities".
- Minimum Qualifications: qualifications – map to "Qualifications" (or Requirements?). Could be "Qualifications". Also there are "Preferred Qualifications": could be part of Qualifications or separate "Preferred Qualifications" but instruction only lists Qualifications as a heading; we could combine minimum and preferred under Qualifications with subheadings? But we must not invent headings not listed. However we could still include a heading "Qualifications" and include both minimum and preferred as lists.
- Indicators of Success: maybe "Skills"? Not exactly. Could be "Skills" but it's more about outcomes. Could treat as "Skills"? Or maybe we could omit if not matching headings. But we need to preserve all substantive information; we cannot omit Indicators of Success. We could incorporate it under "Qualifications" or "Skills". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, but we should prefer those. However we could still add other headings if needed, but better to map to given ones.
We could map Indicators of Success to "Skills" (since they are about behaviors). Or we could create a "Requirements" section for minimum qualifications and "Qualifications" for preferred? But we have both minimum and preferred. Could do:
- About the role (Why This Role Exists)
- Responsibilities (What You’ll Do)
- Requirements (Minimum Qualifications)
- Qualifications (Preferred Qualifications)
- Skills (Indicators of Success)
That seems reasonable.
We must not include Pay, Schedule, Benefits as they are not present.
We need to remove boilerplate: "Notice to Third Party Recruitment Agencies" is legal boilerplate; should be removed. Also "Consequential Work. Dedicated People." maybe tagline but could be kept? It's not boilerplate but maybe part of intro. It's okay to keep as prose.
We need to preserve all substantive information: company description, role purpose, responsibilities, minimum qualifications, preferred qualifications, indicators of success. Also note "Required: Top Secret clearance with eligibility for SCI In person in Colorado Springs, CO" – that's a requirement (location and clearance). Should be included somewhere, maybe under Requirements or Qualifications. It's a required qualification. We'll include in Requirements.
Also note "Founded in 2019..." etc is company description; keep.
We need to format lists: For responsibilities, we have bullet points after "Core responsibilities:" then a list of items separated by line breaks. We'll convert each line to
- .
Similarly for Minimum Qualifications: list of items after colon.
Preferred Qualifications: list after colon.
Indicators of Success: list after colon.
We need to ensure we don't duplicate lines.
Let's extract content.
First, the intro:
"Consequential Work. Dedicated People. About Onebrief Onebrief builds collaboration and AI-powered workflow software for military planning and operational coordination. Military planning is complex by nature, requiring teams to coordinate information, people, and decisions across systems and locations. Onebrief brings planning, collaboration, simulation, and AI into one connected environment, helping teams test strategies, adapt to changing conditions, and make decisions with greater clarity when the stakes are real. We are a distributed team of builders from military, operational, and technology backgrounds who care deeply about improving how important work gets done. Some team members work remotely, while others work directly alongside customers in operational environments around the world. Founded in 2019, Onebrief is backed by leading investors including General Catalyst, Battery Ventures, Insight Partners, Sapphire Ventures, and Human Capital. Valued at more than $2 billion, we continue to invest in product innovation, AI capabilities, and team growth."
That's company description.
Then "Required: Top Secret clearance with eligibility for SCI In person in Colorado Springs, CO"
Then "Why This Role Exists As a Partner Engagement Manager at Onebrief, you're the customer's trusted technical partner. You serve as the subject-matter expert, maintaining power-user-level fluency in the platform. You stay current on product updates, translating new releases into practical impact for the specific workflows your customer relies on. You act as the primary line of communication between the customer and Onebrief — as the product evolves, you deliver ongoing, role-specific training to ensure users adopt new capabilities rather than getting stuck on outdated workflows. You bridge the technical gap between engineering and the customer, explaining product behavior in terms their staff can actually act on."
Then "What You’ll Do Core responsibilities: Clearly communicate user needs to the product team. Maintain a high product proficiency, and excite the customer about each product improvement.Understand, request, and effectively leverage Company resources to meet the goals of the Company.Lead or support exercises.Use your observations of our users to recommend product improvements.Identify gaps between existing directorate workflows and effective Onebrief usage, then drive adoption through hands-on configuration, user coaching, and workflow optimization.When responding to incidents (product is unavailable, broken, or not delighting the customer), coordinate with the customer and our product engineering team.Instill the Onebrief brand image.Align your team’s efforts to deliver the best customer experience, while coordinating with fellow Partner Engagement Managers to ensure planning and workflows remain synchronized across commands.Enable our expansion to Allies and Partners."
Note there are some missing spaces after periods; but we keep as is.
Then "Minimum Qualifications Proven experience in leading operational planning within a military context, preferably at multi-star headquarters.Exposure to large staff planning, through classical training in Professional Military Education or through service experienceFamiliarity and experience with major military planning exercises and the protocols for software deployment on classified networks.Proven ability to expand business presence within a customer location with emphasis on software or technology solutions.Experience in customer support, both face-to-face and remote, and capability to respond to incidents coordinating with customers and product engineering teams.Strong technical skills to master our application, troubleshoot issues and liaise with customers on technical matters.Proven ability to navigate large government organizations, solve bureaucratic challenges, and deliver successful outcomes.You hold a current Top Secret clearance with eligibility for SCI and have the ability to access DOD facilities and installations."
Then "Preferred Qualifications You’re technically adept. You don’t need to code, but you do need to be savvy. Can you become a power user of our product and talk engineering with the customer?Customers trust you. You demonstrate strong interpersonal skills, develop rapport, align diverse perspectives, and communicate with clarity and influence.You’re intense about our mission. It’s a core part of who you areYou’re proactive and adaptable. You see a problem and get to work. You’re comfortable working autonomously or in a cross-functional team, especially in a fast-paced or ambiguous settingYou communicate clearly, concisely, and candidly. Our Company relies on you to assess the situation within your account and effectively communicate your assessment and recommendations to inform strategic decisions."
Then "Indicators of Success This role will evolve as priorities change, but the outcomes below reflect what success typically looks like in the first six months. A successful Partner Engagement Manager will: Opinion and expertise are valued by the customer and company alike (rapport/trust)Learns quick, identifies opportunities and drives progress within the account (Forward-leaning/ bias for action)Open-minded and able to pivot when priorities shift (Adaptability/ Humility)"
Then the notice to third party recruitment agencies (boilerplate) to remove.
Now we need to produce HTML.
We'll start with a
for company description? Could be multiple paragraphs. We'll keep as
for each paragraph.
We need to include the required clearance and location as part of Requirements maybe.
Let's structure:
About the role
Why This Role Exists ...
Responsibilities
- Clearly communicate user needs to the product team.
- Maintain a high product proficiency, and excite the customer about each product improvement.
- Understand, request, and effectively leverage Company resources to meet the goals of the Company.
- Lead or support exercises.
- Use your observations of our users to recommend product improvements.
- Identify gaps between existing directorate workflows and effective Onebrief usage, then drive adoption through hands-on configuration, user coaching, and workflow optimization.
- When responding to incidents (product is unavailable, broken, or not delighting the customer), coordinate with the customer and our product engineering team.
- Instill the Onebrief brand image.
- Align your team’s efforts to deliver the best customer experience, while coordinating with fellow Partner Engagement Managers to ensure planning and workflows remain synchronized across commands.
- Enable our expansion to Allies and Partners.
Note: The original had some run-on sentences; we split at each sentence after a period. Need to ensure we captured all.
Check the responsibilities text: "Clearly communicate user needs to the product team. Maintain a high product proficiency, and excite the customer about each product improvement.Understand, request, and effectively leverage Company resources to meet the goals of the Company.Lead or support exercises.Use your observations of our users to recommend product improvements.Identify gaps between existing directorate workflows and effective Onebrief usage, then drive adoption through hands-on configuration, user coaching, and workflow optimization.When responding to incidents (product is unavailable, broken, or not delighting the customer), coordinate with the customer and our product engineering team.Instill the Onebrief brand image.Align your team’s efforts to deliver the best customer experience, while coordinating with fellow Partner Engagement Managers to ensure planning and workflows remain synchronized across commands.Enable our expansion to Allies and Partners."
We need to split correctly:
- Clearly communicate user needs to the product team.
- Maintain a high product proficiency, and excite the customer about each product improvement.
- Understand, request, and effectively leverage Company resources to meet the goals of the Company.
- Lead or support
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: - About Onebrief (company description) – could be "About the role"? Actually "About Onebrief" is company overview. Might be considered "About the role"? But we have "Why This Role Exists" which is like role purpose. Could map to "About the role". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings where appropriate. We have: - Why This Role Exists: description of role purpose. Could be "About the role". - What You’ll Do: core responsibilities – map to "Responsibilities". - Minimum Qualifications: qualifications – map to "Qualifications" (or Requirements?). Could be "Qualifications". Also there are "Preferred Qualifications": could be part of Qualifications or separate "Preferred Qualifications" but instruction only lists Qualifications as a heading; we could combine minimum and preferred under Qualifications with subheadings? But we must not invent headings not listed. However we could still include a heading "Qualifications" and include both minimum and preferred as lists. - Indicators of Success: maybe "Skills"? Not exactly. Could be "Skills" but it's more about outcomes. Could treat as "Skills"? Or maybe we could omit if not matching headings. But we need to preserve all substantive information; we cannot omit Indicators of Success. We could incorporate it under "Qualifications" or "Skills". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The e.g. suggests those are examples, but we should prefer those. However we could still add other headings if needed, but better to map to given ones. We could map Indicators of Success to "Skills" (since they are about behaviors). Or we could create a "Requirements" section for minimum qualifications and "Qualifications" for preferred? But we have both minimum and preferred. Could do: - About the role (Why This Role Exists) - Responsibilities (What You’ll Do) - Requirements (Minimum Qualifications) - Qualifications (Preferred Qualifications) - Skills (Indicators of Success) That seems reasonable. We must not include Pay, Schedule, Benefits as they are not present. We need to remove boilerplate: "Notice to Third Party Recruitment Agencies" is legal boilerplate; should be removed. Also "Consequential Work. Dedicated People." maybe tagline but could be kept? It's not boilerplate but maybe part of intro. It's okay to keep as prose. We need to preserve all substantive information: company description, role purpose, responsibilities, minimum qualifications, preferred qualifications, indicators of success. Also note "Required: Top Secret clearance with eligibility for SCI In person in Colorado Springs, CO" – that's a requirement (location and clearance). Should be included somewhere, maybe under Requirements or Qualifications. It's a required qualification. We'll include in Requirements. Also note "Founded in 2019..." etc is company description; keep. We need to format lists: For responsibilities, we have bullet points after "Core responsibilities:" then a list of items separated by line breaks. We'll convert each line to
for company description? Could be multiple paragraphs. We'll keep as
for each paragraph. We need to include the required clearance and location as part of Requirements maybe. Let's structure:
About the role
Why This Role Exists ...
Responsibilities
- Clearly communicate user needs to the product team.
- Maintain a high product proficiency, and excite the customer about each product improvement.
- Understand, request, and effectively leverage Company resources to meet the goals of the Company.
- Lead or support exercises.
- Use your observations of our users to recommend product improvements.
- Identify gaps between existing directorate workflows and effective Onebrief usage, then drive adoption through hands-on configuration, user coaching, and workflow optimization.
- When responding to incidents (product is unavailable, broken, or not delighting the customer), coordinate with the customer and our product engineering team.
- Instill the Onebrief brand image.
- Align your team’s efforts to deliver the best customer experience, while coordinating with fellow Partner Engagement Managers to ensure planning and workflows remain synchronized across commands.
- Enable our expansion to Allies and Partners.