AI Subject Matter Expert
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info. Ensure we don't lose details like "remote", "contingent hire", "senior level, full-time". Also include citizenship, clearance, etc.
Let's extract details.
About the role paragraph: We'll keep as
.
Responsibilities bullet points: list each.
Let's list them:
- Serve as the contractor team’s senior AI technical advisor to the VHA National AI Institute across the AI inventory, risk management, oversight, and enterprise strategy workstreams.
- Author and maintain AI risk management playbooks, standard operating procedures, guides, and living FAQ documents that enable AI use case owners to satisfy federal and agency risk management requirements.
- Translate federal AI policy into practical, actionable guidance for a non-specialist VHA audience (Executive Order 13960, OMB M-25-21 and M-25-22, and the VA Trustworthy AI Framework).
- Advise AI use case owners on the development and execution of AI risk management plans through working sessions, office hours, and asynchronous support, at a cadence of at least one working session per month.
- Design and execute the AI risk stratification pilot, including a new methodology for evaluating and assigning risk levels to AI systems, and evaluate its results.
- Support VHA business units in creating and updating their AI innovation and governance strategies, covering at least five business units.
- Develop training materials and deliver training webinars for AI use case owners and AI oversight personnel.
- Provide expert content and programming for the VHA AI Assessment Subcommittee, field AI committees, and other centralized governance entities, including trainings and summits.
- Research emerging AI risk management approaches and tools from published and publicly available literature, webinars, and vendor developments for briefings to Institute leadership and government stakeholders.
- Develop AI entrepreneur and adopter playbooks covering both internal development and vendor evaluation pathways.
Make sure to keep parentheses content.
Minimum Qualifications bullet points:
- More than 15 years of experience in the life sciences industry with a focus on creating and delivering data science and artificial intelligence solutions to accelerate healthcare innovation.
- Preferred: eight or more of those years developing or applying AI tools inside a healthcare enterprise at scale.
- Required experience: Previous experience leading efforts to aggregate, analyze, and interpret health information.
- Required experience: Previous experience developing new processes, solutions, and information architectures that leverage a variety of data types including medical images, electronic health records, wearable data, and -omics data.
- Required experience: Previous experience using data platforms to scale machine learning algorithms through a ModelOps AI platform.
- Degree: Doctorate degree in a computational, data science, health informatics, clinical, or life sciences discipline. Any doctorate is eligible, including a DrPH, MD, PhD, or ScD.
- Licensure/certifications: None required. NIST AI Risk Management Framework training or an equivalent AI governance credential preferred.
- Work location: Work is performed at the contractor’s site and no travel is anticipated.
- Clearance: None required. Must be able to obtain and maintain a favorably adjudicated Tier 1 / National Agency Check with Written Inquiries (NACI) background investigation in accordance with VA Handbook 0710. Must complete VA Privacy and Information Security Awareness and Rules of Behavior training (TMS #10176) prior to system access and annually thereafter.
- Citizenship: Must be authorized to work in the United States. All work must be performed within a jurisdiction subject to the law of the United States or its territories.
Desired Qualifications bullet points:
- Command of the federal AI policy and governance landscape, including EO 13960, OMB M-25-21 and M-25-22, the VA Trustworthy AI Framework, and the NIST AI Risk Management Framework.
- Demonstrated ability to move fluidly between deeply technical AI discussion and executive-level strategy conversation with non-technical leadership.
- Experience standing up or operating an AI use case inventory, model registry, or comparable enterprise AI transparency mechanism.
- Experience aggregating, analyzing, and interpreting health information across imaging, EHR, wearable, and -omics data types.
- Familiarity with ModelOps or comparable platforms for scaling machine learning algorithms in production.
- Prior VA, VHA, DoD health, or other federal health agency experience strongly preferred.
- Experience advising clinical stakeholders on AI risk in a health system setting.
- Familiarity with VA Arches or comparable accredited federal AI and analytics environments.
- Experience authoring governance artifacts such as charters, playbooks, SOPs, assessment guides that were actually adopted and used by an operating organization.
- Ability to get up to speed quickly on complex issues; desire to work in a fast-paced, rapidly evolving environment.
- Capable self-starter with a drive to get all types of work done and high attention to detail.
- Outstanding written and verbal communications skills.
- Knowledge of military and Veteran populations.
Also there is "Client Information" about NAII. Could be considered "About the role" maybe but we already have about role. Could add a separate section? Not in allowed list. Could incorporate into About the role or maybe treat as "About the role" extended. But we must not invent sections not allowed. Could we add a section "About the client"? Not allowed. So we should incorporate that info into About the role or maybe as a paragraph under About the role. The instruction: "include a section ONLY when the posting has real, specific content for it". The allowed sections are those headings. We can put client info under About the role as additional paragraph.
Also "About Aptive" description: could be considered "About the company" but not allowed. Could we put under About the role? Might be irrelevant. Probably we should omit duplicated About Aptive as it's boilerplate? It's not boilerplate but it's about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Aptive is not those, but it's not in allowed sections. We could either omit it or incorporate into About the role? The role description already mentions Aptive. The About Aptive repeats earlier content. It's somewhat duplicative. Might be considered duplicated lines? It's repeated twice. We could drop it as duplicate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we can drop the duplicated About Aptive paragraphs.
Thus final HTML will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
We need to decide what goes into Skills. Could extract from Desired Qualifications items that are skill-like: Outstanding written and verbal communications skills, Knowledge of military and Veteran populations, Ability to get up to speed quickly..., Capable self-starter..., Demonstrated ability to move fluidly..., etc. But many desired qualifications are more like experience/knowledge. Could treat Desired Qualifications as Qualifications section, and Skills as maybe a subset? But we have both Qualifications and Skills allowed. We could put Minimum Qualifications under Requirements, Desired Qualifications under Qualifications, and maybe Skills under Skills (like communication, etc). However we risk losing some content if we split incorrectly. Better to treat Minimum Qualifications as Requirements, Desired Qualifications as Qualifications, and maybe Skills empty? But we must not create empty sections. So we need to decide: either combine Desired Qualifications into Qualifications and omit Skills, or split some into Skills.
Given the instruction: "Prefer a few substantive sections over many thin ones." So better to have fewer sections. We could have About the role, Responsibilities, Requirements, Qualifications. That's four sections. That seems good. We can put all desired qualifications under Qualifications. No Skills section.
Thus we will not have Skills, Benefits, Pay, Schedule.
Now we need to ensure we include all substantive info from Minimum Qualifications and Desired Qualifications.
Let's craft HTML.
Structure:
About the role
... (intro paragraph plus client info maybe)
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Make sure to preserve details like "remote", "contingent hire", "senior level, full-time". Those are in intro paragraph.
Let's write intro paragraph: Combine the initial description plus maybe client info.
Original intro: "Aptive Resources is seeking an AI Subject Matter Expert with more than fifteen years of experience in the life sciences industry focused on creating and delivering data science and artificial intelligence solutions that accelerate healthcare innovation. In this role you will be Aptive’s senior AI advisor supporting the Veterans Health Administration’s National Artificial Intelligence Institute by writing the playbooks and risk management guidance that VHA AI use case owners rely on, advising the governance bodies that decide which AI systems reach Veterans, and helping business units across the enterprise build AI strategies that hold up under federal scrutiny. The role is advisory throughout: you will equip and advise government decision-makers rather than make agency decisions. This senior level, full-time position is remote. This is a contingent hire position."
Client Information paragraph: "The National Artificial Intelligence Institute sits within the Digital Health Office of the Veterans Health Administration (VHA). Its mission is to improve the health and well-being of Veterans and to empower the VHA workforce by harnessing the potential of trustworthy AI solutions and emerging technologies. The Institute identifies and matures AI use cases, pursues and tests solutions for
for prose. We need to preserve all substantive info. Ensure we don't lose details like "remote", "contingent hire", "senior level, full-time". Also include citizenship, clearance, etc. Let's extract details. About the role paragraph: We'll keep as
. Responsibilities bullet points: list each. Let's list them: - Serve as the contractor team’s senior AI technical advisor to the VHA National AI Institute across the AI inventory, risk management, oversight, and enterprise strategy workstreams. - Author and maintain AI risk management playbooks, standard operating procedures, guides, and living FAQ documents that enable AI use case owners to satisfy federal and agency risk management requirements. - Translate federal AI policy into practical, actionable guidance for a non-specialist VHA audience (Executive Order 13960, OMB M-25-21 and M-25-22, and the VA Trustworthy AI Framework). - Advise AI use case owners on the development and execution of AI risk management plans through working sessions, office hours, and asynchronous support, at a cadence of at least one working session per month. - Design and execute the AI risk stratification pilot, including a new methodology for evaluating and assigning risk levels to AI systems, and evaluate its results. - Support VHA business units in creating and updating their AI innovation and governance strategies, covering at least five business units. - Develop training materials and deliver training webinars for AI use case owners and AI oversight personnel. - Provide expert content and programming for the VHA AI Assessment Subcommittee, field AI committees, and other centralized governance entities, including trainings and summits. - Research emerging AI risk management approaches and tools from published and publicly available literature, webinars, and vendor developments for briefings to Institute leadership and government stakeholders. - Develop AI entrepreneur and adopter playbooks covering both internal development and vendor evaluation pathways. Make sure to keep parentheses content. Minimum Qualifications bullet points: - More than 15 years of experience in the life sciences industry with a focus on creating and delivering data science and artificial intelligence solutions to accelerate healthcare innovation. - Preferred: eight or more of those years developing or applying AI tools inside a healthcare enterprise at scale. - Required experience: Previous experience leading efforts to aggregate, analyze, and interpret health information. - Required experience: Previous experience developing new processes, solutions, and information architectures that leverage a variety of data types including medical images, electronic health records, wearable data, and -omics data. - Required experience: Previous experience using data platforms to scale machine learning algorithms through a ModelOps AI platform. - Degree: Doctorate degree in a computational, data science, health informatics, clinical, or life sciences discipline. Any doctorate is eligible, including a DrPH, MD, PhD, or ScD. - Licensure/certifications: None required. NIST AI Risk Management Framework training or an equivalent AI governance credential preferred. - Work location: Work is performed at the contractor’s site and no travel is anticipated. - Clearance: None required. Must be able to obtain and maintain a favorably adjudicated Tier 1 / National Agency Check with Written Inquiries (NACI) background investigation in accordance with VA Handbook 0710. Must complete VA Privacy and Information Security Awareness and Rules of Behavior training (TMS #10176) prior to system access and annually thereafter. - Citizenship: Must be authorized to work in the United States. All work must be performed within a jurisdiction subject to the law of the United States or its territories. Desired Qualifications bullet points: - Command of the federal AI policy and governance landscape, including EO 13960, OMB M-25-21 and M-25-22, the VA Trustworthy AI Framework, and the NIST AI Risk Management Framework. - Demonstrated ability to move fluidly between deeply technical AI discussion and executive-level strategy conversation with non-technical leadership. - Experience standing up or operating an AI use case inventory, model registry, or comparable enterprise AI transparency mechanism. - Experience aggregating, analyzing, and interpreting health information across imaging, EHR, wearable, and -omics data types. - Familiarity with ModelOps or comparable platforms for scaling machine learning algorithms in production. - Prior VA, VHA, DoD health, or other federal health agency experience strongly preferred. - Experience advising clinical stakeholders on AI risk in a health system setting. - Familiarity with VA Arches or comparable accredited federal AI and analytics environments. - Experience authoring governance artifacts such as charters, playbooks, SOPs, assessment guides that were actually adopted and used by an operating organization. - Ability to get up to speed quickly on complex issues; desire to work in a fast-paced, rapidly evolving environment. - Capable self-starter with a drive to get all types of work done and high attention to detail. - Outstanding written and verbal communications skills. - Knowledge of military and Veteran populations. Also there is "Client Information" about NAII. Could be considered "About the role" maybe but we already have about role. Could add a separate section? Not in allowed list. Could incorporate into About the role or maybe treat as "About the role" extended. But we must not invent sections not allowed. Could we add a section "About the client"? Not allowed. So we should incorporate that info into About the role or maybe as a paragraph under About the role. The instruction: "include a section ONLY when the posting has real, specific content for it". The allowed sections are those headings. We can put client info under About the role as additional paragraph. Also "About Aptive" description: could be considered "About the company" but not allowed. Could we put under About the role? Might be irrelevant. Probably we should omit duplicated About Aptive as it's boilerplate? It's not boilerplate but it's about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Aptive is not those, but it's not in allowed sections. We could either omit it or incorporate into About the role? The role description already mentions Aptive. The About Aptive repeats earlier content. It's somewhat duplicative. Might be considered duplicated lines? It's repeated twice. We could drop it as duplicate. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we can drop the duplicated About Aptive paragraphs. Thus final HTML will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We need to decide what goes into Skills. Could extract from Desired Qualifications items that are skill-like: Outstanding written and verbal communications skills, Knowledge of military and Veteran populations, Ability to get up to speed quickly..., Capable self-starter..., Demonstrated ability to move fluidly..., etc. But many desired qualifications are more like experience/knowledge. Could treat Desired Qualifications as Qualifications section, and Skills as maybe a subset? But we have both Qualifications and Skills allowed. We could put Minimum Qualifications under Requirements, Desired Qualifications under Qualifications, and maybe Skills under Skills (like communication, etc). However we risk losing some content if we split incorrectly. Better to treat Minimum Qualifications as Requirements, Desired Qualifications as Qualifications, and maybe Skills empty? But we must not create empty sections. So we need to decide: either combine Desired Qualifications into Qualifications and omit Skills, or split some into Skills. Given the instruction: "Prefer a few substantive sections over many thin ones." So better to have fewer sections. We could have About the role, Responsibilities, Requirements, Qualifications. That's four sections. That seems good. We can put all desired qualifications under Qualifications. No Skills section. Thus we will not have Skills, Benefits, Pay, Schedule. Now we need to ensure we include all substantive info from Minimum Qualifications and Desired Qualifications. Let's craft HTML. Structure:
About the role
... (intro paragraph plus client info maybe)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...