Identity and Access Management Intermediate

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key info: - Position Title: Identity and Access Management Intermediate (but we must not repeat job title as heading; page already shows it, so we don't output heading for title.) - Department: Information Technology, Department: 450280-IT SYSTEM ADMINISTRATION - Location: Las Cruces - Target Hourly/Salary Rate: $53,165.80; Commensurate with experience. (We should not create Pay section if content is just "commensurate with experience" which is placeholder? 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. Here they state a specific number $53,165.80; plus "Commensurate with experience." That's partially filler but there is a concrete number. Should we include Pay section? The posting states a target hourly/salary rate: $53,165.80; Commensurate with experience. That is a specific number, though also says commensurate with experience. I think we can include Pay section with that number. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state a rate, so we can include Pay. - Appointment Full-time Equivalency: 1.0 - FLSA Status: Exempt - Bargaining Unit Announcement: This is NOT a bargaining unit position with AFSCME. - Contingent Upon Funding: Not Applicable - Standard Work Schedule: Standard (M-F, 8-5) Thus we have Schedule info: Standard (M-F, 8-5). That's specific, we can include Schedule section. - Benefits: Not explicitly mentioned. There's no benefits description. So we should not create Benefits section. - Skills: Not explicitly listed; maybe implied but not explicit. We should not create Skills unless explicit. - Qualifications: There's Required Education and Experience: Associate's Degree + 4 years of relevant experience or a Bachelor's degree + 2 years of relevant experience. Equivalent Qualifications Preferred Qualifications: Special Certification/Licensure (but not detailed). Also Working Conditions and Physical Effort etc. Could be part of Qualifications or Requirements. We need to decide sections: About the role (maybe a summary), Responsibilities (Job Duties and Responsibilities), Requirements (maybe Required Education and Experience), Qualifications (maybe Preferred Qualifications?), Skills (if any), Benefits (none), Pay (yes), Schedule (yes). We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can group them. We must not include boilerplate like EEO, accommodation request, etc. Also remove duplicated lines, cookie/navigation/legal etc. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: - Advertising Summary: "Support and enhance NMSU's Identity and Access Management (IAM) platform by managing systems integrations, monitoring security and compliance, and maintaining accurate identity data. Collaborate with functional users, IT Governance, and technical teams to implement IAM solutions, perform audits, support system upgrades, and ensure secure, reliable access management across the university. Maintain system documentation and stay current with emerging IAM technologies and best practices." That's a good summary for About the role. - Job Duties and Responsibilities: list bullet points: "In partnership with functional users and IT Governance, manage and maintain the NMSU enterprise identity and access management (IAM) platform. Connect and integrate various data sources, such as directories, databases, and applications, into the IAM system to ensure seamless identity management. Develop and maintain mapping rules to align data from different sources with IAM requirements. Monitor IAM platform activity and perform regular audits. Collaborate with other IT team members to design and implement IAM solutions that meet business requirements. Plan and implement upgrades or enhancements to IAM platforms to improve functionality and security. Stay updated with the latest industry trends and technologies to continually improve system reliability and performance. Document system configurations, procedures, and changes to maintain an accurate and comprehensive knowledge base." We can put these as

• items. - Qualifications Required Education and Experience: "Associate's Degree + 4 years of relevant experience or a Bachelor's degree + 2 years of relevant experience." - Equivalent Qualifications Preferred Qualifications: "Special Certification/Licensure" (no specifics). This is vague; maybe we can omit as it's not specific detail. The instruction: never emit a heading followed by filler/placeholder text. "Special Certification/Licensure" is placeholder. So we should not create a section for that if it's just placeholder. Could include under Qualifications as a note? But better to omit if not specific. - Working Conditions and Physical Effort: "Work is normally performed indoors. Physical Effort: Moderate physical activity. Lifting Requirements: Requires handling of average-weight objects up to 25 pounds or standing and/or walking for more than four (4) hours per day. Risk: Work environment involves some exposure to hazards or physical risks, which require following basic safety precautions." That's substantive; could be part of Requirements or a separate section like Working Conditions. But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put working conditions under Requirements or Qualifications. Probably Requirements includes education/experience and maybe working conditions. But we can also add a separate section like "Working Conditions" but not in allowed list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should likely stick to those. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should limit to those headings. So we need to map content to those. Thus: - About the role: Advertising Summary. - Responsibilities: Job Duties and Responsibilities list. - Requirements: Could include Required Education and Experience, plus maybe Working Conditions and Physical Effort (since those are requirements). Could also include "Must be authorized to work in the United States. Visa sponsorship is not available for this position." Also foreign transcript evaluation requirement. Those are requirements. - Qualifications: Could include Preferred Qualifications (Special Certification/Licensure) but it's placeholder; maybe we skip Qualifications if no substantive content. Or we could include "Equivalent Qualifications" but it's vague. Better to omit Qualifications section if no real content. - Skills: Not explicitly listed; maybe we could infer from responsibilities but not explicit. Better to omit. - Benefits: Not mentioned; omit. - Pay: Include the salary rate: $53,165.80; Commensurate with experience. Since we have a specific number, we can include Pay section with that number. The phrase "Commensurate with experience" is filler but we still have a number. We could present as "$53,165.80 (commensurate with experience)". That's okay. - Schedule: Standard Work Schedule: Standard (M-F, 8-5). Include that. Also we have other metadata like Position Title, Department, Location, etc. Should we include those? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short paragraph at top with metadata like Department, Location, etc. Not as headings. Thus output:

  Department: Information Technology – 450280‑IT SYSTEM ADMINISTRATION. Location: Las Cruces, New Mexico, United States. Must be authorized to work in the United States; visa sponsorship not available. Foreign transcript evaluation required if applicable.

  Then sections:

  About the role

  Support and enhance NMSU's Identity and Access Management (IAM) platform by managing systems integrations, monitoring security and compliance, and maintaining accurate identity data. Collaborate with functional users, IT Governance, and technical teams to implement IAM solutions, perform audits, support system upgrades, and ensure secure, reliable access management across the university. Maintain system documentation and stay current with emerging IAM technologies and best practices.

  Responsibilities

  • In partnership with functional users and IT Governance, manage and maintain the NMSU enterprise identity and access management (IAM) platform.
  • Connect and integrate various data sources, such as directories, databases, and applications, into the IAM system to ensure seamless identity management.
  • Develop and maintain mapping rules to align data from different sources with IAM requirements.
  • Monitor IAM platform activity and perform regular audits.
  • Collaborate with other IT team members to design and implement IAM solutions that meet business requirements.
  • Plan and implement upgrades or enhancements to IAM platforms to improve functionality and security.
  • Stay updated with the latest industry trends and technologies to continually improve system reliability and performance.
  • Document system configurations, procedures, and changes to maintain an accurate and comprehensive knowledge base.

  Requirements

  • Associate's Degree + 4 years of relevant experience or a Bachelor's degree + 2 years of relevant experience.
  • Must be authorized to work in the United States; visa sponsorship not available.
  • Foreign transcript evaluation required if using foreign course work to meet credential requirements.
  • Work is normally performed indoors.
  • Physical effort: moderate physical activity.
  • Lifting requirements: handling of average‑weight objects up to 25 lb or standing/walking >4 hours per day.
  • Work environment involves some exposure to hazards or physical risks; basic safety precautions required.

  Pay

  $53,165.80 (commensurate with experience)

  Schedule

  Standard (M‑F, 8‑5)

  We should not include Benefits, Qualifications, Skills sections as they lack substantive content. Check for any duplicated lines: we removed boilerplate. Check that we preserved all substantive info: we included advertising summary, responsibilities list, education/experience, work authorization, foreign transcript eval, working conditions, physical effort, lifting, risk, pay, schedule. Also we included department and location in opening paragraph. Did we include FLSA status, bargaining unit, contingent upon funding, appointment FTE? Those are minor metadata; we could fold them into short p as well. The instruction says fold minor metadata into a short

  or drop it. So we could add them to the opening paragraph. Let's include: Appointment FTE: 1.0, FLSA Status: Exempt, Not a bargaining unit position with AFSCME, Contingent Upon Funding: Not Applicable. We can add them after location. Thus opening paragraph:

  Department: Information Technology – 450280‑IT SYSTEM ADMINISTRATION. Location: Las Cruces, New Mexico, United States. Appointment FTE: 1.0; FLSA Status: Exempt; Not a bargaining unit position (AFSCME). Contingent upon funding: Not applicable. Must be authorized to work in the United States; visa sponsorship not available. Foreign transcript evaluation required if applicable.

  That's concise