Test Proctor

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. The posting includes: - Title: Test Center Administrator (TCA) (we do not repeat as heading) - Location: address (maybe minor metadata) - Wage: $18.25/hr. plus benefits for full time positions - Hours: Full Time: Schedule Options Tues/Wed/Fri/Sat (8a-5:30p, close) Mon/Thurs/Fri/Sat (8a-5:30p, close) - About PSI (company description) maybe not needed? Could be part of About the role? Actually "About PSI" is separate but we can include as part of About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications and Skills if present. The posting includes "Knowledge, Skills And Experience Requirements". That's a mix. We can split into Requirements (maybe includes knowledge, skills, experience). Could also have Skills separate but we can combine. We must not create sections with filler like "commensurate with experience". We have actual content. We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO etc). There's none. We need to output only HTML fragment, no /, no markdown fences. We need to use

for each section heading, then content: either

for prose,

• for lists. We need to include location and wage maybe as minor metadata in a short

  or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include location and wage in a

  maybe before sections. We need to include schedule options as schedule section. Pay: wage $18.25/hr plus benefits. Benefits: list of benefits. Responsibilities: list of duties. About the role: description. Requirements: list of knowledge, skills, experience. We may also have Qualifications separate but we can incorporate into Requirements. We need to avoid duplicate content. Let's extract: About PSI: "Join PSI – A Global Leader in Testing Solutions At PSI, we help people achieve their goals through fair and secure assessments. We provide license and certification exams for state and federal agencies, as well as assessments, for public and private companies. Our mission is to create a positive testing experience that empowers candidates to succeed." But that's about company, not role. Could be part of About the role? Might be considered boilerplate? It's substantive but not role-specific. The instruction: "About the role" heading for section about role. The "About PSI" could be considered company overview; maybe we can include under About the role? But better to include as part of About the role? The role description includes "About The Role As a Test Center Administrator (Exam Proctor), you’ll play a critical role..." So we can combine. Thus About the role section will contain both the company overview and role description? Might be okay. Responsibilities list: - Welcome test takers and explain testing procedures clearly. - Verify IDs and maintain strict exam security protocols. - Set up workstations and troubleshoot technical issues with internal teams. - Supervise exams and ensure compliance with PSI policies. - Perform opening/closing procedures and light housekeeping (e.g., sanitizing workstations). - Troubleshoot with internal departments, such as our IT department, to fix any technical issues in the Test Center. - Provide support for test takers with accessibility needs. Requirements/Knowledge, Skills And Experience: - High school diploma or equivalent. - US citizenship is required. - Customer Service Experience Preferred (training Provided). - Strong communication skills and attention to detail. - Ability to remain calm under pressure and handle sensitive situations. - Basic computer skills; Microsoft Office experience is a plus. - Physical ability to stand/walk for up to 40% of your shift. - Commitment to exam security and compliance. Benefits & Perks list: - Competitive pay + comprehensive benefits (medical, dental, vision). - Paid time off and retirement plans (401(k), pension). - Flexible scheduling and work-life balance. - Career development and training opportunities. - Wellness programs and global initiatives. - Volunteer opportunities and community engagement. Pay: $18.25/hr. plus benefits for full time positions. Schedule: Full Time: Schedule Options Tues/Wed/Fri/Sat (8a-5:30p, close) Mon/Thurs/Fri/Sat (8a-5:30p, close) We need to output sections only if they have real specific content. All have. We should not repeat job title as heading. We need to include location maybe as a short

  before sections. Let's craft HTML:

  Location: 7 Entin Rd, Suite D, Parsippany, NJ 07054

  Wage: $18.25/hr. plus benefits for full time positions

  Then sections:

  About the role

  Join PSI – A Global Leader in Testing Solutions. At PSI, we help people achieve their goals through fair and secure assessments. We provide license and certification exams for state and federal agencies, as well as assessments for public and private companies. Our mission is to create a positive testing experience that empowers candidates to succeed. As a Test Center Administrator (Exam Proctor), you’ll play a critical role in maintaining exam integrity and delivering a smooth, professional experience for every test taker. This is an entry-level position with training provided, perfect for individuals who value accuracy, customer service, and a calm testing environment.

  Responsibilities

  • Welcome test takers and explain testing procedures clearly.
  • Verify IDs and maintain strict exam security protocols.
  • Set up workstations and troubleshoot technical issues with internal teams.
  • Supervise exams and ensure compliance with PSI policies.
  • Perform opening/closing procedures and light housekeeping (e.g., sanitizing workstations).
  • Troubleshoot with internal departments, such as our IT department, to fix any technical issues in the Test Center.
  • Provide support for test takers with accessibility needs.

  Requirements

  • High school diploma or equivalent.
  • US citizenship is required.
  • Customer Service Experience Preferred (training Provided).
  • Strong communication skills and attention to detail.
  • Ability to remain calm under pressure and handle sensitive situations.
  • Basic computer skills; Microsoft Office experience is a plus.
  • Physical ability to stand/walk for up to 40% of your shift.
  • Commitment to exam security and compliance.

  Benefits

  • Competitive pay + comprehensive benefits (medical, dental, vision).
  • Paid time off and retirement plans (401(k), pension).
  • Flexible scheduling and work-life balance.
  • Career development and training opportunities.
  • Wellness programs and global initiatives.
  • Volunteer opportunities and community engagement.

  Pay

  $18.25/hr. plus benefits for full time positions

  Schedule

  Full Time: Schedule Options Tues/Wed/Fri/Sat (8a-5:30p, close) Mon/Thurs/Fri/Sat (8a-5:30p, close)

  We already have wage in earlier p; but we also have Pay section repeating. Might be duplicate. The instruction: do not repeat job title as heading, but we can repeat wage? It's okay but maybe we should not duplicate. We could drop the earlier wage p and rely on Pay section. But location we can keep as minor metadata. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So location and wage are minor metadata; we can put them in a short

  before sections. Then we still need Pay section? The Pay section would be duplicate of wage. But we could omit Pay section if we already included wage in metadata. However the instruction says: "Prefer a few substantive sections over many thin ones." If we put wage in metadata, we might not need a separate Pay section. But the Pay section is a heading that would have specific content (the wage). If we already put wage in metadata, we could still have Pay section but it would be duplicate. Better to not duplicate. So we can include location and wage in a single

  metadata, and not have a separate Pay section. However the instruction says: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we omit Pay section, that's fine because we already conveyed pay in metadata. But we might lose the heading "Pay" which is one of the suggested headings. But it's not required to include all headings; only include if there is real specific content. Since we already included wage in metadata, we could still have a Pay section with that same content; but that would be duplicate. The instruction didn't forbid duplication explicitly, but we should avoid redundancy. I'd choose to include Pay section and drop the metadata wage line, keeping location only as metadata. Or we could include both location and wage in metadata and not have Pay section. Which is better? The instruction says "fold minor metadata into a short

  or drop it." So we can fold wage into a short

  . Then we don't need a Pay heading. That seems to follow the instruction: we are not creating a Pay section unless the posting actually states them (it does state them). But we are stating them in the metadata p. That's okay. However they said "Prefer a few substantive sections over many thin ones." Having a Pay section with just a line might be thin. So better to incorporate wage into metadata and not have a separate Pay section. Let's do that. Thus we will have:

  Location: 7 Entin Rd, Suite D, Parsippany, NJ 07054

  Wage: $18.25/hr. plus benefits for full time positions

  Then sections: About the role, Responsibilities, Requirements, Benefits, Schedule. We might also include Qualifications? Not needed. Check that we haven't missed any substantive info: The "Why You’ll Love Working Here" paragraph is more fluff but could be considered part of About the role or Benefits? It's about culture. Could be omitted as boilerplate? It's not a list but it's substantive. However it's somewhat generic. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly boilerplate but could be considered promotional. Might be okay to include in About the role? But we already have About the role covering role description. Could add a paragraph after About the role about why you'll love working here. However that might be considered filler? It's specific to PSI: "At PSI, you’re more than an employee—you’re part of a global team making a real impact. We value integrity, growth, and purpose. If you’re ready to join a company that invests in your future, apply today!" That's somewhat generic but still specific to PSI. The instruction says remove duplicated lines and application