Strategic QE Consultant

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate: EEO, etc. Also remove navigation, legal, scam warning, duplicated lines, application instructions. We need to preserve all substantive info. Let's parse the posting. Overview: description of unit and role. That's "About the role" maybe. Then "In the assigned Job Role of Process Consultant 3, your Area Of Responsibility will be as below:" then bullet list of responsibilities (lead comprehensive process analysis... etc). So responsibilities section. Then "Your Contribution To The Team" bullet list of expertise (skills). That could be Skills. Then "Required Skill And Experience" bullet list of many experiences. That's Requirements. Then "Preferred Skill And Experience" bullet list of more experiences. Could be additional Requirements or maybe also Skills? But we can combine required and preferred under Requirements? The instruction: Use sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have required skill and experience (requirements). Preferred skill and experience could be also requirements but maybe we treat as Requirements as well (or maybe as Skills). However we have also "Additional Required Qualifications" with Bachelor's degree etc. That's Qualifications. Benefits section present: "Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:" then list. Pay: mention "competitive pay" but not specific numbers. The rule: never create Pay section unless posting actually states them. It says "competitive pay" but no specific numbers. Is that considered stating pay? It's vague. The instruction: 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. "competitive pay" is vague but still states that there is competitive pay. Might be considered stating pay? It's not a specific number or range. It's still a statement about pay. The instruction says "unless the posting actually states them". It does state "competitive pay". That is a statement about pay, albeit not specific. I'd argue we can include Pay section with that statement. However they said prefer few substantive sections over many thin ones. Could we omit Pay because it's not specific? The phrase "competitive pay" is somewhat generic but still a statement. I'd lean to include Pay section with that sentence. Schedule: not mentioned. No schedule info. So omit Schedule. Now we need to format. Sections:

About the role

with paragraph(s) from Overview. Overview text: "The Infosys SURE (Services, Utilities, Resources, Energy) unit is dedicated to empowering businesses within the services, utilities, energy, and resources sectors through strategic digital transformation. We specialize in guiding organizations through the complexities of disruption, enabling them to unlock value and realize sustainable growth. Join us to be part of a pioneering team that leverages advanced AI and digital technologies to drive innovation and operational excellence. You'll have the opportunity to work on transformative projects that shape the future of these critical industries, collaborate with industry experts, and develop resilient strategies that respond to change and seize new opportunities. If you're passionate about AI and eager to make a significant impact, the Infosys SURE unit is the perfect place for you to grow and excel" We can put that as

. Then responsibilities: list items from "Lead comprehensive process analysis initiatives..." etc. Each bullet as

. We need to capture all bullet points. Let's extract them: - Lead comprehensive process analysis initiatives using advanced techniques like process mining, workflow simulation, and efficiency modelling to identify strategic opportunities. - Develop complex data models that provide actionable insights for process enhancement and guiding critical business decisions and influencing long-term planning - Conduct in-depth evaluations of complex IT solutions, leveraging process-centric expertise to assess their effectiveness in streamlining operations and achieving organizational goals - Lead the creation of technical materials, simplifying complex process concepts for diverse audiences, including process practitioners and business stakeholders - Lead advanced research on process tools, analysing long-term product roadmaps and vendor strategies to identify trends and adopt cutting-edge solutions that enhance efficiency and innovation - Design comprehensive architectural models and blueprints for implementing process enhancements and automation solutions that address both immediate and future business needs - Formulate proactive maintenance strategies to ensure system health, scalability, and sustained process performance. Now "Your Contribution To The Team" bullet list: - Expertise in advanced process analysis techniques and methodologies - Proficiency in evaluating IT solutions and aligning them with process enhancement goals - A focus on innovation and adaptability for integrating new technologies - Proactive problem-solving to streamline complex requirements. - Skilled in research, innovation adoption, and designing scalable architectures That could be Skills section. Now "Required Skill And Experience" bullet list (many). Let's capture each: - Experience in quality engineering and testing strategy. - Experience in quality engineering transformation and modernization initiatives. - Experience in AI Engineering/AI/ML Solution Architecture and design. - Experience in test consulting process. - Experience in test automation and continuous testing strategy. - Experience in Agile, DevOps, and CI/CD practices. - Experience in program and portfolio management. - Experience in data warehouse and ETL testing. - Experience in performance engineering and non-functional testing. - Experience in Cloud migration validation. - Experience in Generative AI and Agentic AI adoption. - Experience in AI-enabled quality engineering solutions. - Experience in enterprise quality roadmaps and transformation strategy development. - Experience in governance frameworks, KPIs, SLAs, and reporting dashboards. - Experience in application modernization and digital transformation programs. - Experience in risk management and delivery governance. - Experience in executive stakeholder management. - Experience in business consulting and digital transformation. - Experience in enterprise automation framework strategy and implementation. - Experience in cross-functional leadership across onsite and offshore teams. - Experience in proposal support, solutioning, estimations, and RFP responses. Now "Preferred Skill And Experience" bullet list: - Experience in AI-driven test generation and quality analytics. - Experience in defect prediction and root cause analysis solutions. - Experience in test data management modernization. - Experience in quality engineering accelerators and reusable frameworks. - Experience in enterprise cloud transformation programs. - Experience in AI observability and engineering governance. - Experience in business process transformation initiatives. - Experience in consulting-led account growth and transformation programs. - Experience in executive workshops and steering committee management. - Experience in innovation strategy and technology advisory. Now "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. We need to include Qualifications section with these points. Now Benefits section: - Medical/Dental/Vision/Life Insurance - Long-term/Short-term Disability - Health and Dependent Care Reimbursement Accounts - Insurance (Accident, Critical Illness , Hospital Indemnity, Legal) - 401(k) plan and contributions dependent on salary level - Paid holidays plus Paid Time Off Also "Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:" So we can have a paragraph before list: "Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:" then

