Java Full Stack AI Architect

We need to output HTML fragment with sections: headings

for sections present. The posting includes Overview (but we shouldn't repeat job title). The content includes Overview paragraph(s). Then "In the assigned Job Role of Architecture Consultant 2, your Area Of Responsibility will be as below:" then bullet list of responsibilities. Then "Your Contribution To The Team" then bullet list of contributions. Then "Required Skill And Experience" then bullet list? Actually it's sentences. Then "Preferred Skill And Experience". Then "Additional Required Qualifications". Then "Benefits". Then "About Us". Then EEO (should be removed). Also need to remove cookie/navigation/legal/EEO boilerplate, duplicated lines, application instructions. There's no explicit application instructions. We need to preserve all substantive information, not invent or summarize away detail. Use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections when posting has real specific content. The headings we can use: maybe "Overview" is not in list but we can use "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings, but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to map content to those headings where appropriate. For example, Overview could be "About the role". Responsibilities heading for responsibilities. Requirements heading for required skill and experience? Qualifications heading for additional required qualifications? Skills heading for preferred skill and experience? Benefits heading for benefits. Pay and Schedule only if present; they are not present (no pay/schedule specifics). So we should not include Pay or Schedule sections. We need to decide mapping: - About the role: could contain the overview paragraph(s) describing the unit, role, opportunity. - Responsibilities: the list after "Participate in customer discussions...". - Requirements: maybe "Required Skill And Experience" plus maybe "Additional Required Qualifications"? But we have separate Qualifications heading. Could split: Requirements = required skill and experience; Qualifications = additional required qualifications (education, relocation, work authorization). Skills = preferred skill and experience. - Benefits: the benefits list. We must not repeat job title as heading. The overview includes "Overview The Infosys Financial Services unit..." We'll put that under

About the role

. We need to preserve all substantive information: include paragraphs, bullet lists. We must remove EEO boilerplate at end. We must not include duplicated lines. Let's extract content. Original text: Overview The Infosys Financial Services unit is a global leader in driving digital transformation for financial institutions. We specialize in leveraging advanced technologies such as AI, cloud, and data-led innovation to help our clients accelerate growth and unlock business value. Our AI-driven solutions empower financial institutions to make smarter decisions, enhance customer experiences, and achieve operational excellence. Join us to be part of a pioneering team that is at the forefront of financial services transformation. You'll have the opportunity to work with cutting-edge AI technologies, collaborate with industry experts, and contribute to transformative projects across banking, wealth management, and insurance sectors. If you're passionate about AI and eager to make a significant impact, the Infosys Financial Services unit is the perfect place for you to grow and excel. In the assigned Job Role of Architecture Consultant 2, your Area Of Responsibility will be as below: Participate in customer discussions to gather and analyze system requirements for performance, security and scalability. Provide suggestions on solution architecture, contribute to tech framework development, support enterprise architecture definition, and drive design creation Identify suitable technologies and tools available in the market, and perform a comparative analysis in line with client's business requirement, thereby identifying optimal architectural solution options Participate in developing integration strategies based on validation of proof of concept of proposed architectural solutions Facilitate a smooth transition by ensuring knowledge transfer and adherence to quality standards, while contributing to the build and deployment automation strategy Collaborate with development teams to resolve complex technical issues using solution deployment and roll out methods, during build, deployment and support phases Analyze system performance basis architectural solutions implemented and support in identifying potential risks in the system landscape Create artifacts of architectural frameworks and technical solutions, thereby enriching team's knowledge repository Your Contribution To The Team The ability to analyse, design, and develop scalable and secure architectures. A knack for assessing multiple technologies, tools and frameworks to recommend optimal solutions. Understanding of integration methodologies, proof-of-concept validation and deployment strategies. The ability to document architectural frameworks and solutions. Proactive communication with internal teams and clients, ensuring alignment with business objectives. A knack to keep with up technical advancements to ensure relevant and effective recommendations. The ability to maintain standards and ensure smooth transition through knowledge transfer Required Skill And Experience Experience in building Java 1.8+, Spring Boot applications with Artificial Intelligence Preferred Skill And Experience Experience in Microservices and Java-based enterprise-level Technology Architecture Additional Required Qualifications Bachelor’s degree or foreign equivalent required from an accredited institution. Will also consider three years of progressive experience in the specialty in lieu of every year of education. This position may require relocation and/or travel to work/project location. Candidates authorized to work for any employer in the United States without employer-based visa sponsorship are welcome to apply. Infosys is unable to provide immigration sponsorship for this role now or in the future. Benefits Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits: Medical/Dental/Vision/Life InsuranceLong-term/Short-term DisabilityHealth and Dependent Care Reimbursement AccountsInsurance (Accident, Critical Illness , Hospital Indemnity, Legal)401(k) plan and contributions dependent on salary levelPaid holidays plus Paid Time Off About Us Infosys is a global leader in next-generation digital services and consulting. We enable clients in more than 50 countries to navigate their digital transformation. With over four decades of experience in managing the systems and workings of global enterprises, we expertly steer our clients through their digital journey. We do it by enabling the enterprise with an AI-powered core that helps prioritize the execution of change. We also empower the business with agile digital at scale to deliver unprecedented levels of performance and customer delight. Our always-on learning agenda drives their continuous improvement through building and transferring digital skills, expertise, and ideas from our innovation ecosystem. EEO Infosys provides equal employment opportunities to applicants and employees without regard to race; color; sex; gender identity; sexual orientation; religious practices and observances; national origin; pregnancy, childbirth, or related medical conditions; status as a protected veteran or spouse/family member of a protected veteran; or disability. We need to remove EEO paragraph. Now we need to format. We'll produce:

About the role

... overview paragraph(s) ...

Then

Responsibilities

• ... each responsibility ...

Then

Your Contribution To The Team

maybe we map to Skills? But instruction says use headings like Skills. However "Your Contribution To The Team" is a section; we could use

Skills

for that? But it's not exactly skills; it's contributions. Could also use

About the role

already used. Maybe we should use

Skills

for the contribution list. But we also have Required Skill And Experience and Preferred Skill And Experience. Might be better to follow instruction: Use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. Thus: - About the role: overview. - Responsibilities: responsibilities list. - Requirements: Required Skill And Experience (maybe also include Additional Required Qualifications? but we have Qualifications heading separate). - Qualifications: Additional Required Qualifications (education, relocation, work authorization). - Skills: Preferred Skill And Experience (maybe also include Your Contribution To The Team? but that is more about contributions; could be considered skills as well). However we have both Required Skill and Preferred Skill. Could combine Required under Requirements, Preferred under Skills. The "Your Contribution To The Team" could be considered part of Skills or maybe we could add another section like "About the role" already used. Could we add a heading "Your Contribution To The Team"? Not in list but instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exhaustive. But they say "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be okay to use other headings as long as they are

. However they also say "Prefer a few substantive sections over many thin ones." So maybe we should combine Your Contribution To The Team into Skills or Requirements. I'd put it under Skills as it's about abilities. Thus: Skills: combine "Your Contribution To The Team" and "Preferred Skill And Experience". But we need to preserve all info; we can list them as bullet points under Skills. But we also have Required Skill And Experience separate; we can put under Requirements. Qualifications: Additional Required Qualifications. Benefits: Benefits list. We must not include Pay or Schedule. Now we need to extract bullet points. Responsibilities list (each sentence separated by period? Actually they are separated by spaces but no punctuation. Let's split: - Participate in customer discussions to gather and analyze system requirements for performance, security and scalability. - Provide suggestions on solution architecture, contribute to tech framework development, support enterprise architecture definition, and drive design creation - Identify suitable technologies and tools available in the market, and perform a comparative analysis in line with client's business requirement, thereby identifying optimal architectural solution options - Participate in developing integration strategies based on validation of proof of concept of proposed architectural solutions - Facilitate a smooth transition by ensuring knowledge transfer and adherence to quality standards, while contributing to the build and deployment automation strategy - Collaborate with development teams to resolve complex technical issues using solution deployment and roll out methods, during build, deployment and support phases - Analyze system performance basis architectural solutions implemented and support in identifying potential risks in the system landscape - Create artifacts of architectural frameworks and technical solutions, thereby enriching team's knowledge repository We'll keep as is. Your Contribution To The Team list: - The ability to analyse, design, and develop scalable and secure architectures. - A knack for assessing multiple technologies, tools and frameworks to recommend optimal solutions. - Understanding of integration methodologies, proof-of-concept validation and deployment strategies. - The ability to document architectural frameworks and solutions. - Proactive communication with internal teams and clients, ensuring alignment with business objectives. - A knack to keep with up technical advancements to ensure relevant and effective recommendations. - The ability to maintain standards and ensure smooth transition through knowledge transfer Preferred Skill And Experience: - Experience in Microservices and Java-based enterprise-level Technology Architecture Required Skill And Experience: - Experience in building Java 1.8+, Spring Boot applications with Artificial Intelligence Additional Required Qualifications: - Bachelor’s degree or foreign equivalent required from an accredited institution. - Will also consider three years of progressive experience in the specialty in lieu of every year of education. - This position may require relocation and/or travel to work/project location. - Candidates authorized to work for any employer in the United States without employer-based visa sponsorship are welcome to apply. - Infosys is unable to provide immigration sponsorship for this role now or in the future. Benefits list: The benefits string is a bit jumbled: "Medical/Dental/Vision/Life InsuranceLong-term/Short-term DisabilityHealth and Dependent Care Reimbursement AccountsInsurance (Accident, Critical Illness , Hospital Indemnity, Legal)401(k) plan and contributions