Senior AI Governance Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: First paragraph: "We are seeking a highly skilled Senior AI Governance Analyst to lead the development, implementation, and oversight of governance frameworks that ensure our predictive and generative AI systems are safe, ethical, secure, and compliant with federal standards. The Senior AI Governance Analyst will serve as a subject-matter expert across responsible AI, policy compliance, risk management, and AI assurance throughout the lifecycle of AI solutions. This role partners closely with engineers, product teams, evaluators, and client stakeholders to embed governance principles into design, development, deployment, and ongoing operations." That's about the role. Then "Contributions" list: bullet points: - Lead the development and implementation of AI governance frameworks aligned to federal policies, NIST AI Risk Management Framework, MLSecOps, agency-specific guidance, and emerging regulatory requirements. - Drive AI risk identification, assessment, and mitigation processes, ensuring that generative and predictive AI systems adhere to ethical, legal, and security standards. - Oversee the creation and maintenance of AI documentation artifacts such as model cards, data cards, lineage records, impact assessments, and system risk profiles. - Collaborate with engineering and product teams to embed privacy, fairness, transparency, and explainability considerations into the design and operation of AI systems. - Partner with AI Evaluation Scientists to establish governance-aligned quality thresholds, safety checks, and ongoing monitoring requirements for model outputs. - Support compliance activities related to data usage, provenance, confidentiality, prompt injection defense, and secure model interaction patterns. - Develop governance review processes, including AI readiness assessments, model approval workflows, and continuous assurance procedures. - Conduct research on emerging AI regulatory trends, industry standards, federal mandates, and best practices, advising leadership on their implications. - Communicate governance requirements and findings to diverse audiences, ensuring that stakeholders across programs understand risks, constraints, and recommended controls. - Mentor junior analysts and contribute to the creation of templates, playbooks, and reusable assets that strengthen Steampunk’s AI governance capabilities. - You will contribute to the growth of our AI & Data Exploitation Practice! That's responsibilities. Then "Qualifications" heading: bullet list: - Ability to hold a position of public trust with the U.S. government. - Bachelor’s, Master’s, or Ph.D. in Public Policy, Computer Science, Law, Cybersecurity, Data Ethics, or a related field. - 5+ years of experience in AI governance, risk management, data ethics, compliance, or responsible technology roles. - Strong understanding of federal policies, standards, and frameworks related to AI, including NIST AI RMF, EO 14110, OMB AI guidance, MLSecOps, privacy law , and agency-level directives. - Demonstrated experience embedding governance controls into AI/ML development workflows, including documentation, reviews, and lifecycle risk management. - Familiarity with LLMs, RAG systems, and generative AI architectures, and an ability to assess risks across these technologies. - Experience conducting algorithmic impact assessments, model risk assessments, or responsible AI reviews. - Strong communication skills with the ability to clearly articulate governance requirements to engineers, product teams, executives, and government clients. - Ability to analyze technical systems, identify risks, and recommend actionable mitigations grounded in policy and best practices. - Exposure to evaluation techniques, fairness assessments, transparency documentation, or audit processes preferred. - Experience working in agile environments, collaborating across cross-functional teams, and driving governance processes independently. Then "About Steampunk" paragraph: "Steampunk relies on several factors to determine salary, including but not limited to geographic location, contractual requirements, education, knowledge, skills, competencies, and experience. The projected compensation range for this position is $120,000 to $150,000. The estimate displayed represents a typical annual salary range for this position. Annual salary is just one aspect of Steampunk’s total compensation package for employees. Learn more about additional Steampunk benefits here." Then "Identity Statement" etc: "As part of the application process, you are expected to be on camera during interviews and assessments. We reserve the right to take your picture to verify your identity and prevent fraud." That's boilerplate? It's about application process, maybe we should remove as it's application instructions? The instruction says remove application instructions. So we should drop that. Then "Steampunk is a Change Agent..." paragraph about company story. That's maybe "About Steampunk" but we already have about Steampunk paragraph earlier. The later paragraph is more about company mission. Could be considered "About Steampunk" but we already have a section about Steampunk? The instruction says we can have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company" section defined. So we should not create a section for that; we can incorporate relevant info into existing sections if appropriate, but we must not invent sections. The "About Steampunk" paragraph includes salary and benefits info. We already have Pay and Benefits sections. The later paragraph about company story is not needed for any defined section; we can drop it as it's not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. However we cannot create arbitrary sections; we must only use the allowed headings. If info doesn't fit any allowed heading, we might need to incorporate into existing sections if possible, or maybe we can omit if it's boilerplate? The later paragraph about company story is substantive but not about role, responsibilities, qualifications, etc. It's about the company. There's no heading for "About the company". The instruction says we can use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they want only those. Safer to stick to those. The company story may be considered "About the role"? Not really. Could be considered "About Steampunk" but not in list. Might be considered boilerplate? It's not legal/EEO. It's descriptive. Might be considered part of "About the role"? Not ideal. We could incorporate the company story into a paragraph under "About the role" maybe as extra context. But that might be stretching. Alternatively, we could create a section "About Steampunk" as an h3, but it's not in the examples. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not an exhaustive list. So we could add other headings if needed, but they said "Prefer a few substantive sections over many thin ones." So we could add About Steampunk if it's substantive. However they also said "include a section ONLY when the posting has real, specific content for it". The posting does have real content about Steampunk (the later paragraph). So we could add an "About Steampunk" section. But we already have a paragraph earlier about Steampunk that mentions salary and benefits. That could be merged. Better to have sections: About the role, Responsibilities, Qualifications, Pay, Benefits. Possibly Skills? The posting mentions skills implicitly but not a separate list. Could combine skills into Qualifications. The instruction says we can have Skills section if there is real specific content. There's no explicit skills list separate from qualifications. So we may omit Skills. Schedule: no info. So omit. Requirements: The qualifications list includes requirements; we could treat Qualifications as requirements. The instruction distinguishes Requirements and Qualifications; but we can combine if needed. However we have both headings possible. The posting has "Qualifications" heading. There's no separate "Requirements". So we could use Qualifications section for those bullet points. Could also have a Requirements section for things like "Ability to hold a position of public trust with the U.S. government." but that's also qualification. So we can just have Qualifications. Thus sections: About the role, Responsibilities, Qualifications, Pay, Benefits. We need to extract Pay and Benefits from the posting. Pay: "The projected compensation range for this position is $120,000 to $150,000." Also mention that salary is one aspect of total compensation. Benefits: "Learn more about additional Steampunk benefits here." That's a link but we don't have URL. The posting says "Learn more about additional Steampunk benefits here." No details. That's vague; not specific benefit details. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting mentions benefits but does not list them; just says learn more. Is that enough to create a Benefits section? It states there are benefits but not specifics. The instruction says never create a section with filler/placeholder text like "not specified", "N/A", "varies", "TBD". "Learn more about additional Steampunk benefits here." is not a specific benefit; it's a placeholder. So we should not create a Benefits section because no specific benefits are listed. We could incorporate the sentence into Pay section maybe as note about total compensation. But we should not create a Benefits heading with no specifics. Thus we have About the role, Responsibilities, Qualifications, Pay. Pay section: include the salary range and note that annual salary is one aspect of total compensation. We also have the earlier line: "Steampunk relies on several factors to determine salary, including but not limited to geographic location, contractual requirements, education, knowledge, skills, competencies, and experience." That's also about pay determination. Include that. Thus Pay section content: combine those. Now we need to format. Use

