Senior Consultant, Acquisition Content Development

We need to produce HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, navigation, cookie, legal, etc. Must preserve all substantive info. We need to parse the posting. First paragraph: "ASI Government provides government leaders..." That's about company overview. Could be "About the role"? Actually "About the role" maybe includes description of role and company. The posting includes "Position Overview" etc. So we can put an

About the role

with paragraphs summarizing the role overview and maybe company description. Then Responsibilities: there is a "Key Responsibilities" section with subheadings: Process Discovery and Client Engagement, Resource Analysis and Content Strategy, Content Development and Quality, AI Enabled Tool and Product Integration, User Testing Adoption and Continuous Improvement, Workstream Leadership and Practice Contribution. We need to list duties as

• . Should we keep subheadings? Probably we can include them as part of list items or separate

  ? But only allowed headings are

  for section headings. We can embed subheadings as bold text inside

  maybe. Simpler: each bullet can contain the responsibility description. We'll extract each bullet's content. Let's extract responsibilities: Process Discovery and Client Engagement: - Build trusted day-to-day relationships with acquisition professionals, program staff, policy owners, and other client stakeholders across assigned workstreams. - Plan and facilitate interviews, working sessions, process walk-throughs, focus groups, and validation sessions to capture how work is performed, where users encounter friction, and what guidance they need. - Quickly understand complex or ambiguous acquisition processes, including variations by organization, requirement, procurement method, dollar value, and level of risk. - Translate stakeholder knowledge and institutional practices into clear process documentation, requirements, findings, and recommendations. - Prepare client-ready agendas, presentations, summaries, and decision materials; document actions, owners, decisions, and next steps. Resource Analysis and Content Strategy: - Inventory, organize, and evaluate acquisition resources such as policies, procedures, templates, clauses, checklists, job aids, training, examples, and reference materials. - Assess content for authority, accuracy, currency, completeness, usability, consistency, duplication, and alignment with user needs and process requirements. - Identify gaps, conflicts, redundancies, and outdated materials; synthesize findings into practical recommendations for development, revision, consolidation, or retirement. - Develop content plans and prioritized backlogs based on user impact, process criticality, implementation feasibility, and engagement objectives. - Define content structures, taxonomies, metadata, and navigation approaches that help users find and apply the right guidance efficiently. Content Development and Quality: - Develop and refine clear, concise content supporting the acquisition lifecycle, including process maps, procedures, instructions, decision trees, templates, checklists, job aids, training, scenarios, and reference materials. - Convert dense policy and expert knowledge into actionable guidance that is useful to both newer and experienced acquisition professionals while preserving necessary nuance and authority. - Apply consistent writing, formatting, source attribution, version control, and quality-review standards across the content library. - Produce content iteratively in a fast-paced environment, balancing speed with accuracy, usability, and readiness for client review. - Review the work of other contributors and incorporate feedback from acquisition, legal, policy, accessibility, user-experience, and technical reviewers. - Recommend opportunities to simplify guidance, standardize repeatable work, reduce rework, and improve the acquisition user experience. AI Enabled Tool and Product Integration: - Partner with product, data, and technical teams to translate content and user needs into requirements for AI-enabled guides, search tools, workflow solutions, and related prototypes. - Participate in design and technical discussions to ensure content architecture, tool functionality, and user workflows remain aligned. - Prepare representative questions, use cases, examples, source sets, and expected outputs to support prototype development and evaluation. - Help validate that AI-enabled outputs are accurate, traceable to authoritative sources, appropriately qualified, and useful within the intended acquisition context. - Track content-related dependencies such as source access, ownership, approvals, migration, configuration, and refresh responsibilities; raise risks with proposed mitigations. User Testing Adoption and Continuous Improvement: - Plan and support demonstrations, usability sessions, pilot testing, and structured feedback activities with target users. - Observe user behavior, capture feedback, analyze patterns, and translate findings into prioritized content, process, and product improvements. - Support training, communications, change management, and rollout activities that build user confidence and adoption. - Define practical measures of content quality, usefulness, findability, adoption, and operational impact; contribute evidence for prototype evaluation and refinement. - Establish sustainable approaches for content governance, ownership, review, maintenance, and continuous improvement in coordination with client and engagement leaders. Workstream Leadership and Practice Contribution: - Lead assigned content workstreams with accountability for scope, workplan, milestones, dependencies, risks, actions, and quality. - Coordinate contributions from ASI staff, client subject-matter experts, and teaming partners, maintaining clear roles, review cycles, and handoffs. - Provide concise status reporting, surface issues early, develop proposed solutions, and elevate decisions requiring engagement-lead or client direction. - Contribute client insight and delivery experience to proposals, account planning, reusable methods, and repeatable acquisition and AI-enabled offerings. - Support adjacent workstreams as needed to meet critical deadlines and advance shared engagement outcomes. Now Requirements: The posting has "Required Experience" bullet list. Also "Preferred Experience". We need to separate maybe Requirements and Qualifications? The instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. "Required Experience" likely maps to Requirements. "Preferred Experience" could be Qualifications or Skills. Also there is "Bachelor’s degree." etc. Also "US citizenship and ability to obtain and maintain the clearance..." etc. Also "Willingness and ability to travel..." etc. We can put Requirements: list of required experience items. Qualifications: maybe education, citizenship, clearance, travel willingness. Skills: maybe strong analytical skills, writing, facilitation, organization, stakeholder management, etc. But those are also in required experience list. However we can separate: Required Experience (mandatory), Preferred Experience (nice-to-have) as Qualifications, and Skills maybe from bullet list like "Strong analytical skills", "Excellent writing and editing skills", etc. But we must not invent content; we need to preserve all substantive info. So we need to include all those details somewhere. We could combine Required Experience and Qualifications into one section? But headings must be used only when there is real specific content. We could have Requirements (required experience), Qualifications (preferred experience + education/clearance), Skills (maybe from required list but we could also omit Skills if no distinct content). However the instruction says prefer a few substantive sections over many thin ones. So we might combine Requirements and Qualifications into one section? But we need to follow the allowed headings; we can omit sections if no content. So we could have About the role, Responsibilities, Requirements (covering required experience, preferred experience, education, citizenship, travel), Benefits (since they mention benefits package). Pay and Schedule: not mentioned, so omit. Thus we will have:

  About the role

  with paragraphs: company overview and position overview.

  Responsibilities

  with

  • each responsibility bullet (maybe grouped under subheadings but we can just list all bullets).

    Requirements

    with
    • for required experience items, preferred experience items, education, citizenship, clearance, travel. We need to ensure we don't repeat content. Let's extract required experience bullet list: - Supporting Department of War or Department of the Navy, preferably within contracting, acquisition, or policy organization. - 5+ years of experience in roles requiring rapid absorption of complex processes and the development of clear, structured content (e.g., consulting, process documentation, training development, technical writing, business analysis, or similar) - Experience independently leading a defined workstream or major project component involving multiple stakeholders, source materials, reviews, and deliverables. - Demonstrated ability to rapidly understand complex or ambiguous processes and translate them into clear, structured, accurate, and usable content. - Strong analytical skills, including the ability to assess large sets of resources, identify gaps and inconsistencies, distinguish authoritative from supplemental content, and recommend improvements. - Excellent writing and editing skills, with experience producing polished client-ready content quickly and accurately for different audiences and formats. - Experience facilitating interviews, working sessions, focus groups, process validation, or user-testing activities with subject-matter experts and client stakeholders. - Strong organization, stakeholder management, attention to detail, and follow-through in a fast-paced environment with shifting priorities. - Proactive, ownership-oriented, and team-focused approach, with the judgment to raise risks and propose practical solutions. - Bachelor’s degree. - US citizenship and ability to obtain and maintain the clearance, credentials, and client-site access required for assigned engagements. - Willingness and ability to travel and work at client sites as required by the engagement. Preferred Experience bullet list: - Experience with Department of War or Department of the Navy acquisition, contracting, or procurement processes, policies, systems, documentation, or workforce development, including familiarity with the FAR, DFARS, and NMCARS. - Experience developing process maps, decision trees, templates, checklists, job aids, training, knowledge bases, or interactive guidance. - Familiarity with AI and machine learning, generative AI, intelligent search, robotic process automation, workflow automation, or digital transformation in a federal context. - Experience supporting content-enabled products through discovery, requirements, prototyping, testing, implementation, governance, and adoption. - Familiarity with content management, taxonomy, metadata, knowledge management, accessibility, or content-governance practices. - Advanced degree or relevant professional certification in acquisition, project management, instructional design, technical communication, knowledge management, or a related field. We could also include "Why Join ASI Government?" as part of About the role maybe. But we need to avoid boilerplate like "Equal Opportunity Employer". We'll strip that. Now Benefits: The posting says: "Receive competitive compensation and a comprehensive benefits package, available on our careers site." Then later: "BENEFITS: ASI Government offers a comprehensive benefit package to our employees. Benefits can be viewed on our careers site." So we have some content about benefits: comprehensive benefit package, viewable on careers site. We'll include that. Pay: Not specified, so omit. Schedule: Not specified, omit. Now About the role: We need to include company overview and position overview. Let's craft paragraphs: Paragraph 1: ASI Government provides government leaders with expertise to navigate acquisition and organizational challenges, impacting over 70 agencies across civilian, defense, intelligence communities for over 30 years. Paragraph 2: The Department of War portfolio supports defense leaders in achieving mission-critical outcomes, working across DoW components (Army, Navy, Air Force, Defense Logistics Agency) on acquisition, industrial-base resilience, emerging technology, workforce, organizational transformation. Paragraph 3: Position Overview: ASI Government seeks a Senior Consultant to lead acquisition content development workstreams across AI-enabled transformation engagements in its Department of War portfolio. Working under direction of an ASI Engagement Lead and alongside acquisition SMEs, client stakeholders, UX specialists, technical teams, the Senior Consultant turns complex policies, processes, templates, institutional knowledge into clear, accurate, usable content for acquisition professionals. Independently plans and delivers defined content workstreams from process discovery through content design, validation, testing, refinement, implementation. Requires strong consulting judgment, analytical and writing skills, client facilitation, ability to rapidly absorb unfamiliar acquisition processes, comfortable in ambiguous fast-paced environments, synthesize complex info into actionable recommendations, skilled at collaborating with leadership and cross-functional teams. Connects content and tool development ensuring AI-enabled guides, search tools, workflow solutions, training, job aids reflect user needs, authoritative guidance, real-world operating conditions. We should keep all substantive info; we