Principal Architect

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. We must not repeat job title. Remove boilerplate etc. We need to parse the posting. Content: - Intro paragraph about OpenText: "Opentext - The Information Company OpenText is a global leader...". That's about the company, could be "About the role"? Actually "About the role" is typical heading for description of role. The intro is about company and mission. Could be placed under "About the role" or maybe not needed. But we need to include substantive info. The posting includes sections: "YOUR IMPACT", "What The Role Offers", "What You Need To Succeed", "ONE LAST THING", compensation details, benefits mention. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content fits each. - About the role: could include the introductory paragraph about OpenText and the role impact: "As a Principal Architect within OpenText Professional Services, you will play a pivotal role..." plus maybe "YOUR IMPACT". So we can put that under About the role. - Responsibilities: from "What The Role Offers": bullet list of duties: lead architecture, design, delivery; partner with customers; provide technical leadership; collaborate; drive cloud/on-prem deployments; support pre-sales; mentor junior consultants. Those are responsibilities. - Requirements: from "What You Need To Succeed": list of experience, expertise, etc. Those are requirements. - Qualifications: maybe overlapping with requirements; but we could separate: Qualifications could be education/experience? However we have only one set. Could combine Requirements and Qualifications? But we need to follow instruction: include a section ONLY when posting has real specific content for it. We have content for Requirements (experience, skills). We could also have Qualifications (maybe certifications? none). Better to put the experience/skills under Requirements and maybe Qualifications could be empty -> omit. - Skills: could list specific technical skills: Java, XML, SQL, PL/SQL, REST services, Kubernetes, ETL tools, etc. Those are skills. We could extract from Requirements. - Benefits: posting mentions benefits package, link to Why Join Us page, variable/commission compensation, vacation, PTO, bonus/commissions eligibility. So we have benefits content. - Pay: Salary range $143,400 - $215,000; plus note about variable, commission, California residents note. So we have pay. - Schedule: not mentioned. No schedule info. So omit Schedule. We must not include placeholder like "commensurate with experience". The posting includes "actual salary may vary and be higher or lower than the range posted." That's specific enough? It's not placeholder; it's a statement. We can include. We must not include boilerplate like EEO, accommodation, AI usage disclosure. Remove those. We must not include duplicated lines. We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to ensure we don't lose any details. Let's extract details precisely. Intro paragraph: "Opentext - The Information Company OpenText is a global leader in information management, where innovation, creativity, and collaboration are the key components of our corporate culture. As a member of our team, you will have the opportunity to partner with the most highly regarded companies in the world, tackle complex issues, and contribute to projects that shape the future of digital transformation. AI-First. Future-Driven. Human-Centered. At OpenText, AI is at the heart of everything we do—powering innovation, transforming work, and empowering digital knowledge workers. We are hiring talent AI can't replace to help us shape the future of information management. Join us." That's a bit fluffy but it's substantive. We'll keep. YOUR IMPACT: "As a Principal Architect within OpenText Professional Services, you will play a pivotal role in helping enterprise customers maximize the value of their information through OpenText Information Archive and enterprise data archiving solutions. Working with some of our largest and most strategic customers, you will provide technical leadership, guide complex archiving and application decommissioning initiatives, and influence solution architecture from pre-sales through delivery. This is an opportunity to leverage your expertise in OpenText Information Archive, cloud technologies, and data transformation while partnering with customers to solve critical business challenges and achieve long-term success." What The Role Offers: list: - Lead the architecture, design, and successful delivery of OpenText Information Archive solutions and complex enterprise data archiving engagements. - Partner with customers to gather business and technical requirements, translating them into scalable archiving, retention, and application decommissioning strategies. - Provide technical leadership across OpenText Information Archive implementations, including system sizing, architecture planning, data discovery, ETL processes, and archival solution design. - Collaborate closely with Account Executives, Solution Consultants, Strategic Partners, and Professional Services teams throughout the sales and delivery lifecycle. - Drive cloud-based and on-premises deployments, including Kubernetes-based environments, ensuring high-quality project execution and customer success. - Support pre-sales activities by contributing to solution scoping, project estimates, proof-of-concepts, demonstrations, and RFP responses. - Mentor and develop junior consultants while promoting delivery excellence, best practices, and deep expertise in OpenText Information Archive and enterprise information management solutions. What You Need To Succeed: - 12+ years of experience in Information Technology, with at least 8+ years focused on enterprise archiving solutions such as OpenText Information Archive, Solix, Informatica, IBM Optim, or similar platforms. - Proven experience architecting and implementing medium-to-large-scale archiving, application decommissioning, and data retention solutions. - Strong expertise in ETL processes and tools, along with hands-on experience with Java, XML, SQL, PL/SQL, REST services, and related technologies. - Solid understanding of enterprise software deployments across both cloud and on-premises environments, including Kubernetes-based infrastructure. - Demonstrated ability to lead technical discussions, develop solution roadmaps, and communicate effectively with technical, business, and executive stakeholders. - Strong analytical, troubleshooting, and problem-solving skills with the ability to deliver innovative customer-focused solutions. - Experience supporting pre-sales engagements, technical demonstrations, proof-of-concepts, and customer workshops. - Collaborative team player who can work independently, build strong customer relationships, and contribute to a culture of excellence and continuous improvement. ONE LAST THING: paragraph about OpenText being more than a tech company, etc. Could be considered additional info about role/culture. Could be placed under About the role or maybe a separate section like "About the company". But we only have allowed headings. Could incorporate into About the role. Compensation/Benefits: - "Compensation: At OpenText, we offer a thoughtfully designed benefits package that supports your physical, emotional, and financial wellbeing. A summary of those benefits can be found on our Why Join Us page. As you move through the hiring process, we’re happy to provide more details about our compensation programs, including variable and commission compensation opportunities for eligible roles, vacation entitlement, and paid time off. Salary Range: $143,400 - $215,000; Depending on the candidate’s education, experience, skills, geographical location, and alignment with internal equity and external market, actual salary may vary and be higher or lower than the range posted. California Residents: The pay range above is a reasonable estimate of salary based on pay scale, candidate experience, skills, and education. In addition to the comprehensive benefits noted above, the role may be eligible for bonus or commissions." - AI Usage Disclosure etc to remove. We need to separate Benefits and Pay sections. Benefits: mention benefits package, link to Why Join Us page, variable/commission compensation opportunities, vacation entitlement, paid time off, bonus/commissions eligibility. Pay: Salary range, note about variation, California residents note. We must not include placeholder like "not specified". We have specifics. Now produce HTML. Structure:

  About the role

  Intro paragraph + YOUR IMPACT combined? Could be two paragraphs.

  Responsibilities

  • ... each bullet

  Requirements

  • ... each bullet

  Skills

  • ... maybe list specific technical skills: Java, XML, SQL, PL/SQL, REST services, ETL tools, Kubernetes, etc.
  But we already listed many skills in Requirements. Could separate: Requirements for experience, Skills for technical skills. However we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we split, we need to ensure we don't lose any info. We could keep Requirements as experience and qualifications, and Skills as technical skills. But the Requirements bullets already include technical skills. If we move them to Skills, we would lose them from Requirements unless we duplicate. Duplication is allowed? It says do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. It doesn't forbid duplicating content across sections, but better to avoid redundancy. However we need to follow typical structure: Requirements often include experience and qualifications; Skills often list technical abilities. We could keep Requirements bullets as they are (including experience and technical skills) and omit Skills section if no extra distinct skills beyond those. But we have specific technical skills listed: Java, XML, SQL, PL/SQL, REST services, ETL processes/tools, Kubernetes. Those are already in Requirements bullet: "Strong expertise in ETL processes and tools, along with hands-on experience with Java, XML, SQL, PL/SQL, REST services, and related technologies." and "Solid understanding of enterprise software deployments across both cloud and on-premises environments, including Kubernetes-based infrastructure." So we could keep Requirements as is and not have a separate Skills section. That would preserve all info. Benefits section: we need to capture benefits package details. Pay section: salary range etc. We must not include Schedule. Now craft HTML. We need to ensure we don't include any boilerplate like EEO, accommodation, AI usage. Let's write. About the role: combine intro paragraph and YOUR IMPACT. Intro paragraph: "Opentext - The Information Company OpenText is a global leader in information management, where innovation, creativity, and collaboration are the key components of our corporate culture. As a member of our team, you will have the opportunity to partner with the most highly regarded companies in the world, tackle complex issues, and contribute to projects that shape the future of digital transformation. AI-First. Future-Driven. Human-Centered. At OpenText, AI is at the heart of everything we do—powering innovation, transforming work, and empowering digital knowledge workers. We are hiring talent AI can't replace to help us shape the future of information management. Join us." YOUR IMPACT: "As a Principal Architect within OpenText Professional Services, you will play a pivotal role in helping enterprise customers maximize the value of their information through OpenText Information Archive and enterprise data archiving solutions. Working with some of our largest and most strategic customers, you will provide technical leadership, guide complex archiving and application decommissioning initiatives, and influence solution architecture from pre-sales through delivery. This is an opportunity to leverage your expertise in OpenText Information Archive, cloud technologies, and data transformation while partnering with customers to solve critical business challenges and achieve long-term success." We can put them as two

  elements under the heading. Responsibilities: list each bullet as

• . Requirements: list each bullet as
• . Benefits: we need to capture: "At OpenText, we offer a thoughtfully designed benefits package that supports your physical, emotional, and financial wellbeing. A summary of those benefits can