Teamcenter Integration Architect

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. The posting includes: Job Title, location, type, experience, must have technical/functional skills, roles & responsibilities, generic managerial skills, key words. No explicit Benefits, Pay, Schedule. So we should not include those sections. We need sections: About the role (maybe from job description?), Responsibilities, Requirements, Qualifications, Skills. The posting includes "Experience: 4 - 8 years" and "Must Have Technical/Functional Skills". That could be Requirements. Also "Roles & Responsibilities". Also "Generic Managerial Skills, If Any". Also "Key Words to search in Resume". Could be Skills. Also maybe "About the role" could be a brief summary: maybe combine job description? The posting includes "Job Description Experience: 4 - 8 years Must Have Technical/Functional Skills ..." Not a separate about. Could create About the role from the first paragraph: "Teamcenter Integration Architect" remote full-time. But we must not repeat job title as heading. We can include a short

about role: remote full-time, 4-8 years experience, etc. However we must preserve all substantive information. Let's parse content: - Job Title: Teamcenter Integration Architect (not to be repeated) - Job Location: Remote - Job Type: Full-Time - Experience: 4 - 8 years - Must Have Technical/Functional Skills: - Strong experience as a Teamcenter Integration Architect / Technical Integration Lead in large-scale PLM transformation programs. - Hands-on experience in Siemens Teamcenter integration architecture, especially integrations between Teamcenter and enterprise applications such as ERP, MES, CAD/ECAD, reporting, data warehouse, supplier/customer portals, and downstream engineering systems. - Strong working knowledge of Teamcenter integration frameworks and tools, including T4EA, T4S, T4O, Teamcenter Gateway, PLM XML, ITK, SOA, REST, SOAP, Webservices, and event-based integrations. - Experience with ERP integrations, preferably with Oracle EBS / Oracle ERP / SAP, including part, BOM, supplier, manufacturer part, change, and document data flows. - Experience with CAD / ECAD integrations, preferably Creo / IPEM, Cadence, Mentor / Xpedition, and related check-in / check-out, metadata, and file synchronization patterns. - Ability to define interface design specifications, integration mapping documents, API designs, error handling, retry logic, reconciliation rules, monitoring, and exception handling. - Roles & Responsibilities: - Experience with Teamcenter 2506.x or higher is preferred. - Work closely with client business, client IT, product vendor, TCS onsite, and offshore teams to understand integration requirements and convert them into scalable technical designs. - Own and drive the integration strategy across Teamcenter, ERP, MES, CAD/ECAD, reporting platforms, data warehouse, supplier/customer portals, and other upstream/downstream enterprise applications. - Review and validate integration inputs from blueprint/design teams and translate approved design artifacts into implementation-ready interface specifications. - Define integration patterns for real-time, batch, event-driven, scheduler-based, API-based, and middleware-based integrations - Support coexistence architecture between legacy PLM and Teamcenter during phased rollout, ensuring clear ownership of data objects, synchronization rules, exception handling, and cutover readiness. - Coordinate with middleware and boundary application teams to ensure interface dependencies, connectivity, data ownership, and test readiness are clearly defined - Review integration code/configuration for quality, maintainability, scalability, performance, and alignment with approved architecture - Generic Managerial Skills, If Any: - Good verbal and written communication skills. - Strong onsite customer-facing consulting and stakeholder management capability - Ability to work in a multi-vendor, multi-geography program environment - Good documentation and presentation skill s - Key Words to search in Resume: Teamcenter. T4EA,T4S,T4O We need to decide sections: About the role (maybe a brief summary: remote full-time, 4-8 years experience). Could be a

