Senior Consultant, AI-Enabled Transformation

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. The posting includes: - Intro about ASI Government (company description). Could be "About the role" or maybe "About the company"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections are present. We have content: description of role, responsibilities (multiple bullet-like paragraphs). There's a "Key Responsibilities" heading with subheadings: Client Engagement and Consulting Delivery, Workstream Planning and Execution, AI Prototype Implementation and Adoption, Team and Partner Coordination, Engagement Operations and Growth Support. Under each there are bullet-like sentences. We have "Required" section with bullet-like requirements. We have "Preferred" section. We have "Why Join ASI Government?" with bullet points. We have "BENEFITS:" line: "ASI Government offers a comprehensive benefit package to our employees. Benefits can be viewed on our careers site." That's vague; not specific benefits listed. According to rule: do NOT create Benefits section unless posting actually states them. It says "Benefits can be viewed on our careers site." That's not specific content; it's a placeholder. So we should NOT include Benefits section. Pay: Not mentioned. So no Pay section. Schedule: Not mentioned. So no Schedule section. Skills: Could be derived from Required/Preferred but we have separate sections for Requirements and Qualifications maybe. The instruction list includes Skills as possible heading. We could put skills under Requirements or Qualifications. But we need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Skills. We have Required and Preferred; we could combine into Requirements (maybe includes both required and preferred). Or we could have Requirements (required) and Qualifications (preferred). The posting has "Required" and "Preferred". So we can make Requirements for required, Qualifications for preferred. Or we could have Skills separate. But we have both required and preferred; we can treat Required as Requirements, Preferred as Qualifications. That seems appropriate. We also have "Why Join ASI Government?" which could be considered "About the role" or maybe a separate section like "Why Join ASI Government?" but not in the list. The instruction only lists those example headings; we could still add other headings? 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 likely we should stick to those. "Why Join ASI Government?" could be considered part of About the role or maybe a separate section like "Why Join ASI Government?" but not in list. Safer to incorporate that content into About the role or maybe a separate "Why Join ASI Government?" but risk deviating. I'd include it as part of About the role (company overview and why join). Or we could make a section "About the role" containing the introductory paragraphs about ASI and the role, plus the "Why Join ASI Government?" bullet points. Thus sections: - About the role: includes company overview, role description, and why join. - Responsibilities: the key responsibilities bullet points (maybe grouped under subheadings but we can just list as

