Senior Consultant, Acquisition Content Development
ASI Government · Philadelphia, PA · 4 wk ago
HybridFull-time
We need to output HTML fragment with sections only when there is real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse posting: It includes intro about ASI Government, Department of War Practice Overview, Position Overview, Key Responsibilities (with sub-bullets), Required Experience, Preferred Experience, Why Join ASI Government? (with bullet points), BENEFITS: (but says benefits can be viewed on careers site - not specific). According to rules: do 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 benefits. So we should not create Benefits section. Also Pay/Schedule sections not present.
We need sections: About the role? Could use "About the role" maybe from intro? The posting includes "Position Overview". Could map to "About the role". Also "Responsibilities" from Key Responsibilities. "Requirements" from Required Experience. "Qualifications" maybe from Preferred Experience? Or "Skills". We need to decide headings: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content.
We have content for About the role (Position Overview). Responsibilities (Key Responsibilities). Requirements (Required Experience). Qualifications (Preferred Experience). Skills maybe not separate; could combine with Requirements? But we could have Skills section if there is specific skill content. The posting includes many skill-like items in Required Experience (analytical, writing, facilitating, etc.) Could put them under Requirements. Qualifications could be Preferred Experience.
We should not create Benefits, Pay, Schedule.
We need to use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content.
We have content for About the role (Position Overview). Responsibilities (Key Responsibilities). Requirements (Required Experience). Qualifications (Preferred Experience). Skills maybe not separate; could combine with Requirements? But we could have Skills section if there is specific skill content. The posting includes many skill-like items in Required Experience (analytical, writing, facilitating, etc.) Could put them under Requirements. Qualifications could be Preferred Experience.
We should not create Benefits, Pay, Schedule.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all bullet points from Key Responsibilities, Required Experience, Preferred Experience, and also the intro paragraphs.
We must remove boilerplate: The intro includes "ASI Government provides government leaders..." that's substantive? It's describing company; maybe keep as part of About the role? Could be considered background. The instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that descriptive text as part of About the role.
Also "Department Of War Practice Overview" is substantive; could be part of About the role or separate section? Could be part of About the role as well. But we have limited headings; we could include a section "About the role" that contains both the company overview and the Department of War practice overview and Position Overview.
We need to avoid duplication: There's some duplicated lines? Not seeing.
We must remove EEO etc. At end there is "EQUAL OPPORTUNITY EMPLOYER: ..." truncated; we must remove that.
Also "Why Join ASI Government?" section includes bullet points; we could treat that as "Why Join ASI Government?" but not in allowed headings list. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "Why Join". Should we omit it? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It didn't say we must restrict to those headings only; it gave examples. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings, but maybe we can also use other headings if appropriate? The examples are just examples; but safer to stick to those headings. However "Why Join ASI Government?" is substantive; we could map it to "About the role" or maybe "Qualifications"? Not ideal. Could we create a section "Why Join ASI Government?" as an h3? The instruction didn't forbid other headings, just gave examples. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections; but we could also use other headings if needed? The safer approach: we can incorporate the "Why Join ASI Government?" content into "About the role" or maybe "Qualifications"? But it's about benefits/culture; maybe we could put under "About the role". However we must not lose that info. We'll embed it as a paragraph under About the role.
Similarly, the "BENEFITS:" line is vague; we can ignore as not specific.
Thus final HTML will have sections:
About the role
... (company overview, Department of War practice overview, Position Overview, Why Join ASI Government?)
Responsibilities
with each responsibility as - (the bullet points under Key Responsibilities). Need to preserve all sub-bullets; each bullet is a sentence; we can keep as
- .
Requirements
with each required experience bullet.
Qualifications
with each preferred experience bullet.
We must not include any filler like "commensurate with experience". Not present.
We must ensure no duplicated lines.
Let's extract content.
First, company overview paragraph:
"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."
Next, Department Of War Practice Overview:
"ASI Government’s rapidly growing Department of War portfolio supports defense leaders in achieving mission-critical outcomes for our nation. Our teams work across DoW components, such as the the Army, Navy, Air Force, or Defense Logistics Agency to address complex challenges in acquisition, industrial-base resilience, emerging technology, workforce, and organizational transformation. We bring together deep mission expertise and rigorous consulting capabilities to translate strategic priorities into practical, measurable results. This is an exciting time to join ASI’s DoW portfolio. Team members can contribute across high-priority engagements, work with experienced acquisition, mission, and technical experts, and help develop AI-enabled tools and guidance that make complex government work easier to navigate and execute. We are looking for adaptable, collaborative consultants who can rapidly learn unfamiliar mission areas, create order from complex information, and improve how defense organizations operate."
Next, Position Overview:
"ASI Government is seeking a Senior Consultant to lead acquisition content development workstreams across AI-enabled transformation engagements in its Department of War portfolio. Working under the direction of an ASI Engagement Lead and alongside acquisition subject-matter experts, client stakeholders, user-experience specialists, and technical teams, the Senior Consultant turns complex policies, processes, templates, and institutional knowledge into clear, accurate, and usable content for acquisition professionals. The Senior Consultant independently plans and delivers defined content workstreams, from process discovery and resource assessment through content design, validation, testing, refinement, and implementation. The role requires strong consulting judgment, analytical and writing skills, client facilitation, and the ability to rapidly absorb unfamiliar acquisition processes. The consultant is comfortable operating in ambiguous and fast-paced environments, able to synthesize complex information into actionable recommendations, and skilled at collaborating with leadership and cross-functional teams. The successful candidate connects content and tool development, ensuring that AI-enabled guides, search tools, workflow solutions, training, and job aids reflect user needs, authoritative guidance, and real-world operating conditions."
Next, Why Join ASI Government? bullet points:
"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."
We'll include that as part of About the role maybe as a paragraph after Position Overview.
Now Responsibilities (Key Responsibilities) list:
We need to capture each bullet under the headings: 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 heading is a bold heading; under each there are multiple sentences separated by periods. We need to turn each sentence into a list item? The instruction: "Use - for any list of duties/requirements/benefits". The responsibilities are presented as headings with sentences; we could treat each heading as a list item containing the sentences? But better to break each sentence into its own
- to preserve detail. However that may lose the heading grouping. Could we keep heading as inside
- ? The instruction didn't forbid markup inside
- . We could do
- Process Discovery and Client Engagement: ... sentences...
. That preserves the heading and detail.
Let's extract each heading's content:
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,
for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all bullet points from Key Responsibilities, Required Experience, Preferred Experience, and also the intro paragraphs. We must remove boilerplate: The intro includes "ASI Government provides government leaders..." that's substantive? It's describing company; maybe keep as part of About the role? Could be considered background. The instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep that descriptive text as part of About the role. Also "Department Of War Practice Overview" is substantive; could be part of About the role or separate section? Could be part of About the role as well. But we have limited headings; we could include a section "About the role" that contains both the company overview and the Department of War practice overview and Position Overview. We need to avoid duplication: There's some duplicated lines? Not seeing. We must remove EEO etc. At end there is "EQUAL OPPORTUNITY EMPLOYER: ..." truncated; we must remove that. Also "Why Join ASI Government?" section includes bullet points; we could treat that as "Why Join ASI Government?" but not in allowed headings list. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "Why Join". Should we omit it? The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It didn't say we must restrict to those headings only; it gave examples. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings, but maybe we can also use other headings if appropriate? The examples are just examples; but safer to stick to those headings. However "Why Join ASI Government?" is substantive; we could map it to "About the role" or maybe "Qualifications"? Not ideal. Could we create a section "Why Join ASI Government?" as an h3? The instruction didn't forbid other headings, just gave examples. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections; but we could also use other headings if needed? The safer approach: we can incorporate the "Why Join ASI Government?" content into "About the role" or maybe "Qualifications"? But it's about benefits/culture; maybe we could put under "About the role". However we must not lose that info. We'll embed it as a paragraph under About the role.
Similarly, the "BENEFITS:" line is vague; we can ignore as not specific.
Thus final HTML will have sections:
About the role
About the role
... (company overview, Department of War practice overview, Position Overview, Why Join ASI Government?)
Responsibilities
- with each responsibility as
- (the bullet points under Key Responsibilities). Need to preserve all sub-bullets; each bullet is a sentence; we can keep as
- .
Requirements
- with each required experience bullet.
- for any list of duties/requirements/benefits". The responsibilities are presented as headings with sentences; we could treat each heading as a list item containing the sentences? But better to break each sentence into its own
- to preserve detail. However that may lose the heading grouping. Could we keep heading as inside
- ? The instruction didn't forbid markup inside
- . We could do
- Process Discovery and Client Engagement: ... sentences...
. That preserves the heading and detail. Let's extract each heading's content: 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,
Qualifications
- with each preferred experience bullet.
We must not include any filler like "commensurate with experience". Not present.
We must ensure no duplicated lines.
Let's extract content.
First, company overview paragraph:
"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."
Next, Department Of War Practice Overview:
"ASI Government’s rapidly growing Department of War portfolio supports defense leaders in achieving mission-critical outcomes for our nation. Our teams work across DoW components, such as the the Army, Navy, Air Force, or Defense Logistics Agency to address complex challenges in acquisition, industrial-base resilience, emerging technology, workforce, and organizational transformation. We bring together deep mission expertise and rigorous consulting capabilities to translate strategic priorities into practical, measurable results. This is an exciting time to join ASI’s DoW portfolio. Team members can contribute across high-priority engagements, work with experienced acquisition, mission, and technical experts, and help develop AI-enabled tools and guidance that make complex government work easier to navigate and execute. We are looking for adaptable, collaborative consultants who can rapidly learn unfamiliar mission areas, create order from complex information, and improve how defense organizations operate."
Next, Position Overview:
"ASI Government is seeking a Senior Consultant to lead acquisition content development workstreams across AI-enabled transformation engagements in its Department of War portfolio. Working under the direction of an ASI Engagement Lead and alongside acquisition subject-matter experts, client stakeholders, user-experience specialists, and technical teams, the Senior Consultant turns complex policies, processes, templates, and institutional knowledge into clear, accurate, and usable content for acquisition professionals. The Senior Consultant independently plans and delivers defined content workstreams, from process discovery and resource assessment through content design, validation, testing, refinement, and implementation. The role requires strong consulting judgment, analytical and writing skills, client facilitation, and the ability to rapidly absorb unfamiliar acquisition processes. The consultant is comfortable operating in ambiguous and fast-paced environments, able to synthesize complex information into actionable recommendations, and skilled at collaborating with leadership and cross-functional teams. The successful candidate connects content and tool development, ensuring that AI-enabled guides, search tools, workflow solutions, training, and job aids reflect user needs, authoritative guidance, and real-world operating conditions."
Next, Why Join ASI Government? bullet points:
"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."
We'll include that as part of About the role maybe as a paragraph after Position Overview.
Now Responsibilities (Key Responsibilities) list:
We need to capture each bullet under the headings: 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 heading is a bold heading; under each there are multiple sentences separated by periods. We need to turn each sentence into a list item? The instruction: "Use