under About the role. Responsibilities: list from Roles & Responsibilities. Requirements: maybe the Must Have Technical/Functional Skills plus Experience 4-8 years. Qualifications: maybe Experience with Teamcenter 2506.x or higher is preferred (that's a qualification). Could also include generic managerial skills? But those are skills. Skills: could include Technical skills (the must have) and Generic Managerial Skills. But we must avoid duplication. Let's think: The posting already separates Must Have Technical/Functional Skills (technical requirements) and Generic Managerial Skills (soft skills). Could map: - Requirements: Experience 4-8 years, Must Have Technical/Functional Skills (list) - Qualifications: Experience with Teamcenter 2506.x or higher preferred (maybe also mention preferred) - Skills: Generic Managerial Skills (communication, stakeholder management, multi-vendor, documentation) But also the Must Have Technical/Functional Skills could be considered Skills. However we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need to follow instruction: use headings only when there is real specific content. We can have multiple sections if they have content. Let's propose sections: - About the role: short paragraph summarizing remote full-time, 4-8 years experience, role as Teamcenter Integration Architect. - Responsibilities: list from Roles & Responsibilities. - Requirements: list from Must Have Technical/Functional Skills plus Experience 4-8 years. - Qualifications: note preferred experience with Teamcenter 2506.x or higher. - Skills: list Generic Managerial Skills. We should not include Benefits, Pay, Schedule. Now we need to output HTML fragment: use

for each section heading, then content: either

for prose or

• for lists. We must not repeat job title as heading. So About the role heading is fine. We need to preserve all substantive information: include location, type, experience, etc. Let's embed location and type in About the role paragraph. Let's craft:

  About the role

  This is a full‑time remote position for a Teamcenter Integration Architect requiring 4‑8 years of experience.

  That captures location and type. Now Responsibilities: list each bullet. We need to ensure we include all bullets from Roles & Responsibilities. Let's list them: - Experience with Teamcenter 2506.x or higher is preferred. - Work closely with client business, client IT, product vendor, TCS onsite, and offshore teams to understand integration requirements and convert them into scalable technical designs. - Own and drive the integration strategy across Teamcenter, ERP, MES, CAD/ECAD, reporting platforms, data warehouse, supplier/customer portals, and other upstream/downstream enterprise applications. - Review and validate integration inputs from blueprint/design teams and translate approved design artifacts into implementation-ready interface specifications. - Define integration patterns for real-time, batch, event-driven, scheduler-based, API-based, and middleware-based integrations - Support coexistence architecture between legacy PLM and Teamcenter during phased rollout, ensuring clear ownership of data objects, synchronization rules, exception handling, and cutover readiness. - Coordinate with middleware and boundary application teams to ensure interface dependencies, connectivity, data ownership, and test readiness are clearly defined - Review integration code/configuration for quality, maintainability, scalability, performance, and alignment with approved architecture Note: The bullet "Experience with Teamcenter 2506.x or higher is preferred." could also be qualification but we already have it in responsibilities list; but it's also in Responsibilities section as per posting. We'll keep it there. Now Requirements: Must Have Technical/Functional Skills plus Experience 4-8 years (though we already mentioned experience in About). But we can still include experience as part of Requirements. List: - Strong experience as a Teamcenter Integration Architect / Technical Integration Lead in large-scale PLM transformation programs. - Hands-on experience in Siemens Teamcenter integration architecture, especially integrations between Teamcenter and enterprise applications such as ERP, MES, CAD/ECAD, reporting, data warehouse, supplier/customer portals, and downstream engineering systems. - Strong working knowledge of Teamcenter integration frameworks and tools, including T4EA, T4S, T4O, Teamcenter Gateway, PLM XML, ITK, SOA, REST, SOAP, Webservices, and event-based integrations. - Experience with ERP integrations, preferably with Oracle EBS / Oracle ERP / SAP, including part, BOM, supplier, manufacturer part, change, and document data flows. - Experience with CAD / ECAD integrations, preferably Creo / IPEM, Cadence, Mentor / Xpedition, and related check-in / check-out, metadata, and file synchronization patterns. - Ability to define interface design specifications, integration mapping documents, API designs, error handling, retry logic, reconciliation rules, monitoring, and exception handling. - 4‑8 years of relevant experience. Now Qualifications: maybe "Experience with Teamcenter 2506.x or higher is preferred." but we already used that in Responsibilities. Could also note that it's preferred. But to avoid duplication, maybe we move that to Qualifications and remove from Responsibilities. However the posting says it's under Roles & Responsibilities. But we can still include it there; duplication is okay? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but we should avoid unnecessary repetition? It didn't forbid duplication, but better to keep each piece once. However the posting includes that bullet under Roles & Responsibilities; we could keep it there and not duplicate elsewhere. For Qualifications we could note something else: maybe "Preferred familiarity with latest Teamcenter version" but that's same. Could also note nothing else. If we have no other qualification, we might omit Qualifications section. But we need to decide. We have Responsibilities, Requirements, Skills. Could also have Qualifications empty -> omit. Skills: Generic Managerial Skills: - Good verbal and written communication skills. - Strong onsite customer-facing consulting and stakeholder management capability - Ability to work in a multi-vendor, multi-geography program environment - Good documentation and presentation skill s (typo: skill s but keep as is) Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now produce HTML. Make sure to close tags properly. Let's craft:

  About the role

  This is a full‑time remote position for a Teamcenter Integration Architect requiring 4‑8 years of experience.

  Responsibilities

  • Work closely with client business, client IT, product vendor, TCS onsite, and offshore teams to understand integration requirements and convert them into scalable technical designs.
  • Own and drive the integration strategy across Teamcenter, ERP, MES, CAD/ECAD, reporting platforms, data warehouse, supplier/customer portals, and other upstream/downstream enterprise applications.
  • Review and validate integration inputs from blueprint/design teams and translate approved design artifacts into implementation-ready interface specifications.
  • Define integration patterns for real-time, batch, event-driven, scheduler-based, API-based, and middleware-based integrations.
  • Support coexistence architecture between legacy PLM and Teamcenter during phased rollout, ensuring clear ownership of data objects, synchronization rules, exception handling, and cutover readiness.
  • Coordinate with middleware and boundary application teams to ensure interface dependencies, connectivity, data ownership, and test readiness are clearly defined.
  • Review integration code/configuration for quality, maintainability, scalability, performance, and alignment with approved architecture.

  Requirements

  • Strong experience as a Teamcenter Integration Architect / Technical Integration Lead in