Pega 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. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to parse the posting. Content: Overview: description about Infosys EAIS unit, team, etc. This could be "About the role" maybe? Actually "Overview" is generic description of unit and role. Could be placed under "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - Overview (description of unit, role, opportunities). Could be "About the role". - "In the assigned Job Role of Architecture Consultant 3, your Area Of Responsibility will be as below:" then bullet list of responsibilities (actually sentences). So we can put under Responsibilities. - "Your Contribution To The Team" then bullet list of expertise/abilities. That could be Skills? Or maybe Qualifications? Actually it's more like "Skills" or "Qualifications". The list: Expertise in designing and reviewing solution architectures..., ability to provide architectural insights..., strategic mindset..., proactively drive initiatives..., ability to engage..., passion for mentoring... This seems like required skills/abilities. Could be under Skills. - "Required Skill And Experience" then list of required skills: Certified Pega LSA, Experience with Pega Smart Investigate, Understanding of Pega frameworks, Experience in SQL, Oracle, data modelling and integrations to external systems using REST/SOAP APIs, JMS, MQ, Ability to evaluate solution options..., Implement complex integrations..., Experience working with business analysts, project managers, and clients... This is definitely Requirements or Skills. Could be under Requirements. - "Preferred Skill And Experience": Ability to work in global delivery model. That's a preferred skill. - "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. All applicants authorized to work in the United States are encouraged to apply. That's Qualifications. - "Benefits" section: list of benefits. - Pay: "Along with competitive pay" but no specific amount. The rule: do NOT create Pay section unless posting actually states them. It says "Along with competitive pay" but no specific number. That's vague; we should not create Pay section because it's not specific. 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. Benefits we have specific list, so we can include Benefits. Pay we have only "competitive pay" which is vague; better to omit Pay section. - Schedule: not mentioned, so omit. - About Us: description of Infosys. Could be part of About the role? Might be separate but we have only allowed headings list; we could put under About the role (maybe combine overview and about us). But we must not repeat job title as heading. The "About Us" is generic company description; could be considered part of About the role? Might be okay to include under About the role as additional context. However we need to preserve all substantive info; we can include it in About the role section. - EEO: boilerplate, remove. Thus sections: About the role, Responsibilities, Skills (maybe split into Required Skills and Preferred Skills?), Requirements, Qualifications, Benefits. We need to decide mapping: - About the role: combine Overview and About Us (maybe also "Your Contribution To The Team"? Actually that is more skill/ability). But we could put "Your Contribution To The Team" under Skills. - Responsibilities: the list after "Area Of Responsibility". - Requirements: maybe "Required Skill And Experience". Could be considered Requirements. - Skills: maybe "Your Contribution To The Team" plus "Preferred Skill And Experience". Or we could have Skills section containing both required and preferred skills? But we already have Required Skill And Experience as Requirements. Might be better to have Requirements for required skills, and Skills for preferred skills and contribution abilities. However the instruction says use headings like Skills, Requirements, Qualifications. So we can have: - Requirements: Required Skill And Experience list. - Skills: Your Contribution To The Team list + Preferred Skill And Experience. - Qualifications: Additional Required Qualifications (degree, experience, relocation, work auth). - Benefits: Benefits list. - About the role: Overview + About Us. We must not create Pay or Schedule. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the sentences as is, but we can format as list items. We must not repeat job title as heading. So no heading "Architecture Consultant 3". Good. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: EEO, etc. We must remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. There's none explicit besides maybe "All applicants authorized to work in the United States are encouraged to apply." That's part of Qualifications; we keep it. Now let's extract each piece. Overview paragraph: "Overview The Infosys Enterprise Application Integration Services (EAIS) unit is at the forefront of transforming businesses through innovative consulting services. Our team is equipped with robust methodologies and tools, ensuring faster implementations, smoother rollouts, dependable production support, and top-quality product development. We specialize in integrating business applications using leading technologies such as TIBCO, Vitria, webMethods, IBM WBI, and SAP NetWeaver. Join us to be part of a dynamic team that drives excellence and innovation in enterprise application integration. You'll have the opportunity to work with cutting-edge technologies, collaborate with industry experts, and contribute to impactful projects that shape the future of business operations. If you're passionate about technology and eager to make a difference, the EAIS unit is the perfect place for you to grow and thrive." We can keep as prose under About the role. About Us paragraph: "About Us 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." We can append to About the role. Now Responsibilities: after "In the assigned Job Role of Architecture Consultant 3, your Area Of Responsibility will be as below:" then list: - Create business requirement documents covering functional and non-functional requirements, basis information gathered as part of workshops and interviews with client stakeholders - Review, propose, and develop solution architecture, ensuring application design aligns with the proposed framework and which are scalable, reliable and maintainable - Assess and recommend suitable technologies, tools and platforms for implementation as a part of architectural design, to meet business requirements - Review technical solutions and develop strategies for integration with different technologies and systems, to ensure seamless communication and data flow - Resolve complex technical challenges during build, deployment, and support phases while promoting reusable frameworks and artifacts - Provide specialized insights to development team and build collaborative relationships with clients and internal teams, securing successful execution of projects - Identify potential risks in the system landscape, monitor system performance and suggest optimization initiatives in line with business requirements and long-term objectives - Establish and uphold comprehensive knowledge base to guarantee that vital information is systematically recorded and readily available - Contribute to proposals and RFPs by delivering insights related to architectural solutions, for successfully delivering the proposed solutions We need to preserve each as list items. Now "Your Contribution To The Team" list: - Expertise in designing and reviewing solution architectures that align with business goals. - The ability to provide architectural insights to strengthen solution proposals and ensure successful delivery. - A strategic mindset to align technical solutions with business goals and market trends. - Proactively drive initiatives to ensure smooth execution and transition of projects. - The ability to engage with clients and internal teams to build strong and productive relationships. - Passion for mentoring and fostering a knowledge-sharing culture. Now "Required Skill And Experience" list: - Certified Pega LSA - Experience with Pega Smart Investigate - Understanding of Pega frameworks - Experience in SQL, Oracle, data modelling and integrations to external systems using REST/SOAP APIs, JMS, MQ - Ability to evaluate the solution options and makes recommendations. - Implement complex integrations with external systems - Experience working with business analysts, project managers, and clients to align technical solutions with business goals. Note: some grammar issues but we keep as is. Now "Preferred Skill And Experience": - Ability to work in global delivery model 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. - All applicants authorized to work in the United States are encouraged to apply. Now Benefits: "Benefits Along with competitive pay, as a full-time Infosys employee you are also eligible for the following benefits: Medical/Dental/Vision/Life InsuranceLong-term/Short-term DisabilityHealth and Dependent Care Reimbursement AccountsInsurance (Accident, Critical Illness , Hospital Indemnity, Legal)401(k) plan and contributions dependent on salary levelPaid holidays plus Paid Time Off" We need to parse that into list items. The text seems concatenated without spaces. We need to split logically: - 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 We should keep as list items. Now we need to output HTML. Structure:

  About the role

  Overview text...

  About Us text...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • Your Contribution To The Team items...
  • Preferred Skill And Experience item...
  But we might want to separate "Your Contribution To The Team" as part of Skills; we could also have two sublists? But we can just list all items under Skills. Alternatively we could have Skills for "Your Contribution To The Team" and Preferred Skills separate? But we only have one Skills heading allowed. We'll combine.

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...
  We must not include Pay or Schedule. Now ensure we preserve all substantive information. Let's copy the exact sentences. Overview text: we need to keep as is. Ensure we don't lose any content. Let's copy: "The Infosys Enterprise Application Integration Services (