Professional, ERP Architecture
Johnson & Johnson MedTech · West Chester, PA · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: About the role? The posting includes description, responsibilities, qualifications, etc. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions.
We need to include location info? Not a heading; maybe in a paragraph.
We need to include Pay: posting says "The anticipated base pay range for this position is : 132,000.00 USD Annual". So we can include Pay section with that.
Schedule: Not mentioned. No schedule info. So omit.
Benefits: posting includes a long list of benefits under "Additional Description For Pay Transparency". That includes vacation, sick time, holiday pay, etc. So we can include Benefits section with that list.
Qualifications: includes Education, Required Experience and Skills, Preferred Experience, Other Language, Travel, Certifications. We'll put under Qualifications.
Skills: maybe separate? The posting also has "Required Skills Preferred Skills:" list. Could be under Skills section. But we already have Qualifications covering skills. The instruction: Use sections like Skills if there is content. We could combine qualifications and skills? Better to follow headings: About the role (summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: brief overview from description: role will plan, design build, and govern multi-instance SAP application landscape etc. Could be a paragraph.
Responsibilities: list of key responsibilities bullet points.
Requirements: maybe education and required experience? But we have Qualifications for education and experience. Requirements could be "Required Experience and Skills". However we have both Qualifications and Skills sections; we need to avoid duplication. Perhaps Qualifications for education and certifications, Skills for technical skills list. But the posting lumps them together. We'll split: Qualifications: Education, Certifications, Language, Travel. Skills: Required Experience and Skills (including hands-on experience) plus Preferred Skills list.
But we also have "Preferred Experience" etc. Could go under Skills as preferred.
We'll produce:
.
Requirements: mandatory experience: "4+ years of experience in enterprise/ERP architecture, including prior experience leading projects or mentoring team members. Hands on and leadership experience with one or more of the following: SAP ABAP – Strong hands on development experience across SAP ECC and S/4HANA, in RICEFW (Reports, Interfaces, Conversions, Enhancements, Forms and Workflows) SAP Security - Strong hands-on expertise with SAP GRC Access Control, including Access Risk Analysis (ARA), Access Request Management (ARM), Business Role Management (BRM) and Emergency Access Management (EAM/Firefighter). SAP BASIS – Strong hands on experience planning, delivering and administering SAP S/4 HANA, SAP ECC, SAP BTP, across hybrid cloud platform landscapes. SAP Integration BTP and IS - Lead integration development and architecture across SAP S/4HANA, SAP ECC, SuccessFactors, Ariba, EWM, TM, GTS, IBP, Concur, Salesforce and other enterprise platforms. Lead teams and SI partners; provide technical governance, code reviews, estimation, design authority and mentoring. Strong experience with production support, critical incident management, performance tuning, root-cause analysis and release management across 24×7 global SAP environments. Excellent collaboration with SAP functional leads, enterprise architects, business stakeholders, QA/Validation, Infrastructure and global IT leadership."
We could break into bullet points for clarity but it's okay as paragraph. However we should use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions.
We need to include location info? Not a heading; maybe in a paragraph.
We need to include Pay: posting says "The anticipated base pay range for this position is : 132,000.00 USD Annual". So we can include Pay section with that.
Schedule: Not mentioned. No schedule info. So omit.
Benefits: posting includes a long list of benefits under "Additional Description For Pay Transparency". That includes vacation, sick time, holiday pay, etc. So we can include Benefits section with that list.
Qualifications: includes Education, Required Experience and Skills, Preferred Experience, Other Language, Travel, Certifications. We'll put under Qualifications.
Skills: maybe separate? The posting also has "Required Skills Preferred Skills:" list. Could be under Skills section. But we already have Qualifications covering skills. The instruction: Use sections like Skills if there is content. We could combine qualifications and skills? Better to follow headings: About the role (summary), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
About the role: brief overview from description: role will plan, design build, and govern multi-instance SAP application landscape etc. Could be a paragraph.
Responsibilities: list of key responsibilities bullet points.
Requirements: maybe education and required experience? But we have Qualifications for education and experience. Requirements could be "Required Experience and Skills". However we have both Qualifications and Skills sections; we need to avoid duplication. Perhaps Qualifications for education and certifications, Skills for technical skills list. But the posting lumps them together. We'll split: Qualifications: Education, Certifications, Language, Travel. Skills: Required Experience and Skills (including hands-on experience) plus Preferred Skills list.
But we also have "Preferred Experience" etc. Could go under Skills as preferred.
We'll produce:
About the role
...
Responsibilities
- ... ...
Requirements
Maybe not needed if we have Qualifications and Skills. But we could put "Required Experience and Skills" under Requirements. However we also have Skills section for preferred skills. Might be redundant. Better: Use Requirements for mandatory qualifications (education, experience, language, travel, certifications). Use Skills for technical skill sets (SAP Basis, Security, ABAP, BTP/IS integration) and preferred skills list. Let's examine posting: - Education Bachelor’s degree ... required Master’s degree or MBA preferred - Required Experience and Skills 4+ years of experience in enterprise/ERP architecture, including prior experience leading projects or mentoring team members. Hands on and leadership experience with one or more of the following: SAP ABAP..., SAP Security..., SAP BASIS..., SAP Integration BTP and IS... - Lead teams and SI partners... - Strong experience with production support... - Excellent collaboration... - Preferred Experience with global S/4 implementations... - Experience with SAP BTP, Integration Suite, Fiori/UI5 and REST/OData services is highly desirable. - Experience with S/4HANA, Fiori, SAP BTP and Joule/Generative AI enablement - Strong knowledge of API Management... - Experience managing SAP security integration... - Understanding of GxP... - Experience in regulated industries... - Exposure to enterprise security... - Experience managing vendors... - Experience in a separation, spin-off, carve-out, or M&A technology environment - Other Language: English required. - Travel: Up to 20%, primarily domestic with occasional international travel - Certifications: ERP platform certifications (e.g., SAP), TOGAF, or cloud certifications preferred Thus we can put Education, Experience, Language, Travel, Certifications under Requirements (or Qualifications). The instruction says use Qualifications heading for qualifications. So we can put Education, Certifications, Language, Travel under Qualifications. Then Skills heading for technical skill sets (SAP Basis, Security, ABAP, BTP/IS integration) and preferred skills list. But the posting also has "Required Experience and Skills" which includes both experience and skill sets. We'll split: Experience (years, leadership) under Qualifications? Might be better to put under Requirements. However we have no Requirements heading used yet; we can use Requirements for mandatory experience and maybe core skill sets. Then Skills for preferred skills list. Let's decide: - About the role: summary paragraph. - Responsibilities: bullet list of key responsibilities. - Requirements: mandatory experience (4+ years enterprise/ERP architecture, leading projects, hands-on leadership experience with SAP ABAP, Security, BASIS, Integration BTP/IS, production support, collaboration, etc.) plus maybe language and travel? But language and travel could be under Qualifications. Hmm. Given the headings list includes Qualifications and Skills, we should use them as intended: Qualifications for education, certifications, language, travel. Skills for technical skills (both required and preferred). Requirements could be used for mandatory experience (years, leadership). But we have both Qualifications and Skills; we can also have Requirements. Thus:About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
Pay
The anticipated base pay range for this position is 132,000.00 USD Annual.
We must not include Schedule. Now we need to extract precise content. About the role: from description: "This role will plan, design build, and govern the multi-instance SAP application landscape including ECC and S/4 as DePuy Synthes separates from JnJ to become a stand alone organization. We are looking for an SAP platform leader to manage multiple conveyed SAP ECC and S/4 instances supporting Day 1 separation, lead through the TSA transition, and execute on SAP instance consolidation into S/4 supporting TSA exit. This role will be responsible to partner closely with business and IT stakeholders to align ERP/SAP architecture with business processes, enabling operational efficiency, innovation, and growth. The position offers the opportunity to influence enterprise-wide technology direction and contribute to a modern, connected digital ecosystem including AI." We'll put that as paragraph(s). Could be two paragraphs but we can combine. Responsibilities: list from "Key Responsibilities" bullet points: - Manage multiple conveyed SAP ECC and S/4 instances supporting Day 1 separation, lead through the TSA transition period, and execute on SAP instance consolidation into S/4 supporting TSA exit. - Define and contribute to the overall ERP and enterprise application architecture, ensuring alignment with business strategy and enterprise technology standards - Design and integrate ERP systems with other enterprise platforms, ensuring compatibility across multiple systems, technologies, and data environments - Evaluate current systems and recommend improvements or new technology solutions to enhance business performance and efficiency - Collaborate with cross-functional teams to translate business requirements into scalable ERP architecture solutions - Lead and support system integration efforts, ensuring seamless data flow and interoperability across applications and platforms - Ensure ERP solutions meet security, compliance, and performance standards for enterprise systems - Provide technical guidance and architectural direction to project teams and developers - Identify opportunities to leverage emerging technologies to optimize ERP capabilities and enterprise operations - Develop and maintain documentation, standards, and architectural models for ERP systems - Support troubleshooting and resolution of complex system integration and performance issues We'll output each as- for any list of duties/requirements/benefits. So we should split into list items.
Thus Requirements list items:
- 4+ years of experience in enterprise/ERP architecture, including prior experience leading projects or mentoring team members.
- Hands-on and leadership experience with SAP ABAP – Strong hands-on development experience across SAP ECC and S/4HANA, in RICEFW (Reports, Interfaces, Conversions, Enhancements, Forms and Workflows).
- Hands-on and leadership experience with SAP Security – Strong hands-on expertise with SAP GRC Access Control, including Access Risk Analysis (ARA), Access Request Management (ARM), Business Role Management (BRM) and Emergency Access Management (EAM/Firefighter).
- Hands-on and leadership experience with SAP BASIS – Strong hands-on experience planning, delivering and administering SAP S/4 HANA, SAP ECC, SAP BTP, across hybrid cloud platform landscapes.
- Hands-on and leadership experience with SAP Integration BTP and IS – Lead integration development and architecture across SAP S/4HANA, SAP ECC, SuccessFactors, Ariba, EWM, TM, GTS, IBP, Concur, Salesforce and other enterprise platforms; lead teams and SI partners; provide technical governance, code reviews, estimation, design authority and mentoring.
- Strong experience with production support, critical incident management, performance tuning, root-cause analysis and release management across 24×7 global SAP environments.
- Excellent collaboration with SAP functional leads, enterprise architects, business stakeholders, QA/Validation, Infrastructure and global IT leadership.
We could also include "Lead teams and SI partners..." but we already included.
Qualifications: Education, Certifications, Language, Travel.
Education: Bachelor’s degree in Information Technology, Computer Science, Engineering, or related field required; Master’s degree or MBA preferred.
Certifications: ERP platform certifications (e.g., SAP), TOGAF, or cloud certifications preferred.
Language: English required.
Travel: Up to 20%, primarily domestic with occasional international travel.
We'll list as
- ...