• each responsibility sentence). We need to preserve all substantive information; we can keep the subheadings as part of
• text or maybe as inside
• . But we should not create extra headings beyond

  . So we can embed subheadings as plain text within

  . - Requirements: the Required bullet points. - Qualifications: the Preferred bullet points. - Skills: maybe not needed if we covered in Requirements/Qualifications. But we could extract skills like "Strong structured problem-solving skills", "Excellent written and verbal communication skills", etc. However those are already in Required. So we could omit Skills section to avoid thin sections. Thus we will output:

  About the role

  ... (company description and role summary and why join)

  Responsibilities

  • ... each responsibility bullet
  ...

  Requirements

  • ... each required bullet
  ...

  Qualifications

  • ... each preferred bullet
  ...

  We must not repeat job title as heading. The job title is "Senior Consultant". Not used as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO, E-Verify, Reasonable Accommodations, etc. Also remove navigation/cookie/legal etc. The posting includes those at bottom; we need to drop them. We must preserve all substantive information. So we need to include the company description paragraphs, the role description, the "Why Join ASI Government?" bullet points, responsibilities, required, preferred. Let's extract content. Original text: "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 you thrive on creating unique and impactful value for Federal clients? Are you passionate about partnering with clients and collaborating to create solutions? Do you enjoy the opportunity to drive change that impacts our nation? We are looking for smart, curious, driven individuals to join us in partnering with our client to help them solve some of the nation’s most challenging problems. ASI Government serves as a trusted adviser to government leaders seeking improved performance, enhanced organization effectiveness, and strategic change. ASI Government is seeking a Senior Consultant to support AI-enabled transformation engagements across our rapidly growing Department of War (DoW) portfolio. For over 30 years, ASI has served as a trusted adviser to government leaders, impacting more than 70 agencies across the defense, intelligence, and civilian communities. Our DoW teams support components such as the Navy, Air Force, and Defense Logistics Agency on complex challenges in acquisition, industrial-base resilience, emerging technology, workforce, and organizational transformation. Working under the direction of an ASI Engagement Lead and alongside acquisition, mission, data, and technical specialists, the Senior Consultant independently leads defined workstreams and serves as a reliable day-to-day point of contact for clients, ASI colleagues, and teaming partners. You will help move AI, automation, and process-improvement initiatives from discovery through piloting, adoption, and scale, translating client needs into structured workplans, rigorous analysis, and executive-ready recommendations. Deep software-development expertise is not required; the ability to engage credibly in technical discussions and convert them into decisions, risks, and actions is essential." Then "Key Responsibilities" with subheadings and bullet-like sentences. Let's extract each responsibility sentence. Under "Client Engagement and Consulting Delivery": - Build trusted day-to-day working relationships with client stakeholders and represent ASI professionally in meetings, working sessions, demonstrations, and decision forums. - Support engagement leaders in managing client expectations, communications, meeting cadence, and stakeholder alignment. - Structure ambiguous client questions, gather and synthesize relevant information, and develop practical recommendations grounded in the client mission and operating environment. - Plan and facilitate working sessions, status reviews, user discussions, and other client interactions; document decisions, actions, owners, and next steps. - Develop polished presentations, analyses, meeting materials, written products, and recurring engagement reporting for client and ASI leadership review. Under "Workstream Planning and Execution": - Lead one or more defined workstreams from planning through delivery, with accountability for workplan, milestones, dependencies, actions, and quality within the assigned scope. - Coordinate work across mission, acquisition, process, change-management, data, and technical contributors so activities remain aligned and handoffs occur on time. - Maintain an integrated view of open actions, decisions, risks, and dependencies, including content development, tool development, client approvals, stakeholder engagement, testing, training, and implementation activities. - Proactively identify delivery issues and emerging risks; develop proposed mitigations and elevate matters requiring engagement-lead or client decisions. - Step into adjacent workstreams when needed to meet critical deadlines and advance shared client outcomes. Under "AI Prototype Implementation and Adoption": - Support discovery and requirements activities by documenting user needs, current processes, pain points, operational constraints, and desired outcomes. - Identify potential automation opportunities to improve operational efficiency, reduce manual effort, and strengthen mission outcomes. - Help translate mission and business requirements into clear inputs for technical teams and confirm that emerging solutions remain aligned to user and program needs. - Coordinate prototype demonstrations, user testing, feedback collection, refinement, training, change management, and performance evaluation. - Track technical and implementation dependencies such as data access, system integration, cybersecurity or authorization activities, content readiness, and deployment approvals in coordination with responsible experts. - Translate technical progress into clear client-ready updates, talking points, risks, recommendations, and decisions without overstating technical expertise. - Capture lessons learned and reusable approaches that support solution improvement and responsible scaling across organizations or mission areas. Under "Team and Partner Coordination": - Coordinate day-to-day collaboration among ASI staff, subcontractors, and other partners, maintaining clear roles, responsibilities, interfaces, and follow-through. - Surface information gaps and cross-team dependencies early and help resolve them through disciplined communication and action tracking. - Contribute to a cohesive team environment by sharing information, providing constructive feedback, and supporting colleagues across disciplines. - Help ensure ASI’s contributions are visible, well integrated, and consistent with its role on the engagement. Under "Engagement Operations and Growth Support": - Support accurate contract reporting, resource tracking, program reviews, and compliance with engagement requirements and internal management expectations. - Monitor assigned work against scope, schedule, and quality expectations and promptly flag issues that could affect performance. - Identify unmet client needs, potential follow-on opportunities, and reusable capabilities; share observations and supporting evidence with engagement and growth leaders. - Contribute client insight, delivery experience, and draft content to proposals, account planning, and the development of repeatable AI-enabled offerings. Now "Required" section: "Required 5+ years of professional experience supporting federal or commercial consulting engagements, complex programs, digital transformation, process improvement, or comparable client-service work, with demonstrated growth in responsibility. Experience independently leading a defined workstream or major project component involving multiple stakeholders, dependencies, and deliverables. Strong structured problem-solving skills and the ability to turn incomplete information into organized analysis, practical options, and clear next steps. Excellent written and verbal communication skills, including developing polished PowerPoint presentations, written products, and status reporting. Strong facilitation, stakeholder-management, and follow-through skills, with close attention to accuracy and detail. Ability to participate credibly in technical discussions and translate outcomes into actions, risks, and client communications without requiring deep software-engineering or data-science expertise. Bachelor's degree. S. citizenship and the 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." Note: "S. citizenship" likely means "U.S. citizenship". We'll keep as is. Now "Preferred" section: "Preferred Understanding of federal and/or Department of War acquisition. Experience supporting DoW or other federal clients in acquisition, logistics, readiness, industrial base, workforce, or organizational transformation. Prior management, strategy, or transformation consulting, or federal professional-services experience. Familiarity with AI and machine learning, generative AI, robotic process automation, intelligent automation, or data analytics in a federal context. Experience supporting AI or digital products through discovery, requirements, prototyping, testing, implementation, change management, and adoption. Familiarity with federal cybersecurity, data-access, system-integration, or ATO processes. Experience working within integrated prime and subcontractor teams. Advanced degree, PMP