Senior Software Engineer, AI & Automation

We need to output HTML fragment with sections: About the role? Actually the posting includes "About NCR VOYIX" then "Senior Software Engineer, AI & Automation Onsite Position: Atlanta, GA". The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include based on content. We have: - About NCR VOYIX (company description). Could be "About the role"? Actually "About the role" is a heading suggestion, but we have "About NCR VOYIX". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests these as examples. We could use "About the company" maybe but they didn't list. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings if appropriate. The posting includes "About NCR VOYIX" which is about the company, not the role. Could we treat that as "About the role"? Might be okay but better to reflect actual content: "About NCR VOYIX". However they didn't list that as example but didn't forbid. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Means we should use

for headings, and those are examples of typical headings. We can still use other headings as needed, but they'd be

. Probably safe to use "About NCR VOYIX" as heading. Then we have responsibilities: "What You'll Do" with subsections: AI Engineering & Agent Development, Technical Leadership & Software Delivery, Cloud Platform & Automation, Collaboration & Customer Focus. Those are responsibilities. Could group under a single "Responsibilities" heading with bullet lists. Then qualifications: "Qualifications Required" and "Preferred". Could be "Qualifications" heading with required and preferred bullet lists. Technical Skills: list of languages etc. Could be "Skills" heading. Benefits, Pay, Schedule: Not mentioned. So we should not include those sections. We must remove boilerplate: EEO statement, etc. Also remove "Offers of employment are conditional upon passage of screening criteria applicable to the job". That's boilerplate? Might be considered legal; remove. Also remove "Statement to Third Party Agencies" and the quote about emails. Remove duplicated lines. We need to preserve all substantive information: company description, role description, responsibilities bullet points, qualifications required, preferred, technical skills. We must not invent or summarize away detail. So we need to keep each bullet point as is, maybe rephrase? No, preserve exactly. We need to output only HTML fragment, no markdown fences. Let's extract content. Company description: "NCR Voyix Corporation (NYSE: VYX) is a global platform-powered leader in unified commerce for shopping and dining. Combining a flexible, intelligent platform with end-to-end payments capabilities and services developed through its deep industry experience, NCR Voyix empowers retailers and restaurants to accelerate new possibilities for their operations, experiences and business outcomes. NCR Voyix is headquartered in Atlanta, Georgia, and serves customers in more than 35 countries worldwide." That's substantive. Then role title line: "Senior Software Engineer, AI & Automation Onsite Position: Atlanta, GA". We should not repeat job title as heading, but we can include location maybe in a short

. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include location in a paragraph. Then "We are seeking a Senior Software Engineer with 5+ years of software development experience to join a team building intelligent automation solutions in the payments and commerce space. The ideal candidate brings experience from organizations focused on point-of-sale (POS), payments, fintech, or transaction processing systems, along with expertise in AI-driven software development, cloud-native architectures, and large-scale automation. This individual will play a key role in designing and building AI-powered agents that automate complex software modernization, deployment, and implementation processes. The first major initiative will focus on developing autonomous agents that accelerate the migration of legacy POS software to modern platforms by analyzing, transforming, validating, and deploying software changes with minimal human intervention. Beyond this initial project, the engineer will help establish a scalable AI automation framework and continue building intelligent agents that improve implementation, support, operational efficiency, and customer experiences across the organization." That's more description; could be part of "About the role" or responsibilities. We'll treat as part of role overview. Then "What You'll Do" with subheadings and bullet points. Let's capture each bullet. Under "AI Engineering & Agent Development": - Design, develop, and deploy AI-powered agents that automate software migration, deployment, configuration, and operational workflows. - Build intelligent systems capable of assisting with or fully automating the conversion of legacy POS applications to modern architectures. - Create agentic workflows that can analyze existing software, recommend code transformations, execute changes, and validate outcomes. - Develop reusable AI frameworks, orchestration patterns, and automation services that can be applied across multiple business functions. - Evaluate and integrate emerging AI technologies, LLMs, and agent frameworks to improve engineering productivity and customer outcomes. - Partner with product and engineering teams to identify new opportunities for AI-driven automation. Under "Technical Leadership & Software Delivery": - Lead the translation of business and customer requirements into scalable, maintainable AI-enabled solutions. - Serve as a technical leader for AI initiatives, helping define architecture, standards, and best practices. - Design, develop, and maintain high-performance software with a focus on reliability, security, scalability, and observability. - Drive architectural decisions related to cloud-native AI services, automation platforms, and software modernization efforts. - Contribute hands-on code in Golang and other technologies as needed. Under "Cloud Platform & Automation": - Build and manage AI solutions within Google Cloud Platform (GCP). - Develop cloud-native services supporting AI agent execution, orchestration, monitoring, and lifecycle management. - Integrate AI capabilities into CI/CD pipelines, deployment automation, and software delivery processes. - Improve operational efficiency through intelligent automation and DevOps-driven engineering practices. - Design systems that reduce implementation timelines and dependency on manual installation activities. Under "Collaboration & Customer Focus": - Partner closely with Product Management, Customer Support, Professional Services, and other stakeholders to identify automation opportunities. - Occasionally engage directly with customers and implementation teams to understand real-world deployment environments and validate automation solutions. - Observe customer workflows and product implementations to continuously improve AI agent effectiveness. - Act as a trusted technical advisor on AI strategy, automation opportunities, and software modernization initiatives. - Mentor engineers on AI adoption, automation patterns, software quality, and emerging technologies. Then "Qualifications Required" bullet list: - 5+ years of professional software engineering experience. - Experience designing and building automation solutions using AI, machine learning, agent-based systems, or intelligent workflows. - Strong experience with Golang development. - Experience building and supporting cloud-native applications and services. - Experience with Google Cloud Platform (GCP) or similar cloud platforms. - Strong understanding of software architecture, APIs, distributed systems, and modern engineering practices. - Experience with CI/CD pipelines, DevOps automation, and containerized deployments. - Ability to translate complex business problems into scalable technical solutions. - Experience leading technical initiatives and mentoring engineers. Then "Preferred Experience" bullet list: - Experience building AI agents, agentic workflows, autonomous systems, or LLM-powered applications. - Experience using AI to automate software modernization, code migration, code generation, or deployment processes. - Experience working within payments, fintech, transaction processing, or POS environments. - Experience building platforms that automate technical implementation or onboarding activities. - Experience with vector databases, retrieval-augmented generation (RAG), agent orchestration frameworks, or AI development platforms. - Experience serving as a technical lead or architect on enterprise-scale applications. - Direct customer-facing experience working alongside implementation or professional services teams. Then "Technical Skills" list: - Languages: Golang (preferred), C#, Java, JavaScript - AI & Automation: LLMs, AI agent frameworks, prompt engineering, agent orchestration, workflow automation, AI-assisted development tools - Cloud & Infrastructure: Google Cloud Platform (GCP), Kubernetes, containerized applications - Databases: SQL, vector databases preferred - DevOps & Tooling: GitHub, CI/CD pipelines, Infrastructure as Code, containerization technologies - Frontend: React - Agile Tools: Jira - Modern Engineering Practices: AI-assisted coding, developer productivity tools, automated testing, observability, monitoring, and software modernization We need to format these as

• for any list of duties/requirements/benefits. So each bullet list becomes
  • items. We need to decide sections. Potential sections: - About NCR VOYIX (company overview) maybe as

    About NCR VOYIX

    then

    ...

    - Role Overview (maybe

    About the role

    ) containing the paragraph about seeking Senior Software Engineer etc. - Responsibilities (

    Responsibilities

    ) containing the four subcategories? Could either keep subheadings inside responsibilities as

    but they said use

    for section headings. Could use

    for each subcategory? But they'd be headings; we could treat each as its own section but that may be many thin sections. They said prefer a few substantive sections over many thin ones. So maybe combine all responsibilities under one

    Responsibilities

    and then have subheadings as

    or just bold? But they only specified

    for section headings; they didn't forbid other heading levels. Safer to use

    for each major section: Responsibilities, Qualifications, Skills. Within Responsibilities we could keep the subheadings as

    or just as inside

    . But the instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other heading levels, but to be safe we can use

    for each of those sections, and within them we can use

    for sub-sections if needed. However they said "Prefer a few substantive sections over many thin ones." So maybe we should not create many sections like each subheading as its own

    . Better to have one Responsibilities section with bullet lists that include the subheading text as part of the bullet? But we need to preserve the subheading text; we could incorporate them as inside a

    that starts a new group? However the bullet lists under each subheading are distinct; we could keep them as separate

    but preceded by a

    for the subheading. That would create many thin sections (subheadings) but they are not major sections; they are sub-sections within Responsibilities. The instruction about preferring few substantive sections likely refers to top