PlainID IAM Consultant

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. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Overview: description about Infosys Financial Services unit, etc. That could be "About the role" or maybe "Overview". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to those headings. We have: - Overview: description of unit, role, etc. Could be "About the role". We'll put that under

About the role

with paragraphs. - Then "In the assigned Job Role of Infrastructure Consultant 2, your Area Of Responsibility will be as below:" followed by bullet list of responsibilities. That's responsibilities. - Then "Your Contribution To The Team" bullet list? Actually it's a paragraph with bullet-like statements: "A collaborative spirit and excellent communication skills. Ability to handle complex incidents and implement resolutions A knack for conducting IT infrastructure assessment and identifying key optimization opportunities Focused approach towards deployment management, system optimization, and process automation initiatives including sector specific focus The ability to work with cross-functional teams". This could be part of Requirements or Skills? Might be "Skills". But we also have "Required Skill And Experience" and "Preferred Skill And Experience". Also "Additional Required Qualifications". So we need sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where each piece goes. Let's extract: Responsibilities: list after "In the assigned Job Role of Infrastructure Consultant 2, your Area Of Responsibility will be as below:" includes many bullet points (starting with Collaborate..., Participate..., Contribute..., Align..., Co-ordinate..., Facilitate..., Conduct..., Gather..., Act as liaison..., Develop...). We'll put those as

