Vice President of Research & Development

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 that have real specific content. The posting includes many bullet points under responsibilities etc. We need to parse the posting. The posting is a job description for a role: AI Fluency and Agentic Delivery etc. It includes sections: "AI Fluency and Agentic Delivery", "Technical Roadmap and AI-Driven Opportunity Set", "Delivery and Execution", "Product Quality and Security", "Team Leadership and Development", "Financial and Resource Ownership", "Platform Modernization", "Stakeholder and Executive Communication", "Experience And Qualifications", "Performance Measurement Success In This Role Is Measured On The Following", then bullet list of metrics, then "Salary range: $125,000 - $135,000 USD per year." We need to map to headings: About the role (maybe summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content. The posting does not have explicit sections like "About the role". We can create an "About the role" paragraph summarizing the role? But we must not invent or summarize away detail. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot create a summary that is not directly in the posting. We need to map the content to the allowed headings, but we cannot create headings without real specific content. If the posting doesn't have a clear "About the role" paragraph, we may omit that heading. However we need to include all substantive info somewhere under appropriate headings. We can treat each major bullet grouping as responsibilities, requirements, qualifications, skills, benefits, pay, schedule. Let's identify: - Responsibilities: The duties listed under each heading like "AI Fluency and Agentic Delivery", "Technical Roadmap and AI-Driven Opportunity Set", "Delivery and Execution", "Product Quality and Security", "Team Leadership and Development", "Financial and Resource Ownership", "Platform Modernization", "Stakeholder and Executive Communication". Those are responsibilities. - Requirements/Qualifications: The "Experience And Qualifications" section lists education, years experience, hands-on AI use, etc. Also maybe "Performance Measurement Success..." is about metrics, not requirements. - Skills: Could be implied from responsibilities but we might not have explicit skills list. Could extract skills like "AI development tools", "agentic delivery", "roadmap planning", "governance", "CI/CD", etc. But we must not invent. If not explicitly listed as skills, we might omit Skills section. - Benefits: Not mentioned besides salary range. No benefits like health, 401k. So we should not create Benefits section unless present. - Pay: Salary range given. - Schedule: Not mentioned (no mention of full-time, remote, etc). So omit. Thus we will have sections: Responsibilities, Requirements (or Qualifications), Pay. We need to decide between Requirements and Qualifications. The posting has "Experience And Qualifications". That's a combined section. We could use either heading. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose either Requirements or Qualifications. Since the section is titled "Experience And Qualifications", we could put under Qualifications. Or we could split: Requirements (maybe years experience) and Qualifications (education). But better to put all under Qualifications. We need to preserve all substantive information. So we need to include each bullet point from responsibilities and each bullet from qualifications. We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none. We need to output HTML fragment only. Structure:

Responsibilities

• ...
...

Qualifications

• ...
...

Pay

Salary range: $125,000 - $135,000 USD per year.

We need to ensure we don't repeat job title as heading. Not needed. Now extract responsibilities bullet points. Let's parse the posting: First paragraph: "AI Fluency and Agentic Delivery Use AI development tools personally and daily, holding a current and practical command of what they can and cannot do rather than relying on secondhand reporting.Research and experiment continuously with new AI tooling, models, and workflows, then bring what proves out into the organization's standard practice.Lead every development team to agentic, human-on-the-loop delivery, where AI agents own bounded work end to end while engineers set goals, define guardrails, and review outcomes.Own the AI delivery-maturity roadmap across all actively supported products, applied stage by stage across the lifecycle rather than as a single global rating.Stand up the governance that makes delegated agent work safe, including review gates, validation, security review of AI-generated code, and measurable outcome reporting.Make the codebase and delivery pipeline accessible to AI agents through documentation, test coverage, CI/CD, and structured context.Build the tooling and training program that moves engineers from AI-assisted work, to AI-directed work, to fully delegated agent execution.Report AI delivery maturity and the business outcomes it produces on a recurring executive cadence." That's a block of responsibilities. We can split into separate li items for each sentence? The instruction: Use

• for any list of duties/requirements/benefits. So we need to break into list items. We can treat each sentence as a duty. However some sentences are long and contain multiple duties separated by commas. But we can keep as one li per sentence to preserve info. We need to preserve all substantive information; not invent or summarize away detail. So we should keep each sentence as is, maybe split by periods. Let's split: 1. Use AI development tools personally and daily, holding a current and practical command of what they can and cannot do rather than relying on secondhand reporting. 2. Research and experiment continuously with new AI tooling, models, and workflows, then bring what proves out into the organization's standard practice. 3. Lead every development team to agentic, human-on-the-loop delivery, where AI agents own bounded work end to end while engineers set goals, define guardrails, and review outcomes. 4. Own the AI delivery-maturity roadmap across all actively supported products, applied stage by stage across the lifecycle rather than as a single global rating. 5. Stand up the governance that makes delegated agent work safe, including review gates, validation, security review of AI-generated code, and measurable outcome reporting. 6. Make the codebase and delivery pipeline accessible to AI agents through documentation, test coverage, CI/CD, and structured context. 7. Build the tooling and training program that moves engineers from AI-assisted work, to AI-directed work, to fully delegated agent execution. 8. Report AI delivery maturity and the business outcomes it produces on a recurring executive cadence. Next section: "Technical Roadmap and AI-Driven Opportunity Set Set the multi-year technical roadmap for the Corrections and Law Enforcement product lines, planned against the pace agentic delivery now makes possible rather than the timelines conventional development assumed.Rebuild roadmap assumptions around that acceleration. Pull committed work forward where AI-enabled delivery shortens the build, and direct the recovered capacity toward customer problems that were previously out of reach.Plan the roadmap around customer problems as much as product features, judging each item on whether AI can reach the outcome faster than a conventional build cycle would.Decide deliberately where AI belongs embedded in the products customers buy and where it is better applied as a fast path to a customer outcome, and treat both as revenue opportunities rather than internal efficiency alone.Balance that acceleration against customer commitments already in flight and the realities of an installed base that cannot absorb change at an unlimited rate.Own technology standards, architectural direction, and technical documentation across the portfolio, and hold the development organizations to them.Evaluate build, buy, and consolidation options where product lines overlap, and bring recommendations with supporting analysis to the Executive Vice President.Monitor industry direction, competitor capability, and emerging technology relevant to law enforcement, corrections, and justice software." Split sentences: 1. Set the multi-year technical roadmap for the Corrections and Law Enforcement product lines, planned against the pace agentic delivery now makes possible rather than the timelines conventional development assumed. 2. Rebuild roadmap assumptions around that acceleration. 3. Pull committed work forward where AI-enabled delivery shortens the build, and direct the recovered capacity toward customer problems that were previously out of reach. 4. Plan the roadmap around customer problems as much as product features, judging each item on whether AI can reach the outcome faster than a conventional build cycle would. 5. Decide deliberately where AI belongs embedded in the products customers buy and where it is better applied as a fast path to a customer outcome, and treat both as revenue opportunities rather than internal efficiency alone. 6. Balance that acceleration against customer commitments already in flight and the realities of an installed base that cannot absorb change at an unlimited rate. 7. Own technology standards, architectural direction, and technical documentation across the portfolio, and hold the development organizations to them. 8. Evaluate build, buy, and consolidation options where product lines overlap, and bring recommendations with supporting analysis to the Executive Vice President. 9. Monitor industry direction, competitor capability, and emerging technology relevant to law enforcement, corrections, and justice software. Next: "Delivery and Execution Own release commitments across every development team, including scope, sequencing, and the dates communicated to customers and to sales.Establish a single reporting cadence for status, blockers, and slips so that risk surfaces early rather than at the release gate.Standardize development process, tooling, and engineering metrics across companies that today operate independently.Resolve cross-team dependencies and resource contention, and escalate the trade-offs that require an executive decision." Split: 1. Own release commitments across every development team, including scope, sequencing, and the dates communicated to customers and to sales. 2. Establish a single reporting cadence for status, blockers, and slips so that risk surfaces early rather than at the release gate. 3. Standardize development process, tooling, and engineering metrics across companies that today operate independently. 4. Resolve cross-team dependencies and resource contention, and escalate the trade-offs that require an executive decision. Next: "Product Quality and Security Set and enforce quality standards covering code review, automated testing, defect thresholds, and release readiness, applied equally to human-written and AI-generated code.Maintain the highest levels of product and platform security, promoting a culture and practice of security awareness in every development team.Ensure development activities meet the regulatory, contractual, and industry requirements that apply to public safety and justice customers.Partner with Support Services to close the loop between escalated customer issues and engineering priorities." Split: 1. Set and enforce quality standards covering code review, automated testing, defect thresholds, and release readiness, applied equally to human-written and AI-generated code. 2. Maintain the highest levels of product and platform security, promoting a culture and practice of security awareness in every development team. 3. Ensure development activities meet the regulatory, contractual, and industry requirements that apply to public safety and justice customers. 4. Partner with Support Services to close the loop between escalated customer issues and engineering priorities. Next: "Team Leadership and Development Lead, mentor, and develop the development managers and directors across the portfolio companies, setting clear goals and performance expectations.Recruit and retain engineering talent, and build succession depth in every key technical role.Set the expectation that every engineer works with AI tools as a normal part of the job, and give them the training, access, and time to get there.Structure the organization for the work ahead, including the balance between onshore, offshore, and contract capacity, and the reshaping that agentic delivery makes possible.Promote transparency and collaboration by making priorities, progress, and decisions visible across the organization." Split: 1. Lead, mentor, and develop the development managers and directors across the portfolio companies, setting clear goals and performance expectations. 2. Recruit and retain engineering talent, and build succession depth in every key technical role. 3. Set the expectation that every engineer works with AI tools as a normal part of the job