Senior Consultant, Acquisition Content Development
ASI Government · Mechanicsburg, PA · 4 wk ago
HybridFull-time
We need to output only HTML fragment, using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate.
We need to extract content: The posting includes description about ASI Government, overview, position overview, key responsibilities (multiple sub-sections), required experience, preferred experience, why join ASI Government, benefits (but benefits details are generic: "comprehensive benefit package ... viewable on careers site" - that is not specific content; we should not create Benefits section unless posting actually states them. It says "Receive competitive compensation and a comprehensive benefits package, available on our careers site." That's vague; not specific. So we should not create Benefits section. Pay and Schedule not mentioned. So we may have sections: About the role (maybe we can use that as overview?), Responsibilities, Requirements, Qualifications, Skills? The posting lumps required experience and preferred experience; we could treat Required Experience as Requirements, Preferred Experience as Qualifications or Skills. But we must only include sections when posting has real specific content. It does have required experience list, preferred experience list. So we can have sections: Responsibilities (with subpoints), Requirements (required experience), Qualifications (preferred experience). Possibly Skills could be derived but not separate; we could omit Skills if not explicit. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. Likely include About the role (overview), Responsibilities, Requirements, Qualifications. Not include Skills, Benefits, Pay, Schedule.
We must preserve all substantive information; do not invent or summarize away detail. Must not omit details. So we need to include all bullet points from responsibilities, required experience, preferred experience. Also include overview paragraphs (position overview, department overview, etc.) as About the role content.
We need to format lists using
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate.
We need to extract content: The posting includes description about ASI Government, overview, position overview, key responsibilities (multiple sub-sections), required experience, preferred experience, why join ASI Government, benefits (but benefits details are generic: "comprehensive benefit package ... viewable on careers site" - that is not specific content; we should not create Benefits section unless posting actually states them. It says "Receive competitive compensation and a comprehensive benefits package, available on our careers site." That's vague; not specific. So we should not create Benefits section. Pay and Schedule not mentioned. So we may have sections: About the role (maybe we can use that as overview?), Responsibilities, Requirements, Qualifications, Skills? The posting lumps required experience and preferred experience; we could treat Required Experience as Requirements, Preferred Experience as Qualifications or Skills. But we must only include sections when posting has real specific content. It does have required experience list, preferred experience list. So we can have sections: Responsibilities (with subpoints), Requirements (required experience), Qualifications (preferred experience). Possibly Skills could be derived but not separate; we could omit Skills if not explicit. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. Likely include About the role (overview), Responsibilities, Requirements, Qualifications. Not include Skills, Benefits, Pay, Schedule.
We must preserve all substantive information; do not invent or summarize away detail. Must not omit details. So we need to include all bullet points from responsibilities, required experience, preferred experience. Also include overview paragraphs (position overview, department overview, etc.) as About the role content.
We need to format lists using - . For prose use
. Use
for each section heading.
We must not include markdown fences.
Let's craft.
First, About the role: combine the introductory paragraphs: "ASI Government provides government leaders...". Also Department Of War Practice Overview, Position Overview. We'll combine into prose.
We must not repeat job title (Senior Consultant) as heading; but we can mention it in prose.
Now Responsibilities: The posting has several 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. Each has bullet-like sentences (some are long). We need to turn each into list items. Probably each sentence or clause separated by periods. We'll need to preserve all substantive information; we can treat each sentence as a list item. But we must not lose details. Could break into multiple list items per sentence? Might be okay to keep each bullet as a list item representing the paragraph. However the instruction: Use - for any list of duties/requirements/benefits. The responsibilities are already a list; we can treat each bullet under each subheading as list items. But the original text uses sentences separated by periods; we can split at periods that end a sentence. We'll produce list items for each distinct duty.
Let's extract responsibilities sections:
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 Required Experience (list):
- Experience 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 (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.
Why Join ASI Government? (list):
- Contribute to high-impact work that improves defense acquisition and mission performance.
- Work with experienced colleagues across acquisition, strategy, analytics, technology, workforce, and organizational transformation.
- Help shape practical AI-enabled tools and guidance that make complex government work easier to navigate and execute.
- Grow in a collaborative, entrepreneurial environment with visible ownership and opportunities to expand your responsibilities.
- Receive competitive compensation and a comprehensive benefits package, available on our careers site.
But we decided not to include Benefits section because it's vague. However "Why Join ASI Government?" could be considered a section; but headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Join ASI Government?" is not in that list, but we could treat it as part of About the role or maybe as a separate section not in list; but instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. We could incorporate "Why Join ASI Government?" content into About the role or maybe into a separate section like "About the role" already covers overview; we could add a subsection but not as heading. Probably better to include it as part of About the role prose.
Thus sections: About the role (overview + why join), Responsibilities, Requirements, Qualifications.
We must not include Skills, Benefits, Pay, Schedule.
Now produce HTML fragment.
We'll start with About the role
then
with prose combining overview and why join.
We need to ensure we preserve all substantive information from overview paragraphs: ASI Government description, Department Of War Practice Overview, Position Overview, plus Why Join ASI Government bullet points.
Let's craft prose:
"ASI Government provides government leaders with the expertise they need to navigate acquisition and organizational challenges so they can make an impact and achieve their goals. For over 30 years, ASI has transformed the way government does business, impacting over 70 government agencies across the civilian, defense, and intelligence communities. Do
. Use
for each section heading.
We must not include markdown fences.
Let's craft.
First, About the role: combine the introductory paragraphs: "ASI Government provides government leaders...". Also Department Of War Practice Overview, Position Overview. We'll combine into prose.
We must not repeat job title (Senior Consultant) as heading; but we can mention it in prose.
Now Responsibilities: The posting has several 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. Each has bullet-like sentences (some are long). We need to turn each into list items. Probably each sentence or clause separated by periods. We'll need to preserve all substantive information; we can treat each sentence as a list item. But we must not lose details. Could break into multiple list items per sentence? Might be okay to keep each bullet as a list item representing the paragraph. However the instruction: Use - for any list of duties/requirements/benefits. The responsibilities are already a list; we can treat each bullet under each subheading as list items. But the original text uses sentences separated by periods; we can split at periods that end a sentence. We'll produce list items for each distinct duty.
Let's extract responsibilities sections:
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 Required Experience (list):
- Experience 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 (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.
Why Join ASI Government? (list):
- Contribute to high-impact work that improves defense acquisition and mission performance.
- Work with experienced colleagues across acquisition, strategy, analytics, technology, workforce, and organizational transformation.
- Help shape practical AI-enabled tools and guidance that make complex government work easier to navigate and execute.
- Grow in a collaborative, entrepreneurial environment with visible ownership and opportunities to expand your responsibilities.
- Receive competitive compensation and a comprehensive benefits package, available on our careers site.
But we decided not to include Benefits section because it's vague. However "Why Join ASI Government?" could be considered a section; but headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Join ASI Government?" is not in that list, but we could treat it as part of About the role or maybe as a separate section not in list; but instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. We could incorporate "Why Join ASI Government?" content into About the role or maybe into a separate section like "About the role" already covers overview; we could add a subsection but not as heading. Probably better to include it as part of About the role prose.
Thus sections: About the role (overview + why join), Responsibilities, Requirements, Qualifications.
We must not include Skills, Benefits, Pay, Schedule.
Now produce HTML fragment.
We'll start with About the role
then
with prose combining overview and why join.
We need to ensure we preserve all substantive information from overview paragraphs: ASI Government description, Department Of War Practice Overview, Position Overview, plus Why Join ASI Government bullet points.
Let's craft prose:
"ASI Government provides government leaders with the expertise they need to navigate acquisition and organizational challenges so they can make an impact and achieve their goals. For over 30 years, ASI has transformed the way government does business, impacting over 70 government agencies across the civilian, defense, and intelligence communities. Do
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. We could incorporate "Why Join ASI Government?" content into About the role or maybe into a separate section like "About the role" already covers overview; we could add a subsection but not as heading. Probably better to include it as part of About the role prose.
Thus sections: About the role (overview + why join), Responsibilities, Requirements, Qualifications.
We must not include Skills, Benefits, Pay, Schedule.
Now produce HTML fragment.
We'll start with About the role
then
with prose combining overview and why join. We need to ensure we preserve all substantive information from overview paragraphs: ASI Government description, Department Of War Practice Overview, Position Overview, plus Why Join ASI Government bullet points. Let's craft prose: "ASI Government provides government leaders with the expertise they need to navigate acquisition and organizational challenges so they can make an impact and achieve their goals. For over 30 years, ASI has transformed the way government does business, impacting over 70 government agencies across the civilian, defense, and intelligence communities. Do