for each section heading. Inside each section, use

for prose,

• for lists. About the role: prose from first paragraph(s). Could be two paragraphs: the initial description and maybe the "You will contribute to the growth..."? That's actually part of contributions list. So About the role: the initial paragraph(s) before "Contributions". That is: "We are seeking a highly skilled Senior AI Governance Analyst to lead the development, implementation, and oversight of governance frameworks that ensure our predictive and generative AI systems are safe, ethical, secure, and compliant with federal standards. The Senior AI Governance Analyst will serve as a subject-matter expert across responsible AI, policy compliance, risk management, and AI assurance throughout the lifecycle of AI solutions. This role partners closely with engineers, product teams, evaluators, and client stakeholders to embed governance principles into design, development, deployment, and ongoing operations." That's it. Responsibilities: the bullet list under "Contributions". We'll output as
  • each. Qualifications: bullet list under "Qualifications". We'll output as
    • . Pay: prose: combine the sentences about salary determination and range and total compensation note. We should not include the "Learn more about additional Steampunk benefits here." line. We should also not include the Identity Statement, company story, EEO, etc. Now produce HTML fragment. Check for any repeated content: ensure we didn't miss any substantive info. Check the responsibilities list: we have 11 bullets. Let's copy them exactly. - Lead the development and implementation of AI governance frameworks aligned to federal policies, NIST AI Risk Management Framework, MLSecOps, agency-specific guidance, and emerging regulatory requirements. - Drive AI risk identification, assessment, and mitigation processes, ensuring that generative and predictive AI systems adhere to ethical, legal, and security standards. - Oversee the creation and maintenance of AI documentation artifacts such as model cards, data cards, lineage records, impact assessments, and system risk profiles. - Collabor