Front Office Action Officer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job posting.
Key parts:
- Job Family Program Management (PRO) Travel Required Up to 10% Clearance Required Active Secret
- What You Will Do: description of duties.
- What You Will Need: requirements: ACTIVE and MAINTAINED “TOP SECRET” Federal or DoD security clearance; THREE (3) or more years of experience in project / program support, task coordination, action coordination, administrative operations; TWO (2) or more years of experience supporting a U.S. Government client.
- What Would Be Nice To Have: nice-to-have: ACTIVE “TS/SCI” Federal or DoD security clearance; Bachelor’s Degree; Prior Front Office support experience, particularly in a DoD or federally funded R&D environment; Experience with Microsoft Office, Excel, Word, and PowerPoint; Prior experience providing briefing coordination and support; Prior experience in an Action Officer role; Project Management Professional (PMP) certification.
- What We Offer: Guidehouse offers a comprehensive, total rewards package... Benefits Include list.
- About Guidehouse: EEO etc (boilerplate to remove). Also includes accommodation contact etc (boilerplate). Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we need sections: About the role (maybe "What You Will Do" maps to About the role or Responsibilities). The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which headings to use based on content.
We have:
- About the role: could be a brief description of the role (maybe from "What You Will Do").
- Responsibilities: list of duties.
- Requirements: mandatory qualifications.
- Qualifications: maybe education? Could combine with Requirements? But we can separate: Requirements (mandatory) and Qualifications (preferred/nice-to-have). However they also have Skills section maybe for technical skills.
- Benefits: list of benefits.
- Pay: not specified (no salary). So we should NOT include Pay section because no specific content.
- Schedule: not specified (travel up to 10% maybe schedule? but not explicit schedule like full-time/part-time). Travel required up to 10% could be considered schedule? But instruction: only include if posting actually states them. Travel is not schedule; schedule would be like full-time, part-time, shift. Not present. So omit Schedule.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to ensure we don't repeat job title as heading.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail.
We need to remove boilerplate: EEO, accommodation contact, etc.
We need to keep the benefits list exactly as given.
Let's extract content.
**What You Will Do** (duties):
"A Front Office Action Officer will provide onsite operational and project management support for our Defense Advanced Research Projects Agency (DARPA) client. They will work in a fast-paced and highly collaborative environment supporting and tracking office and agency actions and deliverables, as well as managing program development processes, scheduling meetings and managing leadership calendars, and maintain overall office timelines. Tasks also include providing briefing development support for office leadership in collaboration with the technical subject matter experts, internal and external engagement coordination and support, documentation review, and engagement with support services across multiple technical and administrative stakeholders. The Action Officer will work as a part of a multi-discipline team made up of technical subject matter experts, program and financial analysts, contract administrators, government partners, and government project managers supporting the advancement of the current state of the art in a wide range of technology areas."
We can turn this into a prose paragraph (
) or maybe bullet list? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. This is prose, not a list. So we can put in
. However we could also break into bullet list for clarity but that would be inventing structure not present. Better to keep as prose.
**What You Will Need** (requirements):
- ACTIVE and MAINTAINED “TOP SECRET” Federal or DoD security clearance
- THREE (3) or more years of experience in project / program support, task coordination, action coordination, administrative operations
- TWO (2) or more years of experience supporting a U.S. Government client
These are list items. Use
- .
**What Would Be Nice To Have** (nice-to-have):
- ACTIVE “TS/SCI” Federal or DoD security clearance
- Bachelor’s Degree
- Prior Front Office support experience, particularly in a DoD or federally funded R&D environment
- Experience with Microsoft Office, Excel, Word, and PowerPoint
- Prior experience providing briefing coordination and support
- Prior experience in an Action Officer role
- Project Management Professional (PMP) certification
These could go under Qualifications or Skills. The instruction: Use headings like Qualifications, Skills. We need to decide.
Qualifications could include education and certifications. Skills could include technical skills like Microsoft Office, briefing coordination, etc. But we can also put all nice-to-have under Qualifications. However we have both Requirements and Qualifications sections. Let's assign:
- Requirements: mandatory (clearance, years experience, US Gov client experience).
- Qualifications: education (Bachelor’s Degree), certifications (PMP), maybe also prior Front Office support experience (experience). But that's also experience.
- Skills: technical skills (Microsoft Office, briefing coordination, etc.) and maybe also prior Action Officer role.
But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one section called Qualifications (or Skills). However instruction says prefer a few substantive sections over many thin ones. So we could have:
- About the role (prose)
- Responsibilities (list)
- Requirements (list)
- Qualifications (list) (including education, certifications, preferred experience, skills)
- Benefits (list)
That's 5 sections.
But we also have "What You Will Do" which is responsibilities; we could label that as Responsibilities.
Thus:
About the role
maybe a short summary: The role is Front Office Action Officer supporting DARPA client etc. But we already have duties in Responsibilities. The About the role could be a brief overview: "A Front Office Action Officer will provide onsite operational and project management support for our Defense Advanced Research Projects Agency (DARPA) client." That's from the first sentence. However we must not repeat content? We can reuse but must preserve all substantive information; we can include it in About the role as a short summary, but then we would be duplicating content if we also list duties in Responsibilities. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we need to include About the role section only if posting has real specific content for it. The posting does not have a separate "About the role" paragraph; the "What You Will Do" is essentially responsibilities. So we could treat "What You Will Do" as About the role (or Responsibilities). Since we need to pick headings, we can map "What You Will Do" to Responsibilities. Then we might not need About the role. But we need to include a section only when posting has real specific content for it. If we omit About the role, that's fine.
Thus we can have:
- Responsibilities (Responsibilities
) with the duties prose.
- Requirements (Requirements
) list.
- Qualifications (Qualifications
) list (nice-to-have).
- Benefits (Benefits
) list.
We could also add Skills if we want to separate technical skills, but that would be thin. Better to put all nice-to-have under Qualifications.
Now we need to format lists.
For Responsibilities: It's prose, not a list. So we put with the paragraph.
But we could also split into multiple sentences as separate
? The instruction: Use
for prose. So we can put the whole block as one
. That's fine.
Now Requirements: list items.
We need to keep exact phrasing: "ACTIVE and MAINTAINED “TOP SECRET” Federal or DoD security clearance". Keep quotes.
"THREE (3) or more years of experience in project / program support, task coordination, action coordination, administrative operations"
"TWO (2) or more years of experience supporting a U.S. Government client"
We should preserve the parentheses and spacing.
Now Qualifications list:
- ACTIVE “TS/SCI” Federal or DoD security clearance
- Bachelor’s Degree
- Prior Front Office support experience, particularly in a DoD or federally funded R&D environment
- Experience with Microsoft Office, Excel, Word, and PowerPoint
- Prior experience providing briefing coordination and support
- Prior experience in an Action Officer role
- Project Management Professional (PMP) certification
We need to keep the exact phrasing.
Now Benefits list: from "Benefits Include" list:
"Medical, Rx, Dental & Vision Insurance"
"Personal and Family Sick Time & Company Paid Holidays"
"Position may be eligible for a discretionary variable incentive bonus"
"Parental Leave and Adoption Assistance"
"401(k) Retirement Plan"
"Basic Life & Supplemental Life"
"Health Savings Account, Dental/Vision & Dependent Care Flexible Spending Accounts"
"Short-Term & Long-Term Disability"
"Student Loan PayDown"
"Tuition Reimbursement, Personal Development & Learning Opportunities"
"Skills Development & Certifications"
"Employee Referral Program"
"Corporate Sponsored Events & Community Outreach"
"Emergency Back-Up Childcare Program"
"Mobility Stipend"
We need to keep each as list item.
Now we need to strip boilerplate: The "About Guidehouse" section includes EEO etc. Remove.
Also remove lines like "Guidehouse offers a comprehensive, total rewards package that includes competitive compensation and a flexible benefits package that reflects our commitment to creating a diverse and supportive workplace." That's part of What We Offer intro before Benefits Include. That is substantive? It's a description of the benefits package. Should we keep it? It's part of What We Offer. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence as prose before the benefits list. However we need to decide where to put it. Could be part of Benefits section as a preamble
then
. That seems appropriate.
Thus Benefits section: Benefits
Guidehouse offers a comprehensive, total rewards package that includes competitive compensation and a flexible benefits package that reflects our commitment to creating a diverse and supportive workplace.
- ...
Now we need to ensure we don't include any other boilerplate like "About Guidehouse" etc.
Now check for any other substantive content: Travel Required Up to 10% and Clearance Required Active Secret appear at top near Job Family. That's metadata: Travel Required Up to 10% and Clearance Required Active Secret. Should we include that? It's not a heading but could be included in About the role or Responsibilities as a short note. The instruction: Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. Travel and clearance are minor metadata; we could fold them into a short
maybe under About the role or Responsibilities. However we already have a Respons
- for any list of duties/requirements/benefits, and
for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO, accommodation contact, etc. We need to keep the benefits list exactly as given. Let's extract content. **What You Will Do** (duties): "A Front Office Action Officer will provide onsite operational and project management support for our Defense Advanced Research Projects Agency (DARPA) client. They will work in a fast-paced and highly collaborative environment supporting and tracking office and agency actions and deliverables, as well as managing program development processes, scheduling meetings and managing leadership calendars, and maintain overall office timelines. Tasks also include providing briefing development support for office leadership in collaboration with the technical subject matter experts, internal and external engagement coordination and support, documentation review, and engagement with support services across multiple technical and administrative stakeholders. The Action Officer will work as a part of a multi-discipline team made up of technical subject matter experts, program and financial analysts, contract administrators, government partners, and government project managers supporting the advancement of the current state of the art in a wide range of technology areas." We can turn this into a prose paragraph (
) or maybe bullet list? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. This is prose, not a list. So we can put in
. However we could also break into bullet list for clarity but that would be inventing structure not present. Better to keep as prose. **What You Will Need** (requirements): - ACTIVE and MAINTAINED “TOP SECRET” Federal or DoD security clearance - THREE (3) or more years of experience in project / program support, task coordination, action coordination, administrative operations - TWO (2) or more years of experience supporting a U.S. Government client These are list items. Use
- .
**What Would Be Nice To Have** (nice-to-have):
- ACTIVE “TS/SCI” Federal or DoD security clearance
- Bachelor’s Degree
- Prior Front Office support experience, particularly in a DoD or federally funded R&D environment
- Experience with Microsoft Office, Excel, Word, and PowerPoint
- Prior experience providing briefing coordination and support
- Prior experience in an Action Officer role
- Project Management Professional (PMP) certification
These could go under Qualifications or Skills. The instruction: Use headings like Qualifications, Skills. We need to decide.
Qualifications could include education and certifications. Skills could include technical skills like Microsoft Office, briefing coordination, etc. But we can also put all nice-to-have under Qualifications. However we have both Requirements and Qualifications sections. Let's assign:
- Requirements: mandatory (clearance, years experience, US Gov client experience).
- Qualifications: education (Bachelor’s Degree), certifications (PMP), maybe also prior Front Office support experience (experience). But that's also experience.
- Skills: technical skills (Microsoft Office, briefing coordination, etc.) and maybe also prior Action Officer role.
But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one section called Qualifications (or Skills). However instruction says prefer a few substantive sections over many thin ones. So we could have:
- About the role (prose)
- Responsibilities (list)
- Requirements (list)
- Qualifications (list) (including education, certifications, preferred experience, skills)
- Benefits (list)
That's 5 sections.
But we also have "What You Will Do" which is responsibilities; we could label that as Responsibilities.
Thus:
About the role
maybe a short summary: The role is Front Office Action Officer supporting DARPA client etc. But we already have duties in Responsibilities. The About the role could be a brief overview: "A Front Office Action Officer will provide onsite operational and project management support for our Defense Advanced Research Projects Agency (DARPA) client." That's from the first sentence. However we must not repeat content? We can reuse but must preserve all substantive information; we can include it in About the role as a short summary, but then we would be duplicating content if we also list duties in Responsibilities. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid redundancy. However we need to include About the role section only if posting has real specific content for it. The posting does not have a separate "About the role" paragraph; the "What You Will Do" is essentially responsibilities. So we could treat "What You Will Do" as About the role (or Responsibilities). Since we need to pick headings, we can map "What You Will Do" to Responsibilities. Then we might not need About the role. But we need to include a section only when posting has real specific content for it. If we omit About the role, that's fine. Thus we can have: - Responsibilities (Responsibilities
) with the duties prose. - Requirements (Requirements
) list. - Qualifications (Qualifications
) list (nice-to-have). - Benefits (Benefits
) list. We could also add Skills if we want to separate technical skills, but that would be thin. Better to put all nice-to-have under Qualifications. Now we need to format lists. For Responsibilities: It's prose, not a list. So we putwith the paragraph. But we could also split into multiple sentences as separate
? The instruction: Use
for prose. So we can put the whole block as one
. That's fine. Now Requirements: list items. We need to keep exact phrasing: "ACTIVE and MAINTAINED “TOP SECRET” Federal or DoD security clearance". Keep quotes. "THREE (3) or more years of experience in project / program support, task coordination, action coordination, administrative operations" "TWO (2) or more years of experience supporting a U.S. Government client" We should preserve the parentheses and spacing. Now Qualifications list: - ACTIVE “TS/SCI” Federal or DoD security clearance - Bachelor’s Degree - Prior Front Office support experience, particularly in a DoD or federally funded R&D environment - Experience with Microsoft Office, Excel, Word, and PowerPoint - Prior experience providing briefing coordination and support - Prior experience in an Action Officer role - Project Management Professional (PMP) certification We need to keep the exact phrasing. Now Benefits list: from "Benefits Include" list: "Medical, Rx, Dental & Vision Insurance" "Personal and Family Sick Time & Company Paid Holidays" "Position may be eligible for a discretionary variable incentive bonus" "Parental Leave and Adoption Assistance" "401(k) Retirement Plan" "Basic Life & Supplemental Life" "Health Savings Account, Dental/Vision & Dependent Care Flexible Spending Accounts" "Short-Term & Long-Term Disability" "Student Loan PayDown" "Tuition Reimbursement, Personal Development & Learning Opportunities" "Skills Development & Certifications" "Employee Referral Program" "Corporate Sponsored Events & Community Outreach" "Emergency Back-Up Childcare Program" "Mobility Stipend" We need to keep each as list item. Now we need to strip boilerplate: The "About Guidehouse" section includes EEO etc. Remove. Also remove lines like "Guidehouse offers a comprehensive, total rewards package that includes competitive compensation and a flexible benefits package that reflects our commitment to creating a diverse and supportive workplace." That's part of What We Offer intro before Benefits Include. That is substantive? It's a description of the benefits package. Should we keep it? It's part of What We Offer. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence as prose before the benefits list. However we need to decide where to put it. Could be part of Benefits section as a preamble
then
- . That seems appropriate.
Thus Benefits section:
- ...
Benefits
Guidehouse offers a comprehensive, total rewards package that includes competitive compensation and a flexible benefits package that reflects our commitment to creating a diverse and supportive workplace.
or drop it. Travel and clearance are minor metadata; we could fold them into a short
maybe under About the role or Responsibilities. However we already have a Respons
- .
**What Would Be Nice To Have** (nice-to-have):
- ACTIVE “TS/SCI” Federal or DoD security clearance
- Bachelor’s Degree
- Prior Front Office support experience, particularly in a DoD or federally funded R&D environment
- Experience with Microsoft Office, Excel, Word, and PowerPoint
- Prior experience providing briefing coordination and support
- Prior experience in an Action Officer role
- Project Management Professional (PMP) certification
These could go under Qualifications or Skills. The instruction: Use headings like Qualifications, Skills. We need to decide.
Qualifications could include education and certifications. Skills could include technical skills like Microsoft Office, briefing coordination, etc. But we can also put all nice-to-have under Qualifications. However we have both Requirements and Qualifications sections. Let's assign:
- Requirements: mandatory (clearance, years experience, US Gov client experience).
- Qualifications: education (Bachelor’s Degree), certifications (PMP), maybe also prior Front Office support experience (experience). But that's also experience.
- Skills: technical skills (Microsoft Office, briefing coordination, etc.) and maybe also prior Action Officer role.
But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one section called Qualifications (or Skills). However instruction says prefer a few substantive sections over many thin ones. So we could have:
- About the role (prose)
- Responsibilities (list)
- Requirements (list)
- Qualifications (list) (including education, certifications, preferred experience, skills)
- Benefits (list)
That's 5 sections.
But we also have "What You Will Do" which is responsibilities; we could label that as Responsibilities.
Thus:
- for any list of duties/requirements/benefits, and