Personnel Employment Assistant II
Serco · Whidbey Island Station, WA · 1 mo ago
Human ResourcesPart-time
We need to output only HTML fragment, using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not put Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to parse the posting.
Key content:
Position Description & Qualifications: description of role.
Responsibilities (list of duties): bullet points after "In This Role, You Will". Many items.
Requirements: "To Be Successful In This Role, You Must Have" list.
Additional Desired Qualifications: list.
Compensation, benefits, etc: mention Service Contract Act, compensation, benefits, health and welfare requirements administered per WD. Also mention "Pay Transparency" section with total rewards, benefits list, etc. Also mention "Benefits – Comprehensible benefits for full-time employees..." list.
We need to decide sections: About the role (maybe a paragraph summarizing role). Responsibilities (list). Requirements (list). Qualifications (maybe combine required and desired? But we have separate sections: Requirements and Qualifications. The instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put required qualifications under Requirements, desired under Qualifications, maybe Skills separate if we have skill list. But we can also combine.
We need to avoid filler headings. If a section lacks real specific content, we omit it.
We have content for About the role: description paragraph.
Responsibilities: many bullet points.
Requirements: list of mandatory qualifications.
Qualifications: additional desired qualifications.
Skills: maybe we can extract skills from requirements: proficiency with Microsoft Office, strong organizational, communication, customer service skills. Could be a Skills section.
Benefits: there is a benefits list.
Pay: there is mention of salary range: "The hourly amount for this position can be found at the top of this posting." Not provided in text. Also "Pay Transparency Our Total Rewards package includes competitive pay, performance-based incentives, and benefits..." Not specific numbers. There's also mention of Service Contract Act prevailing wage. No specific pay amount given. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have no specific number; we have generic statements but not a specific amount. Should we include Pay? The posting says "Salary range: The hourly amount for this position can be found at the top of this posting." Since we don't have that amount, we cannot provide specific pay. The rule: never create Pay section unless posting actually states them. It does state that the hourly amount can be found at top of posting, but we don't have it. It's not a specific value. Likely we should omit Pay section because we don't have concrete pay info. Similarly Schedule: no schedule info.
Benefits: there is a benefits list. So we include Benefits section.
Now we need to output HTML fragment with headings
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not put Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to parse the posting.
Key content:
Position Description & Qualifications: description of role.
Responsibilities (list of duties): bullet points after "In This Role, You Will". Many items.
Requirements: "To Be Successful In This Role, You Must Have" list.
Additional Desired Qualifications: list.
Compensation, benefits, etc: mention Service Contract Act, compensation, benefits, health and welfare requirements administered per WD. Also mention "Pay Transparency" section with total rewards, benefits list, etc. Also mention "Benefits – Comprehensible benefits for full-time employees..." list.
We need to decide sections: About the role (maybe a paragraph summarizing role). Responsibilities (list). Requirements (list). Qualifications (maybe combine required and desired? But we have separate sections: Requirements and Qualifications. The instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put required qualifications under Requirements, desired under Qualifications, maybe Skills separate if we have skill list. But we can also combine.
We need to avoid filler headings. If a section lacks real specific content, we omit it.
We have content for About the role: description paragraph.
Responsibilities: many bullet points.
Requirements: list of mandatory qualifications.
Qualifications: additional desired qualifications.
Skills: maybe we can extract skills from requirements: proficiency with Microsoft Office, strong organizational, communication, customer service skills. Could be a Skills section.
Benefits: there is a benefits list.
Pay: there is mention of salary range: "The hourly amount for this position can be found at the top of this posting." Not provided in text. Also "Pay Transparency Our Total Rewards package includes competitive pay, performance-based incentives, and benefits..." Not specific numbers. There's also mention of Service Contract Act prevailing wage. No specific pay amount given. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have no specific number; we have generic statements but not a specific amount. Should we include Pay? The posting says "Salary range: The hourly amount for this position can be found at the top of this posting." Since we don't have that amount, we cannot provide specific pay. The rule: never create Pay section unless posting actually states them. It does state that the hourly amount can be found at top of posting, but we don't have it. It's not a specific value. Likely we should omit Pay section because we don't have concrete pay info. Similarly Schedule: no schedule info.
Benefits: there is a benefits list. So we include Benefits section.
Now we need to output HTML fragment with headings and content:
for prose,
- for lists.
We must not include boilerplate like EEO, application instructions, etc. Also remove duplicated lines.
Let's extract content.
About the role: The first paragraph: "The Personnel Assistant II (Identity Credentialing Specialist) provides professional customer service and administrative support in a secure credentialing environment. This position verifies customer identity, processes credential applications and updates, maintains electronic records, and ensures compliance with established organizational policies, security requirements, and operating procedures. The successful candidate demonstrates exceptional attention to detail, professionalism, and a commitment to providing outstanding customer service while safeguarding sensitive information. This position is designated for the capture of Navy ICA incumbent personnel."
We can keep that as prose.
Responsibilities: list after "In This Role, You Will". Let's capture each bullet:
- Provide courteous, professional, and timely customer service to individuals requesting identity credentialing and related administrative services.
- Verify customer identity and eligibility using authorized credentialing and enrollment systems.
- Process new credential requests, renewals, replacements, updates, and related administrative transactions.
- Review applications and support documentation for completeness, accuracy, and compliance with established procedures.
- Enter, update, and maintain electronic records with a high degree of accuracy.
- Assist customers with application requirements, documentation, and eligibility questions.
- Process credential maintenance transactions, including password resets, certificate updates, and account maintenance, as authorized.
- Operate credential production equipment, scanners, cameras, printers, computers, and other office equipment.
- Perform basic user-level maintenance and troubleshooting of office equipment.
- Protect sensitive and confidential information in accordance with applicable privacy and security requirements.
- Maintain accountability of controlled materials, supplies, and equipment.
- Respond to customer inquiries by telephone, email, and in person in a professional and courteous manner.
We should ensure no duplication.
Requirements (mandatory): list after "To Be Successful In This Role, You Must Have":
- High school diploma or equivalent.
- Minimum one (1) year of experience in customer service, administrative support, records management, human resources, office administration, or a related field.
- Experience using computerized information systems for data entry and record maintenance.
- Proficiency with Microsoft Office applications, including Word, Excel, Outlook, and Teams.
- Strong organizational, communication, and customer service skills.
- Must be able to successfully complete all required background screening and maintain eligibility for access to secure systems and facilities.
Qualifications (desired): list after "Additional Desired Qualifications":
- Experience in identity management, credentialing, records administration, or document verification.
- Experience working in a highly regulated or security-focused environment.
- Experience providing face-to-face customer support in a high-volume office.
- Experience using enterprise database applications.
Skills: Could extract from requirements: proficiency with Microsoft Office, strong organizational, communication, customer service skills. Also maybe "experience using computerized information systems". We could make a Skills section with those items.
But we need to avoid duplication: if we put skills in Skills section, we might also have them in Requirements. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the info somewhere. If we put them in Requirements, we can still also put them in Skills? That would duplicate. Better to keep them only in Requirements and not create a Skills section unless we have distinct skill info not covered elsewhere. The Skills section could be used for skills like "proficiency with Microsoft Office applications, strong organizational, communication, and customer service skills". But those are already in Requirements. If we create Skills section, we would be duplicating. The instruction says preserve ALL substantive information; it doesn't forbid duplication, but better to avoid unnecessary duplication. However, we need to decide whether to include Skills section. The posting does not have a separate "Skills" heading; we could create one if we have skill-specific content not already captured. Since we have skill info in Requirements, we could omit Skills section to avoid thin section. The instruction: Prefer a few substantive sections over many thin ones. So we might omit Skills.
Benefits: we have a benefits list after "Benefits – Comprehensible benefits for full-time employees (part-time members receive a limited package tailored to their role):". Let's extract:
- Medical, dental, and vision insurance
- Robust vacation and sick leave benefits, and flexible work arrangements where permitted by role or contract
- 401(k) plan that includes employer matching funds
- Tuition reimbursement program
- Life insurance and disability coverage
- Optional coverages that can be purchased, including pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection
- Birth, adoption, parental leave benefits
- Employee Assistance Plan that includes counseling conditions
Also earlier there is mention of "Health and Welfare Benefits based on the WD for the contract." and "Total Rewards package includes competitive pay, performance-based incentives, and benefits that promote well-being and work-life balance". But we can keep the detailed list.
We should also maybe include mention of "Health and Welfare Benefits based on the WD for the contract." as part of benefits.
We need to ensure we don't include boilerplate like "Program availability may vary based on factors such as contract type, location, hire date, and applicable collective bargaining agreements." That's somewhat generic but still substantive? It's about benefits variability. Might be considered boilerplate but it's still info about benefits. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not exactly those categories; it's about benefits variability. Might keep.
But we need to avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "Program availability may vary based on factors such as contract type, location, hire date, and applicable collective bargaining agreements." includes "may vary". That's not prohibited; it's not a placeholder. It's substantive.
We'll include that as a sentence in benefits.
Now we need to output HTML.
Structure:
About the role
... paragraph ...
Responsibilities
- ... each ...
Requirements
- ... each ...
Qualifications
- ... each ...
Benefits
... maybe a paragraph summarizing benefits variability then list.
- ... each benefit ...