. Pay section: we could have a paragraph: "Competitive pay." But we already mentioned competitive pay in benefits intro. Maybe better to have Pay section with just "Competitive pay." However that might be redundant. But we need to follow instruction: include Pay section only if posting actually states them. It does state competitive pay. So we can have Pay section with a short paragraph: "Competitive pay." But we already used "competitive pay" in benefits intro. Could we avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the phrase "competitive pay". If we put it in Pay section, we should not also repeat it in benefits intro. But the benefits intro includes that phrase as part of sentence. We could rephrase benefits intro to not include "competitive pay"? But we must preserve all substantive information; we can't remove that phrase. However we could keep the sentence as is, and also have Pay section repeating it? That would duplicate info, which is not allowed? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not explicitly forbidden but likely undesirable. Better to keep the sentence in Benefits section and not have a separate Pay section, because the Pay info is already there. However the rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does not say we must create a Pay section if pay is mentioned elsewhere. We could choose to not create a Pay section if the pay info is already within Benefits section. But the instruction also says: Prefer a few substantive sections over many thin ones. So we can omit Pay section and keep the competitive pay mention inside Benefits paragraph. Thus we will have Benefits section with a paragraph that includes the competitive pay phrase, then list. Now Schedule: not present, omit. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

About the role

...

Responsibilities

• ...
...

Skills

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Benefits

Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits:

• Medical/Dental/Vision/Life Insurance
• Long-term/Short-term Disability
• Health and Dependent Care Reimbursement Accounts
• Insurance (Accident, Critical Illness , Hospital Indemnity, Legal)
• 401(k) plan and contributions dependent on salary level
• Paid holidays plus Paid Time Off
Check for any duplicated lines: Ensure we didn't include EEO etc. We removed "About Us" and "EEO". Also removed "Infosys is a global leader..." etc. That's boilerplate? It's about company but not required? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" might be considered boilerplate? It's not explicitly listed but could be considered company description not required. However it's substantive? It's generic. Might be considered boilerplate. Safer to remove it. The instruction says remove boilerplate, but not explicitly "About Us". However it's likely considered boilerplate. We'll remove it. Thus we keep only the sections we identified. Now ensure we didn't miss any substantive content: The overview about SURE unit and role is kept. The responsibilities, contribution, required skill, preferred skill, qualifications, benefits. We didn't include "Preferred Skill And Experience" as separate section; we could merge into Requirements or Skills. But we have Requirements section for required skill and experience. Preferred could be considered additional requirements but not mandatory. Could we add a separate section for "Preferred Qualifications"? Not in allowed headings. Could we put them under Requirements as well? Might be okay to include them in Requirements list, but we should differentiate? The instruction: Use sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Preferred skill and experience could be considered part of Requirements (maybe as "Preferred Requirements")