Principal Enterprise Applications SAP Basis Consultant
Infosys · United States · 1 mo ago
RemoteRemoteInformation Technology$117k–$150k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also need to not include sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting includes "Estimated annual compensation range for this role will be as follows: In CA, WA, NY, CO, MD, IL, MN, NJ : $116700 to $150000". So Pay section should be included with that detail. Schedule? Not mentioned explicitly; there is mention of travel may be required, but no schedule like full-time, part-time, shift. So we should not create Schedule section.
Benefits: The posting includes benefits list: 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. So Benefits section.
About the role: The first paragraph describes role: "As a Principal Enterprise Applications SAP consultant, you will be a expert contributing to different phases of the consulting lifecycle..." etc. So we can put that in About the role.
Responsibilities: Many bullet points: define problem, propose solution, development, configuration, deployment, guide teams, proposal development, client training, internal capability building, detail project scope, shape value-adding consulting solutions. Also many tasks under Preferred Qualifications? Actually those are more qualifications. But we can separate responsibilities vs qualifications. The posting includes "Basic Qualifications" and "Preferred Qualifications". Also "Additional Required Qualifications" repeats basic qualifications. We need to extract substantive info.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Qualifications" could combine basic and preferred? But we need to follow instruction: Use headings for those categories if content exists. We can have Requirements (basic qualifications), Qualifications (preferred), Skills (maybe technical skills). However we must not create thin sections; prefer few substantive sections. Could combine Requirements and Qualifications into one? But headings are prescribed; we can include only those with real content. Let's see what content we have:
- About the role: yes.
- Responsibilities: we have many duties: define problem, propose solution, development, configuration, deployment, guide teams, proposal development, client training, internal capability building, detail project scope, shape value-adding consulting solutions. Also tasks like lead troubleshooting sessions, provide technical risk assessments, etc. Those could be responsibilities.
- Requirements: Basic Qualifications: Bachelor's degree or equivalent, 3 years experience in lieu of each year of education, at least 11 years IT experience, may require travel/relocation, work authorization, no sponsorship.
- Qualifications: Preferred Qualifications list many items: lead end-to-end SAP ECC to S/4HANA brownfield migration using SUM DMO tools, manage SAP landscape architecture, configure/monitor/administer SAP systems, system sizing, resource planning, capacity management, ensure high availability, oversee system copies, refreshes, kernel upgrades, patch management, performance tuning, manage TMS, monitor logs, manage HANA Cockpit, backup/restore, security setup, ensure alignment with pharma regulatory requirements (GxP, FDA, CSV/CSA), implement SAP security standards, maintain SOPs, validation docs, technical runbooks, migration artifacts, act as primary SAP Basis lead, work with infrastructure/cloud teams, coordinate with functional/ABAP/QA/business teams, provide technical risk assessments, lead troubleshooting sessions, strong knowledge of SAP NetWeaver, Fiori, Gateway, Solution Manager, SAPRouter, SSL, SSO, certificates, Unix/Linux, experience with cloud-hosted SAP landscapes (Azure/AWS/GCP) plus, excellent communication/documentation/client-facing skills, proven expertise with SAP ECC to S/4HANA brownfield migrations, strong experience with SAP HANA DB admin & performance tuning, experience in FDA-regulated pharma/life sciences (highly preferred), SAP Basis/HANA certs preferred, ITIL cert a plus.
- Skills: Could extract technical skills: SAP Basis, SAP HANA, SAP ECC/S/4HANA, SUM DMO, TMS, CTS+, SAP Solution Manager, Fiori, Gateway, SAPRouter, SSL, SSO, certificates, Unix/Linux, cloud (Azure/AWS/GCP), communication, documentation, client-facing, troubleshooting, risk assessment, architecture recommendations, etc. But we might not need separate Skills if we already have Qualifications covering skills. However instruction says we can include Skills section if there is real specific content. We could include Skills summarizing the technical competencies. But we must avoid thin sections; maybe combine Skills into Qualifications? But headings are separate; we could still include Skills if we have enough content. Let's see: we have many specific technical skills listed; we could put them in Skills. However the Preferred Qualifications already includes many of those as bullet points; we could treat them as Qualifications (preferred) and Skills as maybe overlapping. To avoid duplication, maybe we just have Requirements (basic), Qualifications (preferred + skills), and Benefits, Pay, About the role, Responsibilities. That seems reasonable.
We must not repeat job title as heading. Must not include Job ID etc. Must not include boilerplate like EEO statement, etc. Must remove duplicated lines (like Additional Required Qualifications repeats basic qualifications; we should include only once). Also remove immigration sponsorship lines etc? Those are part of Requirements (work authorization). We should keep that info: "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 at this time." That's part of Requirements.
Also note there is a line: "Infosys is unable to provide immigration sponsorship for this role now or in the future." Duplicate; we keep once.
Also there is a paragraph about Infosys company description; that's boilerplate? It's not EEO but could be considered company overview; maybe we can include in About the role? But it's generic; could be considered boilerplate but it's descriptive of the company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description may not be considered boilerplate; but it's not specific to the role. Might be considered filler; but it's substantive about the employer. However we might keep it under About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that description if it's substantive. However it's generic marketing; but it's still info about the company. I'd include it in About the role perhaps after the role description.
But we need to avoid duplication: there is also "Infosys provides equal employment opportunities..." which is EEO boilerplate; must remove.
Also there is "The job entails sitting as well as working at a computer for extended periods of time. Should be able to communicate by telephone, email or face to face. Travel may be required as per the job requirements." That's about work environment; could be part of Responsibilities or Requirements? Might be considered generic; but it's substantive about job demands. Could be included under Responsibilities or maybe a separate section like "Work Environment" but not in prescribed headings. Could fold into Responsibilities as bullet.
We need to output only HTML fragment, no markdown.
Let's structure:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also need to not include sections with filler like "commensurate with experience". Pay and Schedule only if posting actually states them. The posting includes "Estimated annual compensation range for this role will be as follows: In CA, WA, NY, CO, MD, IL, MN, NJ : $116700 to $150000". So Pay section should be included with that detail. Schedule? Not mentioned explicitly; there is mention of travel may be required, but no schedule like full-time, part-time, shift. So we should not create Schedule section.
Benefits: The posting includes benefits list: 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. So Benefits section.
About the role: The first paragraph describes role: "As a Principal Enterprise Applications SAP consultant, you will be a expert contributing to different phases of the consulting lifecycle..." etc. So we can put that in About the role.
Responsibilities: Many bullet points: define problem, propose solution, development, configuration, deployment, guide teams, proposal development, client training, internal capability building, detail project scope, shape value-adding consulting solutions. Also many tasks under Preferred Qualifications? Actually those are more qualifications. But we can separate responsibilities vs qualifications. The posting includes "Basic Qualifications" and "Preferred Qualifications". Also "Additional Required Qualifications" repeats basic qualifications. We need to extract substantive info.
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly also "Qualifications" could combine basic and preferred? But we need to follow instruction: Use headings for those categories if content exists. We can have Requirements (basic qualifications), Qualifications (preferred), Skills (maybe technical skills). However we must not create thin sections; prefer few substantive sections. Could combine Requirements and Qualifications into one? But headings are prescribed; we can include only those with real content. Let's see what content we have:
- About the role: yes.
- Responsibilities: we have many duties: define problem, propose solution, development, configuration, deployment, guide teams, proposal development, client training, internal capability building, detail project scope, shape value-adding consulting solutions. Also tasks like lead troubleshooting sessions, provide technical risk assessments, etc. Those could be responsibilities.
- Requirements: Basic Qualifications: Bachelor's degree or equivalent, 3 years experience in lieu of each year of education, at least 11 years IT experience, may require travel/relocation, work authorization, no sponsorship.
- Qualifications: Preferred Qualifications list many items: lead end-to-end SAP ECC to S/4HANA brownfield migration using SUM DMO tools, manage SAP landscape architecture, configure/monitor/administer SAP systems, system sizing, resource planning, capacity management, ensure high availability, oversee system copies, refreshes, kernel upgrades, patch management, performance tuning, manage TMS, monitor logs, manage HANA Cockpit, backup/restore, security setup, ensure alignment with pharma regulatory requirements (GxP, FDA, CSV/CSA), implement SAP security standards, maintain SOPs, validation docs, technical runbooks, migration artifacts, act as primary SAP Basis lead, work with infrastructure/cloud teams, coordinate with functional/ABAP/QA/business teams, provide technical risk assessments, lead troubleshooting sessions, strong knowledge of SAP NetWeaver, Fiori, Gateway, Solution Manager, SAPRouter, SSL, SSO, certificates, Unix/Linux, experience with cloud-hosted SAP landscapes (Azure/AWS/GCP) plus, excellent communication/documentation/client-facing skills, proven expertise with SAP ECC to S/4HANA brownfield migrations, strong experience with SAP HANA DB admin & performance tuning, experience in FDA-regulated pharma/life sciences (highly preferred), SAP Basis/HANA certs preferred, ITIL cert a plus.
- Skills: Could extract technical skills: SAP Basis, SAP HANA, SAP ECC/S/4HANA, SUM DMO, TMS, CTS+, SAP Solution Manager, Fiori, Gateway, SAPRouter, SSL, SSO, certificates, Unix/Linux, cloud (Azure/AWS/GCP), communication, documentation, client-facing, troubleshooting, risk assessment, architecture recommendations, etc. But we might not need separate Skills if we already have Qualifications covering skills. However instruction says we can include Skills section if there is real specific content. We could include Skills summarizing the technical competencies. But we must avoid thin sections; maybe combine Skills into Qualifications? But headings are separate; we could still include Skills if we have enough content. Let's see: we have many specific technical skills listed; we could put them in Skills. However the Preferred Qualifications already includes many of those as bullet points; we could treat them as Qualifications (preferred) and Skills as maybe overlapping. To avoid duplication, maybe we just have Requirements (basic), Qualifications (preferred + skills), and Benefits, Pay, About the role, Responsibilities. That seems reasonable.
We must not repeat job title as heading. Must not include Job ID etc. Must not include boilerplate like EEO statement, etc. Must remove duplicated lines (like Additional Required Qualifications repeats basic qualifications; we should include only once). Also remove immigration sponsorship lines etc? Those are part of Requirements (work authorization). We should keep that info: "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 at this time." That's part of Requirements.
Also note there is a line: "Infosys is unable to provide immigration sponsorship for this role now or in the future." Duplicate; we keep once.
Also there is a paragraph about Infosys company description; that's boilerplate? It's not EEO but could be considered company overview; maybe we can include in About the role? But it's generic; could be considered boilerplate but it's descriptive of the company. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description may not be considered boilerplate; but it's not specific to the role. Might be considered filler; but it's substantive about the employer. However we might keep it under About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that description if it's substantive. However it's generic marketing; but it's still info about the company. I'd include it in About the role perhaps after the role description.
But we need to avoid duplication: there is also "Infosys provides equal employment opportunities..." which is EEO boilerplate; must remove.
Also there is "The job entails sitting as well as working at a computer for extended periods of time. Should be able to communicate by telephone, email or face to face. Travel may be required as per the job requirements." That's about work environment; could be part of Responsibilities or Requirements? Might be considered generic; but it's substantive about job demands. Could be included under Responsibilities or maybe a separate section like "Work Environment" but not in prescribed headings. Could fold into Responsibilities as bullet.
We need to output only HTML fragment, no markdown.
Let's structure:
About the role
As a Principal Enterprise Applications SAP consultant, you will be an expert contributing to different phases of the consulting lifecycle. You will be intensely involved in business process consulting; you will define the problem, propose and create the solution. You will also play an important role in the development, configuration and deployment of the overall solution. You will guide teams on project processes, deliverables and contribute to the proposal development, client training and internal capability building and help detail the project scope. You will have the opportunity to shape value-adding consulting solutions that enable our clients to meet the changing needs of the global landscape. 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.
Responsibilities
- Define business problems and propose/create solutions.
- Lead development, configuration, and deployment of SAP solutions.
- Guide teams on project processes and deliverables.
- Contribute to proposal development, client training, and internal capability building.
- Detail project scope and shape value‑adding consulting solutions.
- Lead troubleshooting sessions during integration testing, regression testing, and go‑live support.
- Provide technical risk assessments, mitigation plans, and architecture recommendations.
- Coordinate with functional, ABAP, QA, and business teams for cutover and go‑live planning.
- Work closely with infrastructure/cloud teams for system provisioning and scaling.
- Monitor logs, dumps, traces, and resolve complex system issues.
Requirements
- Bachelor’s degree or foreign equivalent from an accredited institution (or three years of progressive experience in the specialty in lieu of each year of education).
- At least 11 years of experience with Information Technology.
- Candidates must be authorized to work for any employer in the United States without employer‑based visa sponsorship; Infosys is unable to provide immigration sponsorship for this role.
- Willingness to travel and/or relocate as required.
Qualifications
- Lead end‑to‑end SAP ECC to S/4HANA brownfield migrations using SUM DMO tools.
- Manage SAP landscape architecture, including HANA installations, upgrades, migrations, and performance optimizations.
- Configure, monitor, and administer SAP systems (ECC, S/4HANA, SAP HANA Database, Solution Manager, Fiori, Gateway, SAP Enterprise Portal, Web Dispatcher, SAP BTP integrations).
- Perform system sizing, resource planning, and capacity management.
- Ensure high system availability, resilience, and reliability across all SAP landscapes.
- Oversee SAP system copies, refreshes, kernel upgrades, and patch management.
- Conduct performance tuning for ABAP, HANA DB, and application servers.
- Manage transport management system (TMS), CTS+, and deployment workflows.
- Monitor logs, dumps, traces, and resolve complex system issues.
- Manage HANA Cockpit, DB configurations, backup/restore, and security setup.
- Ensure alignment with pharmaceutical regulatory requirements (GxP, FDA, CSV/CSA compliance).
- Implement SAP security standards, user administration, and role‑based access control.
- Maintain SOPs, validation documentation, technical runbooks, and migration artifacts.
- Act as the primary SAP Basis lead for the migration program.
- Provide technical risk assessments, mitigation plans, and architecture recommendations.
- Lead troubleshooting sessions during integration testing, regression testing, and