Principal Architect

We need to produce HTML fragment with sections: About the role? The posting includes Overview, then "In the assigned Job Role of Engineering Principal, your Area Of Responsibility will be as below:" then list of responsibilities. Then "Your Contribution To The Team" list of contributions. Then "Required Skill And Experience" list. Then "Preferred Skill And Experience" list. Then "Additional Required Qualifications". Then "Benefits". Then "About Us". Then EEO (should be removed). Also need to remove boilerplate like EEO, application instructions, etc. We need headings: Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content to appropriate headings. We have Overview (maybe "About the role"?). The overview describes the unit and role. Could be "About the role". We'll put that as

About the role

then

with overview text. Responsibilities: list of bullet points after "In the assigned Job Role...". We'll put

Responsibilities

then

• each. Your Contribution To The Team: maybe "Skills" or "Qualifications"? Actually contributions are like what you bring. Could be "Skills" or "Qualifications". The instruction says use headings like Skills, Benefits, Pay, Schedule, Requirements, Qualifications. We have Required Skill And Experience (skills), Preferred Skill And Experience (maybe also skills), Additional Required Qualifications (qualifications). We'll map: - Required Skill And Experience ->

  Skills

  (or Requirements?). Since they are required skills, could be Skills. We'll use Skills. - Preferred Skill And Experience -> maybe also Skills but we could combine? But instruction: prefer few substantive sections over many thin ones. Could combine required and preferred into Skills section with subheadings? But we must not invent headings not allowed? We can still have

  Skills

  and include both required and preferred as lists, maybe separate
  with headings inside? But we cannot add extra headings besides allowed ones? Not explicitly forbidden, but we should follow allowed headings. Could add inside

  but better to keep simple: maybe two sections: Required Skills and Preferred Skills? But those aren't in allowed list. However we could treat Required Skill And Experience as "Skills" and Preferred Skill And Experience as also "Skills" but we could merge them into one list? Might lose distinction but still preserve info. Could include both as separate

  with preceding

  indicating required vs preferred. That's okay. Additional Required Qualifications ->

  Qualifications

  . Benefits ->

  Benefits

  . About Us -> maybe "About the role"? Already used. Could be "About the company"? Not in allowed headings. Could omit? But we should preserve substantive information. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About Us". However we could treat About Us as part of About the role? Might be okay to include as a paragraph under About the role. Or we could create a section with heading not in list? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says use

  for section headings (e.g. ...). Likely we should stick to those headings. So we should not create a heading like "About Us". We can incorporate that info into About the role paragraph. Pay and Schedule: not present, so we omit those sections. Requirements: we have not a separate requirements section besides skills and qualifications. Could treat Required Skill And Experience as Requirements? But we already used Skills. Could also have Requirements heading for required skill and experience. But we need to decide. We have Required Skill And Experience (list). Preferred Skill And Experience (list). Additional Required Qualifications (list). Could map: - Requirements: Required Skill And Experience (maybe also include Additional Required Qualifications? but that's qualifications). We'll do:

  Requirements

  for Required Skill And Experience.

  Qualifications

  for Additional Required Qualifications. Skills: maybe Preferred Skill And Experience? Or we could combine required and preferred under Skills. But we already used Requirements for required. Let's think. Better: Use Requirements for required skill and experience. Use Skills for preferred skill and experience. Use Qualifications for additional required qualifications. Thus:

  Requirements

  list of required skill and experience.

  Skills

  list of preferred skill and experience.

  Qualifications

  Additional Required Qualifications text (Bachelor’s degree... relocation... etc). Could also include bullet? It's prose. Benefits:

  Benefits

  list. About the role:

  About the role

  overview + About Us combined. We must not repeat job title as heading. Good. We must remove EEO, boilerplate, application instructions, etc. We need to preserve all substantive information: overview text, responsibilities list, contribution list, required skill list, preferred skill list, additional qualifications, benefits, about us. Let's extract content. Overview paragraph: "The Infosys Retail, Consumer Goods, and Logistics unit stands as a globally respected partner of choice, dedicated to helping clients achieve their business goals through cutting-edge technology and seamless services. Our unit offers a dynamic forum where projects and teams can effectively learn, adopt, and excel in all technologies. We foster a vibrant community that leverages shared skills and experiences to deliver high-quality, value-enhanced solutions. Join us and become part of a team that drives innovation, operational efficiency, and sustainable growth in the retail, consumer goods, and logistics sector. Together, we can shape the future of these industries and achieve remarkable success." Then after that: "In the assigned Job Role of Engineering Principal, your Area Of Responsibility will be as below:" then list: - Collaborate with stakeholders to align requirements with current and future market needs, while analysing trends and emerging technologies - Guide on design principles to ensure feasibility, cost-effectiveness, and technical accuracy and lead conceptualization and development of innovative solutions aligned with industry advancements - Guide the creation and validation of solution specifications, ensuring alignment with business goals and recommended optimizations - Oversee prototyping and testing to ensure high-quality, functional prototypes that meet engineering standards - Direct technical integration, ensuring systems meet functional and performance criteria - Lead performance optimization initiatives, setting benchmarks and recommending improvements based on system analysis Then "Your Contribution To The Team" then list: - A strategic vision for aligning technical solutions with evolving business goals and industry trends - Expertise in guiding cost-effective, technically sound, and innovative design solutions - Strong client and stakeholder management skills to bridge technical and business needs. - A collaborative mindset to drive innovation and ensure project success. - Ability to lead design conceptualization and implementation based on market insights Then "Required Skill And Experience" then list (many items). Let's copy exactly: Contact Center & Customer Experience Transformation, AI-CC (AI Contact Center), AI-CX (AI Customer Experience), CCaaS Platforms (Amazon Connect, Genesys Cloud CX, NICE CXone, Five9), Conversational AI, Generative AI, Agentic AI, Voicebots, Chatbots, NLP, NLU, Omnichannel CX, CRM Platforms (Salesforce, Dynamics 365, ServiceNow, Pega), API & Middleware Integrations, Cloud Architecture (AWS, Azure, GCP), Customer Journey Transformation, Solution Architecture, Enterprise Consulting, Executive Stakeholder Management, Large-scale CX Modernization Programs, Global Delivery Leadership, Pre-sales & Advisory. Note: It's a comma-separated list. We need to turn into

  • each item. Should we split by commas? The items are separated by commas, but some contain commas inside parentheses. Safer to treat each comma-separated segment as an item, but that may split incorrectly inside parentheses. However the list seems to be discrete items separated by commas, and internal commas only appear within parentheses (e.g., "Amazon Connect, Genesys Cloud CX, NICE CXone, Five9)" which is a list itself). Splitting by commas would break that. Better to keep as one item? But the original is a list of skills; they'd likely expect each skill as separate bullet. Could treat each major area before a comma that is not inside parentheses as separate. That's complex. Simplify: we can keep the whole string as one
  • but that loses granularity. However instruction: preserve ALL substantive information; do not invent or summarize away detail. If we keep as one bullet, we still preserve the info (the whole string). It's not summarizing; it's just grouping. That's acceptable. Similarly for Preferred Skill And Experience list. Preferred list: "Amazon Bedrock, Amazon Lex, Google Dialogflow/CCAI, Kore.ai, Azure OpenAI, Microsoft Copilot, RAG-based Knowledge Solutions, Real-time Speech Analytics, Voice Intelligence, Contact Center Analytics, Workforce Engagement Management (WEM), AI Observability, Customer Intent Mining, Process Automation, Data & Analytics, Healthcare Domain, Banking & Financial Services Domain, Insurance Domain, Telecommunications Domain, Public Sector/State Government Experience, AWS Solution Architect Certification, Amazon Connect Certification, Genesys Cloud CX Certification, NICE CXone Certification, PMP/SAFe/CBAP Certifications, Business Development, GTM Strategy, Thought Leadership, Practice Building, Multi-million Dollar Transformation Engagements." Again comma-separated with internal commas in some items (e.g., "Workforce Engagement Management (WEM)" no internal comma). "Public Sector/State Government Experience" no internal comma. "PMP/SAFe/CBAP Certifications" includes slashes but not commas. So splitting by commas is safe except for "Amazon Bedrock, Amazon Lex, Google Dialogflow/CCAI, Kore.ai, Azure OpenAI, Microsoft Copilot, RAG-based Knowledge Solutions, Real-time Speech Analytics, Voice Intelligence, Contact Center Analytics, Workforce Engagement Management (WEM), AI Observability, Customer Intent Mining, Process Automation, Data & Analytics, Healthcare Domain, Banking & Financial Services Domain, Insurance Domain, Telecommunications Domain, Public Sector/State Government Experience, AWS Solution Architect Certification, Amazon Connect Certification, Genesys Cloud CX Certification, NICE CXone Certification, PMP/SAFe/CBAP Certifications, Business Development, GTM Strategy, Thought Leadership, Practice Building, Multi-million Dollar Transformation Engagements." No internal commas besides separating items. So we can split. For Required list, there are internal commas inside parentheses for CCaaS Platforms (Amazon Connect, Genesys Cloud CX, NICE CXone, Five9) and CRM Platforms (Salesforce, Dynamics 365, ServiceNow, Pega) and Cloud Architecture (AWS, Azure, GCP). Those internal commas would cause over-splitting. To avoid, we could keep required list as one bullet or we could manually keep those groups as single items by not splitting on commas inside parentheses. That's more work. Given the instruction to preserve all substantive information, grouping them as one bullet still preserves the info (the whole string). It's not losing detail; it's just presenting as a single bullet containing all items. That's acceptable. Thus we will produce:

    About the role

    Overview + About Us combined.

    We need to include About Us paragraph: "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