Senior AI Engineer

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about company mission, then description of role. We need headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have responsibilities (list of duties). Requirements: "What you'll need to have:" list. Qualifications maybe same as requirements? Could treat "What you'll need to have:" as Requirements. Also "What would be nice for you to have:" could be Skills or Preferred Qualifications. Benefits: there is mention of outstanding benefit programs but no specifics; they say "We demonstrate our commitment by offering outstanding [1] benefit programs". That's vague, not specific. So we should not create Benefits section because no specific benefits listed. Pay: not mentioned. Schedule: hybrid role requiring at least 1 day per week in office locations; that is schedule info. So we can include Schedule section with that detail. Also maybe location info could be part of Schedule or separate? We'll put Schedule. We need to not repeat job title as heading. No Job ID. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the "Why Jack Henry?" sections? That's culture description; could be considered About the role? Might be considered generic but it's substantive about company culture. However instructions: remove EEO/equal-opportunity boilerplate. The "Why Jack Henry?" includes culture description; not EEO. Might keep as part of About the role? But we already have intro about mission. Could combine into About the role section. We need to output only HTML fragment. Let's extract content: Intro: "At Jack Henry, we’re more than a technology company, we’re a force for good in financial services. We’re redefining how community banks and credit unions connect with the people they serve. Our mission is rooted in people inspired innovation, empowering financial institutions to deliver seamless, secure, and human centered experiences. We deliver cutting-edge solutions that are paving the way for the next generation of digital banking and payments, but our true impact begins with our associates. If you're ready to help transform an industry and grow with a company that values purpose, collaboration, and excellence then we’d love to meet you." Then role description: "This Senior AI Engineer bridges AI experimentation and production engineering. This role is responsible for turning AI prototypes, agents, and platform capabilities into reliable, secure, enterprise-ready solutions. Working closely with engineering, cloud infrastructure, cybersecurity, and AI enablement teams, they operationalize AI systems that can scale across Jack Henry while meeting compliance and governance requirements." Then bullet list under that: "* AI Platform Engineering: Build and support production AI capabilities including AI Gateway services, MCP integrations, agent frameworks, self-hosted inference, and AI-powered applications. * Production Readiness & Reliability: Develop testing, evaluation, monitoring, logging, and observability practices that ensure AI systems remain dependable, scalable, and auditable in production. * Cross-Functional Delivery: Partner with cybersecurity, cloud infrastructure, architecture, and business teams to design and deliver AI solutions that meet enterprise standards. * AI Optimization & Governance: Improve AI system performance through model evaluation, operational monitoring, quality assurance, and continuous improvement practices. * Technical Leadership & Adoption: Mentor engineers, establish best practices for AI development, and help drive adoption of AI technologies and agentic development workflows across the organization." Then hybrid location sentence: "This position is a hybrid role requiring at least 1 day per week in any of the following office locations: Allen, TX, Louisville, KY, Birmingham, AL, Cedar Falls, IA, Charlotte, NC, Overland Park, KS, Monett, MO or Springfield, MO. This position is ineligible for immigration sponsorship and support. Please do not apply if at any time you will need immigration support now or in the future (i.e., H-1B, PERM)." Immigration note maybe not needed but it's substantive? It's a restriction; we could keep as part of Schedule or a note. Probably keep as part of Schedule or a separate note but not a heading. We'll include in Schedule paragraph. Then "What you'll be responsible for:" list of duties (many bullet points). We'll treat as Responsibilities. Then "What you'll need to have:" list (requirements). Then "What would be nice for you to have:" list (preferred qualifications/skills). Then motivational paragraph about applying, etc. Might be considered boilerplate? It's encouraging to apply; could be considered application instruction? It's not instruction to apply but encouragement. Might keep as part of About the role? Probably safe to keep as a paragraph under About the role? But it's generic; maybe we can omit as it's not substantive detail about role. The instruction: remove duplicated lines, application instructions. This is not exactly instruction but encouraging to apply; could be considered fluff. Safer to omit. Then "Why Jack Henry?" section with culture description. Might be considered substantive about company; we could include as About the role or separate section like "About Jack Henry". But headings limited to given list; we could use About the role for company overview. We'll include that content in About the role. Then EEO boilerplate: remove. Then "Requests for full corporate job descriptions may be requested through the interview process at any time." That's application instruction; remove. Then "#INDTech References Visible links" and links; remove. Thus final HTML:

  About the role

  At Jack Henry, we’re more than a technology company, we’re a force for good in financial services. We’re redefining how community banks and credit unions connect with the people they serve. Our mission is rooted in people inspired innovation, empowering financial institutions to deliver seamless, secure, and human centered experiences. We deliver cutting-edge solutions that are paving the way for the next generation of digital banking and payments, but our true impact begins with our associates. If you're ready to help transform an industry and grow with a company that values purpose, collaboration, and excellence then we’d love to meet you. This Senior AI Engineer bridges AI experimentation and production engineering. This role is responsible for turning AI prototypes, agents, and platform capabilities into reliable, secure, enterprise-ready solutions. Working closely with engineering, cloud infrastructure, cybersecurity, and AI enablement teams, they operationalize AI systems that can scale across Jack Henry while meeting compliance and governance requirements.

  • AI Platform Engineering: Build and support production AI capabilities including AI Gateway services, MCP integrations, agent frameworks, self-hosted inference, and AI-powered applications.
  • Production Readiness & Reliability: Develop testing, evaluation, monitoring, logging, and observability practices that ensure AI systems remain dependable, scalable, and auditable in production.
  • Cross-Functional Delivery: Partner with cybersecurity, cloud infrastructure, architecture, and business teams to design and deliver AI solutions that meet enterprise standards.
  • AI Optimization & Governance: Improve AI system performance through model evaluation, operational monitoring, quality assurance, and continuous improvement practices.
  • Technical Leadership & Adoption: Mentor engineers, establish best practices for AI development, and help drive adoption of AI technologies and agentic development workflows across the organization.

  Responsibilities

  • Performs and leads system analysis and programming activities that take AI proofs of concept to production-ready software — including the research needed where no established pattern exists yet, and timely, quality delivery into production.
  • Performs, and may lead, technical/engineering support for new and existing applications from code delivery until the retirement of the application.
  • Develops, tests and reviews applications based on business requirements and industry best practices. Uses best practices, standard guidance, and agentic development workflows to create and modify code.
  • Considers how code changes will affect end users and internal teams.
  • Reviews code created by less experienced team members.
  • Collaborates with quality and security partners — cybersecurity, cloud infrastructure, and AI governance — to ensure timely delivery of high-quality products.
  • Performs and may lead work with cross-team as projects dictate.
  • Works on and leads critical tasks and deliverables with no assistance, and sets and updates expectations on size, scope, and timelines.
  • Participates in and may lead team in cross-functional meetings and discussions.
  • Creates required technical documentation.
  • Stays updated with emerging AI technologies and industry trends, recommending innovative solutions to improve software development processes.
  • Adheres to documented departmental and corporate standards.
  • Participates in the definition and documentation of standards — including what "production-ready" means for AI systems at Jack Henry.
  • Lead unit tests, integration tests, and evals to ensure the reliability, security, and performance of developed software, especially AI systems and workflows.
  • Debugs and troubleshoots issues as they arise, providing timely resolutions — including failure modes specific to AI systems, like quality drift, prompt regressions, provider outages, and cost spikes.
  • May contribute to product architecture.
  • May Perform other duties as assigned.

  Requirements

  • Must have a minimum of 6 years of technical experience in software development.
  • Production ownership of AI systems (AI agents, AI features in products, MCP servers, etc).
  • Experience with a major cloud environment (GCP, AWS, or Azure).
  • Experience with unit testing and end-to-end automated testing.
  • Experience with Kubernetes.
  • Experience with any of the following: Large language models (LLM), vector databases.
  • Comfort with ambiguity and shifting priorities.
  • Must be self-directed, and willing to push through roadblocks rather than wait them out.
  • Must be able to travel up to 10% to attend internal business meetings, training and/or professional conferences.

  Preferred Qualifications

  • Bachelor’s degree.
  • Fintech experience.
  • Experience with GCP and infrastructure as code (Terraform).
  • Experience in cloud security and DevOps.
  • Experience with model fine-tuning, evaluation (e.g. controlling for bias), and validation.
  • Experience with AI observability, evals, and model monitoring.

  Schedule

  This position is a hybrid role requiring at least 1 day per week in any of the following office locations: Allen, TX, Louisville, KY, Birmingham, AL, Cedar Falls, IA, Charlotte, NC, Overland Park, KS, Monett, MO or Springfield, MO. This position is ineligible for immigration sponsorship and support; applicants who will need immigration support now or in the future (e.g., H-1B, PERM) should not apply.

  Check we didn't miss any substantive info: The bullet list under role description we included as About the role bullet list. Good. We omitted the "Why Jack Henry?" culture paragraphs; they are somewhat substantive but not required; we could include as part of About the role but we already have a lot. Might be okay to omit as not required heading. The instruction: Prefer a few substantive sections over many thin ones. We have About the role, Responsibilities, Requirements, Preferred Qualifications, Schedule. That's five sections. Could we combine Preferred Qualifications into Skills? But we have no Skills heading; we could use Skills for preferred qualifications. But we already have Preferred Qualifications; it's okay. We must not create Pay/Benefits sections unless posting actually states them. Not present.