Senior Administrative Coordinator
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Key sections:
- Overview (maybe "About the role"? Actually "Overview" describes the directorate, not the role. Could be "About the role" or "About the position". The posting includes "Overview" describing PNNL directorates, OSD, etc. That's about the role context. Could be "About the role". We'll include that as a section.
- Responsibilities: there is a "Responsibilities" heading with bullet points (though they are sentences separated by periods). We'll need to extract each responsibility as list items.
- Qualifications: there is "Minimum Qualifications:" and "Preferred Qualifications". Also "Experience in planning meetings and coordinating travel" is under Minimum? Actually after Minimum Qualifications line: "Experience in planning meetings and coordinating travel". Then "Preferred Qualifications" list.
- Additional Information: "Not Applicable." That's placeholder; we should not create a section for it because it's filler.
- About PNNL: description of PNNL, benefits, location, etc. Could be "About the organization" or "About PNNL". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the organization" but we could use "About the role" for overview and maybe "About PNNL" as part of that? But we should stick to allowed headings. However we can also create other headings if needed? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. It says "Prefer a few substantive sections over many thin ones." Likely we should use those headings where applicable. For "About PNNL" maybe we can put under "About the role". Or we could create a section "About the organization" but not in list; maybe better to incorporate into "About the role". We'll include overview and PNNL description in "About the role".
- Benefits: The posting mentions "Rockstar Rewards Employees and their families are offered medical insurance, dental insurance, vision insurance, robust telehealth care options, several mental health benefits, free wellness coaching, health savings account, flexible spending accounts, basic life insurance, disability insurance*, employee assistance program, business travel insurance, tuition assistance, relocation, backup childcare, legal benefits, supplemental parental bonding leave, surrogacy and adoption assistance, and fertility support. Employees are automatically enrolled in our company-funded". That's benefits details. So we should include a Benefits section with list.
- Pay: Not mentioned. No salary. So we should NOT create Pay section.
- Schedule: The posting says "This position is based in Richland, WA and requires an onsite presence 4 days a week." That's schedule info. So we should include a Schedule section.
- Skills: Not explicitly listed; maybe we could infer from qualifications but better not to create Skills unless there is explicit skills list. There's "Professional judgment", "Effective relationship management", etc. Those are more like qualifications/skills. Could be placed under Qualifications. We'll not create separate Skills unless needed.
- Requirements: Could be same as Qualifications? The instruction includes Requirements as a possible heading. We have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements section. But we already have Qualifications heading. We'll use Qualifications for both minimum and preferred. Or we could split: Requirements for minimum, Qualifications for preferred? But we need to avoid thin sections. Let's combine into Qualifications.
Thus sections: About the role (h3), Responsibilities (h3), Qualifications (h3), Benefits (h3), Schedule (h3).
Now we need to extract content.
About the role: Should include overview text about PNNL directorates, OSD, etc., plus the About PNNL paragraph (including benefits? but benefits separate). We'll include overview and About PNNL description up to before benefits? Actually About PNNL includes benefits description later; we separated benefits. So we need to split About PNNL text: first part: "Pacific Northwest National Laboratory (PNNL) is a world-class research institution powered by a highly educated, diverse workforce committed to the values of Integrity, Creativity, Collaboration, Impact, and Courage. Every year, scores of dynamic, driven people come to PNNL to work with renowned researchers on meaningful science, innovations and outcomes for the U.S. Department of Energy and other sponsors; here is your chance to be one of them! At PNNL, you will find an exciting research environment and excellent benefits including health insurance, and flexible work schedules. PNNL is located in eastern Washington State—the dry side of Washington known for its stellar outdoor recreation and affordable cost of living. The Lab’s campus is only a 45-minute flight (or ~3 hour drive) from Seattle or Portland, and is serviced by the convenient PSC airport, connected to 8 major hubs."
That includes mention of benefits (health insurance, flexible work schedules). But we have a separate Benefits section with detailed list. To avoid duplication, we could keep the general mention in About the role and then Benefits section list the specific rewards. That's okay; we preserve all substantive info. Not duplicate exactly but overlapping. It's fine.
Now Responsibilities: The responsibilities block is a long paragraph with many sentences separated by periods. We need to break into list items. Each sentence seems to be a responsibility. Let's list them:
1. Provide comprehensive, proactive administrative support to the PI&E staff, manage complex calendars for PI&E leadership, coordinate meetings and logistics, prepare agendas and materials, track action items, and manage executive correspondence.
2. Anticipate administrative, scheduling, reporting, and information needs; gather and organize information, identify potential conflicts or gaps, and take appropriate action within established procedures to keep division priorities moving forward.
3. Coordinate end-to-end travel and expense processes for staff including travel requests, itinerary planning, expense reporting, corporate card monitoring, issue resolution, compliance documentation, and guidance on applicable policies and best practices.
4. Serve as a primary administrative point of contact for staff, providing support and guidance on Laboratory tools, processes, policies, and best practices related to training, IT hardware, procurement, DOE correspondence, meeting coordination, and other administrative services.
5. Coordinate division purchasing and supply needs, including supplies, materials, and equipment; initiate and track purchase requests, resolve routine and issues, and help ensure requests are complete, timely, and compliant with applicable requirements.
6. Support FIGC activities and associated administrative processes, coordinating information, documentation, scheduling, and follow-through as needed.
7. Assists with submitting and tracking staff memberships, licenses, and certifications, including preparing written justifications and processing related purchases. The position ensures all documentation is accurate, current, and compliant with organizational requirements.
8. Coordinate recruiting and hiring activities, including creation and routing of job requisitions, interview scheduling, panel logistics, preparation of materials, and candidate and panel communications, onboarding, in partnership with hiring managers and HR/Talent Acquisition.
9. Coordinate new-hire onboarding from pre-arrival through the first weeks of employment, including orientation, access requests, workspace readiness, equipment provisioning, required training, introductions, and first-week schedules.
10. Coordinate and track formal correspondence, including letters, memos, and notifications, from draft through review, approval, signature, distribution, and archiving; complete required Correspondence and Commitment Tracking System training.
11. Draft, edit, and format clear, professional communications, presentations, meeting materials, and other content that may be distributed across multiple organizations; ensure materials are accurate, complete, and appropriate for the intended audience.
12. Maintain organized electronic and physical records, meeting documentation, operational materials, and administrative records; support consistent records management and retrieval practices.
13. Apply knowledge of PI&E and Laboratory processes to identify and address administrative issues, gather information needed to resolve or escalate problems, and coordinate with appropriate partners through resolution.
14. Provide guidance and support to administrative team members and share knowledge, tools, and effective practices that strengthen consistency and continuity of administrative support.
15. Participate actively as a member of the Operational Systems Directorate administrative team, providing cross-coverage and backup support during absences and contributing to coordinated administrative practices across the directorate.
16. Identify opportunities to improve administrative workflows, coordination, and service; recommend practical improvements and support implementation within established procedures and practices.
That seems comprehensive.
Now Qualifications: Minimum Qualifications: "High school diploma/GED and 8 years of relevant experience in an administrative environment -OR-AA degree or higher and 6 years of relevant experience in an administrative environment." Also "Experience in planning meetings and coordinating travel" (maybe part of Minimum). Then Preferred Qualifications list: "Professional judgment in fast‑moving operational environments. Effective relationship management with staff, subcontractors, and leadership. Exceptional attention to detail across scheduling, documentation, and operational coordination. Initiative and ownership of administrative workflows and improvement opportunities. Clear, confident communication, both written and verbal. Experience coordinating business travel, including travel planning, booking, expense reporting, and account reconciliation using the Concur travel system."
We'll put these as list items under Qualifications, maybe separate Minimum and Preferred? Could have two subheadings but we should avoid many thin sections. Could just list all qualifications as bullet points, noting minimum vs preferred? Might be okay to just list them all. But we need to preserve ALL substantive information; we can include both minimum and preferred as separate bullet groups with a note. Could do - Minimum: ...
etc. That's acceptable.
Now Benefits: The "Rockstar Rewards" paragraph lists many benefits. We'll extract each benefit as list items.
List: medical insurance, dental insurance, vision insurance, robust telehealth care options, several mental health benefits, free wellness coaching, health savings account, flexible spending accounts, basic life insurance, disability insurance*, employee assistance program, business travel insurance, tuition assistance, relocation, backup childcare, legal benefits, supplemental parental bonding leave, surrogacy and adoption assistance, fertility support. Also "Employees are automatically enrolled in our company-funded" (maybe missing continuation). We'll include that as a bullet: "Automatically enrolled in company-funded [plan]" but it's incomplete. The text cut off: "Employees are automatically enrolled in our company-funded". Probably missing something like "retirement plan"? But we cannot invent. We'll include the phrase as is: "Employees are automatically enrolled in our company-funded". Might be placeholder but it's actual text. We'll keep it.
Now Schedule: "This position is based in Richland, WA and requires an onsite presence 4 days a week." We'll put as a paragraph.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce:
About the role
...overview text...
...About PNNL text (up to before benefits)...
Responsibilities
- ...
...
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to parse the posting. Key sections: - Overview (maybe "About the role"? Actually "Overview" describes the directorate, not the role. Could be "About the role" or "About the position". The posting includes "Overview" describing PNNL directorates, OSD, etc. That's about the role context. Could be "About the role". We'll include that as a section. - Responsibilities: there is a "Responsibilities" heading with bullet points (though they are sentences separated by periods). We'll need to extract each responsibility as list items. - Qualifications: there is "Minimum Qualifications:" and "Preferred Qualifications". Also "Experience in planning meetings and coordinating travel" is under Minimum? Actually after Minimum Qualifications line: "Experience in planning meetings and coordinating travel". Then "Preferred Qualifications" list. - Additional Information: "Not Applicable." That's placeholder; we should not create a section for it because it's filler. - About PNNL: description of PNNL, benefits, location, etc. Could be "About the organization" or "About PNNL". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the organization" but we could use "About the role" for overview and maybe "About PNNL" as part of that? But we should stick to allowed headings. However we can also create other headings if needed? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list. It says "Prefer a few substantive sections over many thin ones." Likely we should use those headings where applicable. For "About PNNL" maybe we can put under "About the role". Or we could create a section "About the organization" but not in list; maybe better to incorporate into "About the role". We'll include overview and PNNL description in "About the role".
- Benefits: The posting mentions "Rockstar Rewards Employees and their families are offered medical insurance, dental insurance, vision insurance, robust telehealth care options, several mental health benefits, free wellness coaching, health savings account, flexible spending accounts, basic life insurance, disability insurance*, employee assistance program, business travel insurance, tuition assistance, relocation, backup childcare, legal benefits, supplemental parental bonding leave, surrogacy and adoption assistance, and fertility support. Employees are automatically enrolled in our company-funded". That's benefits details. So we should include a Benefits section with list.
- Pay: Not mentioned. No salary. So we should NOT create Pay section.
- Schedule: The posting says "This position is based in Richland, WA and requires an onsite presence 4 days a week." That's schedule info. So we should include a Schedule section.
- Skills: Not explicitly listed; maybe we could infer from qualifications but better not to create Skills unless there is explicit skills list. There's "Professional judgment", "Effective relationship management", etc. Those are more like qualifications/skills. Could be placed under Qualifications. We'll not create separate Skills unless needed.
- Requirements: Could be same as Qualifications? The instruction includes Requirements as a possible heading. We have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements section. But we already have Qualifications heading. We'll use Qualifications for both minimum and preferred. Or we could split: Requirements for minimum, Qualifications for preferred? But we need to avoid thin sections. Let's combine into Qualifications.
Thus sections: About the role (h3), Responsibilities (h3), Qualifications (h3), Benefits (h3), Schedule (h3).
Now we need to extract content.
About the role: Should include overview text about PNNL directorates, OSD, etc., plus the About PNNL paragraph (including benefits? but benefits separate). We'll include overview and About PNNL description up to before benefits? Actually About PNNL includes benefits description later; we separated benefits. So we need to split About PNNL text: first part: "Pacific Northwest National Laboratory (PNNL) is a world-class research institution powered by a highly educated, diverse workforce committed to the values of Integrity, Creativity, Collaboration, Impact, and Courage. Every year, scores of dynamic, driven people come to PNNL to work with renowned researchers on meaningful science, innovations and outcomes for the U.S. Department of Energy and other sponsors; here is your chance to be one of them! At PNNL, you will find an exciting research environment and excellent benefits including health insurance, and flexible work schedules. PNNL is located in eastern Washington State—the dry side of Washington known for its stellar outdoor recreation and affordable cost of living. The Lab’s campus is only a 45-minute flight (or ~3 hour drive) from Seattle or Portland, and is serviced by the convenient PSC airport, connected to 8 major hubs."
That includes mention of benefits (health insurance, flexible work schedules). But we have a separate Benefits section with detailed list. To avoid duplication, we could keep the general mention in About the role and then Benefits section list the specific rewards. That's okay; we preserve all substantive info. Not duplicate exactly but overlapping. It's fine.
Now Responsibilities: The responsibilities block is a long paragraph with many sentences separated by periods. We need to break into list items. Each sentence seems to be a responsibility. Let's list them:
1. Provide comprehensive, proactive administrative support to the PI&E staff, manage complex calendars for PI&E leadership, coordinate meetings and logistics, prepare agendas and materials, track action items, and manage executive correspondence.
2. Anticipate administrative, scheduling, reporting, and information needs; gather and organize information, identify potential conflicts or gaps, and take appropriate action within established procedures to keep division priorities moving forward.
3. Coordinate end-to-end travel and expense processes for staff including travel requests, itinerary planning, expense reporting, corporate card monitoring, issue resolution, compliance documentation, and guidance on applicable policies and best practices.
4. Serve as a primary administrative point of contact for staff, providing support and guidance on Laboratory tools, processes, policies, and best practices related to training, IT hardware, procurement, DOE correspondence, meeting coordination, and other administrative services.
5. Coordinate division purchasing and supply needs, including supplies, materials, and equipment; initiate and track purchase requests, resolve routine and issues, and help ensure requests are complete, timely, and compliant with applicable requirements.
6. Support FIGC activities and associated administrative processes, coordinating information, documentation, scheduling, and follow-through as needed.
7. Assists with submitting and tracking staff memberships, licenses, and certifications, including preparing written justifications and processing related purchases. The position ensures all documentation is accurate, current, and compliant with organizational requirements.
8. Coordinate recruiting and hiring activities, including creation and routing of job requisitions, interview scheduling, panel logistics, preparation of materials, and candidate and panel communications, onboarding, in partnership with hiring managers and HR/Talent Acquisition.
9. Coordinate new-hire onboarding from pre-arrival through the first weeks of employment, including orientation, access requests, workspace readiness, equipment provisioning, required training, introductions, and first-week schedules.
10. Coordinate and track formal correspondence, including letters, memos, and notifications, from draft through review, approval, signature, distribution, and archiving; complete required Correspondence and Commitment Tracking System training.
11. Draft, edit, and format clear, professional communications, presentations, meeting materials, and other content that may be distributed across multiple organizations; ensure materials are accurate, complete, and appropriate for the intended audience.
12. Maintain organized electronic and physical records, meeting documentation, operational materials, and administrative records; support consistent records management and retrieval practices.
13. Apply knowledge of PI&E and Laboratory processes to identify and address administrative issues, gather information needed to resolve or escalate problems, and coordinate with appropriate partners through resolution.
14. Provide guidance and support to administrative team members and share knowledge, tools, and effective practices that strengthen consistency and continuity of administrative support.
15. Participate actively as a member of the Operational Systems Directorate administrative team, providing cross-coverage and backup support during absences and contributing to coordinated administrative practices across the directorate.
16. Identify opportunities to improve administrative workflows, coordination, and service; recommend practical improvements and support implementation within established procedures and practices.
That seems comprehensive.
Now Qualifications: Minimum Qualifications: "High school diploma/GED and 8 years of relevant experience in an administrative environment -OR-AA degree or higher and 6 years of relevant experience in an administrative environment." Also "Experience in planning meetings and coordinating travel" (maybe part of Minimum). Then Preferred Qualifications list: "Professional judgment in fast‑moving operational environments. Effective relationship management with staff, subcontractors, and leadership. Exceptional attention to detail across scheduling, documentation, and operational coordination. Initiative and ownership of administrative workflows and improvement opportunities. Clear, confident communication, both written and verbal. Experience coordinating business travel, including travel planning, booking, expense reporting, and account reconciliation using the Concur travel system."
We'll put these as list items under Qualifications, maybe separate Minimum and Preferred? Could have two subheadings but we should avoid many thin sections. Could just list all qualifications as bullet points, noting minimum vs preferred? Might be okay to just list them all. But we need to preserve ALL substantive information; we can include both minimum and preferred as separate bullet groups with a note. Could do - Minimum: ...
etc. That's acceptable.
Now Benefits: The "Rockstar Rewards" paragraph lists many benefits. We'll extract each benefit as list items.
List: medical insurance, dental insurance, vision insurance, robust telehealth care options, several mental health benefits, free wellness coaching, health savings account, flexible spending accounts, basic life insurance, disability insurance*, employee assistance program, business travel insurance, tuition assistance, relocation, backup childcare, legal benefits, supplemental parental bonding leave, surrogacy and adoption assistance, fertility support. Also "Employees are automatically enrolled in our company-funded" (maybe missing continuation). We'll include that as a bullet: "Automatically enrolled in company-funded [plan]" but it's incomplete. The text cut off: "Employees are automatically enrolled in our company-funded". Probably missing something like "retirement plan"? But we cannot invent. We'll include the phrase as is: "Employees are automatically enrolled in our company-funded". Might be placeholder but it's actual text. We'll keep it.
Now Schedule: "This position is based in Richland, WA and requires an onsite presence 4 days a week." We'll put as a paragraph.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce:
About the role
...overview text...
...About PNNL text (up to before benefits)...
Responsibilities
- ...
...
About the role
...overview text...
...About PNNL text (up to before benefits)...
Responsibilities
- ... ...