• . Your Contribution To The Team: seems like desired attributes/skills. Could go under Skills or Requirements. Since we have separate Required Skill And Experience and Preferred Skill And Experience, we could put those under Skills (maybe Required Skills and Preferred Skills). But we also have Qualifications (education). Let's map: - Required Skill And Experience: bullet list: "This resource is required to support existing PlainID services (onboarding, production support, analysis) and help with migration to PlainID SaaS platform Experience supporting onboarding to services, business analysis, testing, production support IAM experience and knowledge specifically policy-based authorization Experience in Testing & Validation and access control models". That's required skills/experience. - Preferred Skill And Experience: list: "Experience in PlainID SaaS Migration, Open Policy Agent (OPA), Cedar, Ping Identity and SailPoint Experience in Access Controls such as ABAC (Attribute-Based Access Control), PBAC (Policy-Based Access Control), RBAC (Role-Based Access Control) Experience in Identity Governance, Enterprise IAM Programs, Authorization Architecture and Identity & Data Integration". That's preferred skills. - 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. 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 now or in the future." That's qualifications (education, experience equivalence, relocation, work authorization). We'll put under Qualifications. - Benefits: paragraph: "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". That's benefits. - Pay: The posting mentions "competitive pay" but no specific numbers. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Along with competitive pay" but no specific pay figure. Is that enough to create a Pay section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "competitive pay" is a statement about pay, but not a specific amount. The instruction also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive pay" is somewhat vague but not exactly placeholder like "commensurate with experience". However it's still not a specific number. The rule might consider that as not specific enough to warrant a Pay section. Safer to omit Pay section because no concrete pay info. Similarly Schedule: not mentioned. So we omit Pay and Schedule. Thus sections: About the role, Responsibilities, Skills (maybe split into Required Skills and Preferred Skills? But we only have one Skills heading allowed. Could combine required and preferred under Skills with subheadings? But we cannot use other headings besides

  . Could we include two

  sections: Required Skills and Preferred Skills? The instruction list includes Skills as a possible heading, not Required Skills. But we could still use

  Skills

  and inside list both required and preferred, maybe separate paragraphs. However we also have Qualifications separate. We also have "Your Contribution To The Team" which could be considered Skills as well. Might combine all skill-related content under Skills. Thus:

  About the role

  : paragraphs from Overview (first paragraph(s) up to "If you're passionate about AI and eager to make a significant impact, the Infosys Financial Services unit is the perfect place for you to grow and excel.") That's the overview. Then

  Responsibilities

  : list of responsibilities. Then

  Skills

  : include "Your Contribution To The Team" (maybe as a paragraph) plus Required Skill And Experience and Preferred Skill And Experience. Could format as
  • for each bullet? The Required Skill And Experience is a paragraph with multiple items separated by spaces. We need to preserve all substantive information; we can break into list items for clarity but must not invent. We could keep as

    preserving original sentences. However instruction: Use

    • for any list of duties/requirements/benefits. So for skills we should use list if it's a list. The Required Skill And Experience is a list of items: support PlainID services, experience supporting onboarding, IAM experience, experience in Testing & Validation and access control models. We can make each as
    • . Similarly Preferred Skill And Experience list items. Your Contribution To The Team: list of attributes: collaborative spirit, excellent communication skills, ability to handle complex incidents, knack for conducting IT infrastructure assessment, focused approach towards deployment management, ability to work with cross-functional teams. Could be list. Thus under Skills we could have multiple
      sections? Might be okay to have one
      with all skill items. But we need to differentiate required vs preferred? Not required but could be okay. Alternatively we could have separate headings: Required Skills and Preferred Skills, but those aren't in the allowed list. However the instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests those are examples, not an exhaustive list? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should stick to those. Thus we will have: - About the role - Responsibilities - Requirements (maybe we could put Required Skill And Experience under Requirements) - Qualifications (education etc.) - Skills (maybe Preferred Skill And Experience + Your Contribution To The Team) - Benefits We need to decide where to put "Your Contribution To The Team". Could be under Requirements (as they are desired attributes). But we already have Required Skill And Experience for requirements. The "Your Contribution To The Team" seems like desired competencies, could be under Requirements as well. However we have a separate Requirements heading allowed. Let's put Required Skill And Experience under Requirements. And put Your Contribution To The Team plus Preferred Skill And Experience under Skills. Thus:

      About the role

      : overview paragraphs.

      Responsibilities

      : list.

      Requirements

      : list of required skill and experience items.

      Qualifications

      : paragraph(s) about degree, experience equivalence, relocation, work authorization, no sponsorship.

      Skills

      : list of your contribution items + preferred skill and experience items.

      Benefits

      : list of benefits. We must not include Pay or Schedule. Now we need to format lists properly. Let's extract exact text. Overview paragraphs: "The Infosys Financial Services unit is a global leader in driving digital transformation for financial institutions. We specialize in leveraging advanced technologies such as AI, cloud, and data-led innovation to help our clients accelerate growth and unlock business value. Our AI-driven solutions empower financial institutions to make smarter decisions, enhance customer experiences, and achieve operational excellence. Join us to be part of a pioneering team that is at the forefront of financial services transformation. You'll have the opportunity to work with cutting-edge AI technologies, collaborate with industry experts, and contribute to transformative projects across banking, wealth management, and insurance sectors. If you're passionate about AI and eager to make a significant impact, the Infosys Financial Services unit is the perfect place for you to grow and excel." We'll put that as

      maybe multiple

      but can be one. Responsibilities list items (as given): - Collaborate with internal and client teams to resolve complex incidents, conduct root cause analyses, and document findings with preventive recommendations - Participate in evaluation of client IT infrastructure, prepare actionable assessment reports, and support due diligence to document infrastructure maturity and improvement opportunities - Contribute to the design of scalable, cost-effective IT infrastructure solutions, review reusable components, and develop technical documentation for deployed systems - Align release schedules and environment readiness, execute deployments as per protocols, perform post-deployment testing, and manage version control to track changes - Co-ordinate maintenance schedules, emergency fixes, and technology upgrades while ensuring uninterrupted integration into existing systems and processes - Facilitate performance data analysis across systems, coordinate insights on system behavior, and support capacity planning to optimize performance - Conduct security checks, recovery drills, and compliance audits, implement security measures, and coordinate continuity plans to maintain adherence to standards - Gather feedback to identify automation opportunities, analyze existing infrastructure processes, and propose enhancements for efficiency gains - Act as liaison with onsite, offshore, and vendor teams to document project requirements, ensuring effective collaboration - Develop a centralized repository of technical and procedural knowledge, leveraging insights from other projects to drive efficiency and retain organizational expertise We'll put each as

      • . Requirements list (Required Skill And Experience): Original text: "This resource is required to support existing PlainID services (onboarding, production support, analysis) and help with migration to PlainID SaaS platform Experience supporting onboarding to services, business analysis, testing, production support IAM experience and knowledge specifically policy-based authorization Experience in Testing & Validation and access control models" We need to split into sensible items. The text seems missing punctuation. Let's parse: - Support existing PlainID services (onboarding, production support, analysis) and help with migration to PlainID SaaS platform - Experience supporting onboarding to services, business analysis, testing, production support - IAM experience and knowledge specifically policy-based authorization - Experience in Testing