Registration Analyst

We need to output HTML fragment with headings for sections that have real content: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove lines like "HID does not accept unsolicited resumes..." etc. Also remove immigration sponsorship note, AI-assisted tech note, etc. Keep substantive info: location, description, who we are, responsibilities list, experience/background list, what we can offer (benefits). Also maybe "Why apply?" could be considered part of benefits or culture but we can include as part of Benefits or maybe as a separate section? The instruction: include a section ONLY when posting has real, specific content for it. So we need to decide which sections have content. We have: - About the role: description of role: "The Registration Analyst is responsible for ensuring that applications for identification certificates are received securely, thoroughly verified, and accurately processed. This role ensures that customer orders are fulfilled correctly and that each customer receives exceptional service throughout the application process." Also "Who are we?" could be about company. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put "About the role" heading with that prose. - Responsibilities: list of duties under "As our Registration Analyst, you’ll support HID’s success by:" then bullet list. So we can create Responsibilities section with

  • items. - Requirements: maybe "Your Experience and Background include:" list. That could be Requirements or Qualifications. The instruction distinguishes Requirements and Qualifications and Skills. We could map "Your Experience and Background include:" to Requirements (or Qualifications). Also there are "Additional experience ... preferred." etc. Those could be Qualifications or Skills. We need to decide. We have: Experience and Background include: - Excellent verbal and written communication skills with a strong customer service background. - Ability to securely handle sensitive and confidential customer data. - Ability to work flexible hours based on business needs. - High school diploma or GED. - Minimum 1–3 years of customer service and/or administrative office experience. - Proficiency in English (written and verbal). - Proficiency with Microsoft Office (Word, Excel, PowerPoint) and Windows operating systems. - Ability to type a minimum of 50 words per minute. Then "Additional experience in verification, authentication, or identity‑related processes is preferred." "Experience handling sensitive documents or regulated customer data is preferred." "Familiarity with certificate authorities, digital identity concepts, or compliance requirements is preferred." "Experience working in high‑volume processing or productivity‑driven environments is preferred." These could be Qualifications or Skills. We could treat the first block as Requirements (mandatory) and the second as Preferred Qualifications (maybe Qualifications). Or we could combine into Requirements and Qualifications sections. We also have "What we can offer you:" list: Competitive salary and rewards package, Competitive benefits and annual leave offering, allowing for work-life balance, A vibrant, welcoming & inclusive culture, Extensive career development opportunities and resources to maximize your potential, To be a part of a global organization that is pioneering the hardware, software and services that allow people to confidently navigate the physical and digital worlds. That's benefits. Also "Why apply?" includes Empowerment, Innovation, Integrity bullet points. That could be considered part of Benefits or culture. But we could include as part of Benefits or maybe as a separate section like "Why join us?" but not in allowed headings. Since allowed headings are limited, we could incorporate those points into Benefits section as additional bullet points. Pay: Not specified (just "Competitive salary and rewards package" but no actual number). The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Competitive salary and rewards package" is a statement about pay but not a specific number. Is that enough to create a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not require a specific number; just states them. The phrase "Competitive salary and rewards package" is a statement about pay. So we could include a Pay section with that statement. However they also said "Prefer a few substantive sections over many thin ones." Might be better to combine Pay into Benefits? But they have separate headings for Benefits and Pay. Since we have a statement about pay, we could create a Pay section with that line. But we also have benefits list. Could we combine Pay and Benefits into one Benefits section? The instruction says to use headings only when posting has real, specific content for it. It does not forbid combining, but we have separate headings allowed. If we create a Pay section with just "Competitive salary and rewards package" that might be considered thin. Better to incorporate into Benefits section as part of benefits. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we cannot combine them; but we have to decide. Given the instruction to prefer a few substantive sections over many thin ones, I'd combine Pay into Benefits (or maybe have Benefits section that includes both compensation and benefits). However they explicitly list Benefits and Pay as separate possible headings. If we omit Pay, we are not creating a Pay section, which is fine because we are not stating specific pay details. The phrase "Competitive salary and rewards package" is more about benefits/compensation. I'd put it under Benefits. Schedule: Not mentioned. No schedule info. So we omit Schedule. Thus sections: About the role, Responsibilities, Requirements (maybe), Qualifications (maybe), Benefits. We need to decide on Requirements vs Qualifications vs Skills. The posting has "Your Experience and Background include:" which seems like requirements. Then "Additional experience ... is preferred." which could be preferred qualifications. Could treat as Qualifications. Skills: maybe Microsoft Office proficiency, typing speed, communication skills could be skills. But we can merge. Given the instruction to prefer few substantive sections, we could have: - About the role (prose) - Responsibilities (list) - Requirements (list of mandatory items) - Qualifications (list of preferred items) - Benefits (list of offered items) That's five sections, each substantive. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, immigration sponsorship, AI-assisted tech, etc. Also remove duplicated lines like "HID Global Identity and Access Management Solutions products protect more than 85 million user identities." appears twice; we keep only once. Also remove "Check us out here: www.hidglobal.com and https://youtu.be/23km5H4K9Eo" maybe considered navigation? It's a link but could be considered part of About the company? Might be okay to keep as part of About the role? It's not essential; but it's not boilerplate? It's a link to company site and video. Might be considered navigation? Probably safe to keep as part of About the role? But it's not required. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link is not navigation per se but could be considered navigation. Safer to remove it. Also remove "We are a high-tech software company headquartered in Austin, TX, with over 4,500 worldwide employees." That's substantive about company; keep. Also remove "Identity and Access Management Solutions (IAMS): HID Global IAM products protect more than 85 million user identities." Keep one. Also remove "At HID Global, we understand that no person, device, or workplace can go unprotected..." that's substantive about philosophy; keep. Also remove "As our Registration Analyst, you’ll support HID’s success by:" we keep as intro to responsibilities. Also remove "Your Experience and Background include:" we keep as intro to requirements. Also remove "What we can offer you:" we keep as intro to benefits. Also remove "Why apply?" we could incorporate into benefits or maybe as separate section but we decided not. Also remove "Empowerment: You’ll work as part of a global team..." etc. Could be part of benefits/culture. We'll incorporate into benefits as bullet points. Also remove "We welcome an opportunity to meet you..." etc. That's fluff; maybe remove as it's application encouragement. Could be considered boilerplate? It's not EEO but it's generic. Might be safe to remove. Also remove "Innovation: You embrace challenges..." etc. Could be kept as part of benefits? Might be considered fluff. I'd remove to keep concise. Also remove "Integrity: You are results-orientated..." etc. Might be fluff. Given the instruction to preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all substantive info, not just summarizing. The "Why apply?" bullet points are substantive? They describe empowerment, innovation, integrity. They are part of the selling points. Might be considered substantive. However they are somewhat generic but still part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep them. But we need to fit them into allowed sections. Could add a section "Why join us?" but not allowed heading. Could incorporate into Benefits or maybe into About the role? Might be okay to add a section "Why apply?" but not in allowed headings list. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings only. It does not explicitly forbid other headings, but says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but likely they want only those headings. Safer to stick to those. Thus we need to map the "Why apply?" content into one of those sections. Perhaps Benefits section can include those as bullet points about empowerment, innovation, integrity. That seems plausible. Now we need to ensure we don't include any boilerplate like EEO, immigration sponsorship, AI-assisted tech, etc. Let's extract substantive content: Location: Salt Lake City, Utah (maybe include in About the role or a separate line). Could be included in About the role paragraph. Job ID: 51189 - drop. Role description: "The Registration Analyst is responsible for ensuring that applications for identification certificates are received securely, thoroughly verified, and accurately processed. This role ensures that customer orders are fulfilled correctly and that each customer receives exceptional service throughout the application process." Company description: "Who are we? HID powers the trusted identities of the world’s people, places, and things, allowing people to transact safely, work productively and travel freely. We are a high-tech software company headquartered in Austin, TX, with over 4,500 worldwide employees." plus maybe the link removed. IAMS description: "Identity and Access Management Solutions (IAMS): HID Global IAM products protect more than 85 million user identities." (only once) Philosophy: "At HID Global, we understand that no person, device, or workplace can go unprotected. This philosophy of Zero Trust drives us to create new advances in risk-based multi-factor authentication, leads us to secure user identities in converged access environments and drives the need to expand implementations with our industry-leading digital certificates and PKIaaS solution to manage them at scale." Responsibilities list (as bullet points): - Reviewing incoming certificate applications in the web‑based system for completeness. - Performing Identification & Authentication (I&A) checks at required levels. - Processing incoming mail and