Government Accounting Analyst
for section headings, - for lists,
for prose. No job title heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Keep substantive info.
We need to parse the posting.
Content:
- Title: Government Accounting Analyst | Tyson Corner - On Site (ignore as heading)
- Intro paragraph: "Are you an accounting professional looking to grow your career in government contracting, billing, and compliance? We’re seeking a Government Accounting Analyst to support billing operations, corporate accounting, and contract compliance activities in a dynamic and growth-focused environment."
- Next paragraph: "This is an excellent opportunity for someone who wants to build deeper expertise in government contract accounting, indirect rates, incurred cost submissions, DCAA audits, and contract closeout activities while partnering with Accounting, Contracts, and Program Management teams."
- Section "Why This Role Stands Out": heading? It's a heading in posting. Should we include? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. "Why This Role Stands Out" could be considered "About the role" or maybe we treat as a section heading. But they gave examples; we can use any appropriate heading. Likely we should use headings like "About the role", "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to include a section only when posting has real specific content.
We have content about responsibilities: "Key Responsibilities" with sub-sections: Billing & Contract Administration, Corporate Accounting, Government Contract Accounting & Compliance. Under each bullet list.
We have qualifications: "Required Qualifications" and "Preferred Qualifications". Also maybe "Skills" could be derived from required qualifications (Excel skills, analytical, etc). But we can treat "Required Qualifications" as a section heading (maybe "Qualifications") and list items.
We have "Preferred Qualifications" maybe also under Qualifications or separate? Could combine.
We have benefits: later in boilerplate: "Benefits are available to contract/temporary professionals, including medical, vision, dental, and life and disability insurance. Hired contract/temporary professionals are also eligible to enroll in our company 401(k) plan." That's substantive benefits info. So we should include a Benefits section.
Pay: not mentioned. So we should not include Pay section.
Schedule: not mentioned (maybe On Site? The title says Tyson Corner - On Site. That indicates location and possibly schedule (on-site). Could treat as Schedule? But they said only include if posting actually states them. The posting says "Tyson Corner - On Site". That indicates work location and that it's on-site. Could be considered schedule? Not exactly schedule (like full-time, part-time). Might be considered location. Since they didn't ask for location heading, we could incorporate into a short paragraph maybe under About the role. But we shouldn't invent a Schedule heading if not explicit about hours. So we skip Schedule.
We also have info about Robert Half etc. That's boilerplate; we should remove navigation/legal/EEO etc. The benefits paragraph is part of Robert Half boilerplate but still substantive about benefits. We'll keep that.
We need to remove duplicated lines, application instructions like "Apply directly to this post for immediate consideration. Direct additional questions to Lee Chernett, VP at Robert Half Finance & Accounting, via LinkedIn". Also Robert Half description etc. Those are boilerplate; we should remove.
We need to preserve ALL substantive information; do not invent or summarize away detail.
Thus we need to extract substantive content:
- Intro paragraphs (two paragraphs) about role and opportunity.
- Why This Role Stands Out paragraph.
- Responsibilities: three categories with bullet points.
- Required Qualifications: list.
- Preferred Qualifications: list.
- Benefits: medical, vision, dental, life and disability insurance, 401(k) plan.
Potentially also mention that it's contract/temporary professionals? The benefits are for contract/temporary professionals. That's substantive.
We should not include the Robert Half promotional text about being world's first etc. That's boilerplate.
We need to format with headings.
Potential sections:
- About the role (could combine intro and why this role stands out). But we have separate "Why This Role Stands Out" heading; we could treat that as About the role.
Better: Use About the role
containing the intro paragraphs and the "Why This Role Stands Out" paragraph.
Then Responsibilities
with subheadings? The instruction only says use for section headings; not forbid using or other? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use for each main section and within responsibilities we can use
for subheadings maybe bold? But we can't use markdown. We could embed subheadings as within . But maybe better to just list all responsibilities under a single
with items that include the subcategory text. However we need to preserve structure; but we can incorporate subcategory as part of list item text.
Simplify: Under Responsibilities, we can have a with items like:
- Billing & Contract Administration: Prepare and review customer invoices for Cost-Plus, Time & Materials (T& M), and fixed-price contracts; Validate labor, subcontractor, and other direct costs for billing accuracy and contract compliance; Perform billing reconciliations and analyze unbilled receivables; Assist with final invoices, final vouchers, and contract closeout documentation; Monitor contract funding limits and help resolve billing discrepancies; Partner with Contracts and Program Management to ensure timely, accurate billing.
- Corporate Accounting: Support month-end and year-end close activities; Prepare journal entries, account reconciliations, and supporting schedules; Assist with balance sheet analyses and financial reporting; Support external audits and annual reporting requirements; Maintain accounting records in line with internal controls and company policies; Participate in process improvement initiatives across accounting and finance.
- Government Contract Accounting & Compliance: Assist with preparation of annual Incurred Cost Submissions (ICS); Support indirect rate calculations, reconciliations, and true-up analyses; Apply FAR Part 31 cost principles in reviewing allowable and unallowable costs; Prepare schedules and supporting documentation for DCAA audits and compliance reviews; Assist with final indirect rate settlements and contract closeout activities; Help maintain government accounting policies, procedures, and controls.
That preserves details.
Then Qualifications: we can have Qualifications
with two sub-sections maybe Required and Preferred. Could use for intro then
for each.
We could do:
Required Qualifications
- Bachelor’s degree in Accounting, Finance, or related field
- 2–5 years of accounting experience in government contracting, project accounting, contract billing, public accounting, or corporate accounting
- Strong Excel skills, including pivot tables, lookups, and data analysis
- Strong analytical, organizational, and communication skills
- Ability to manage multiple priorities and work effectively in a collaborative environment
Preferred Qualifications
- Knowledge of government contracting principles, FAR, DCAA, and federal contract compliance
- Experience with Cost-Plus and/or T& M billing, incurred cost submissions, indirect rate calculations, or contract closeout
- Experience with account reconciliations, month-end close, and financial reporting
- CPA or other accounting certification is a plus
But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list Required Qualifications or Preferred Qualifications as examples, but we can still use for those headings; it's still a section heading. It's okay.
Alternatively combine into Qualifications with subheadings
Required:
etc. But simpler to use separate headings.
Benefits: Benefits
- Medical, vision, dental, and life and disability insurance (available to contract/temporary professionals)
- Eligibility to enroll in company 401(k) plan (for hired contract/temporary professionals)
We need to ensure we don't include boilerplate like "Visit roberthalf.gobenefits.net for more information." That's a link; maybe we can keep as part of benefits? It's a reference for more info; but it's still substantive? It's a URL; could be considered boilerplate but it's providing info. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URL is not necessarily boilerplate; it's a reference for benefits info. Might be okay to keep. But we could drop it as it's not essential detail; but we should preserve ALL substantive information. The URL is substantive info about where to get more info. I'd keep it as a maybe.
But we should not include the copyright line, EEO statement, etc.
Thus final HTML fragment:
About the role
Are you an accounting professional looking to grow your career in government contracting, billing, and compliance? We’re seeking a Government Accounting Analyst to support billing operations, corporate accounting, and contract compliance activities in a dynamic and growth-focused environment.
This is an excellent opportunity for someone who wants to build deeper expertise in government contract accounting, indirect rates, incurred cost submissions, DCAA audits, and contract closeout activities while partnering with Accounting, Contracts, and Program Management teams.
Why This Role Stands Out: This position offers strong career development for professionals who want hands-on exposure across billing, corporate accounting, and government contract compliance. You’ll gain valuable experience supporting the financial operations of a growing government contractor and expand your knowledge of the full contract lifecycle with an organization that has a strong history of developing their people and promoting from within.
Responsibilities
- Billing & Contract Administration: Prepare and review customer invoices for Cost-Plus, Time & Materials (T& M), and fixed-price contracts; Validate labor, subcontractor, and other direct costs for billing accuracy and contract compliance; Perform billing reconciliations and analyze unbilled receivables; Assist with final invoices, final vouchers, and contract closeout documentation; Monitor contract funding limits and help resolve billing discrepancies; Partner with Contracts and Program Management to ensure timely, accurate billing.
- Corporate Accounting: Support month-end and year-end close activities; Prepare journal entries, account reconciliations, and supporting schedules; Assist with balance sheet analyses and financial reporting; Support external audits and annual reporting requirements; Maintain accounting records in line with internal controls and company policies; Participate in process improvement initiatives across accounting and finance.
- Government Contract Accounting & Compliance: Assist with preparation of annual Incurred Cost Submissions (ICS); Support indirect rate calculations, reconciliations, and true-up analyses; Apply FAR Part 31 cost principles in reviewing allowable and unallowable costs; Prepare schedules and supporting documentation for DCAA audits and compliance reviews; Assist with final indirect rate settlements and contract closeout activities; Help maintain government accounting policies, procedures, and controls.
Required Qualifications
- Bachelor’s degree in Accounting, Finance, or related field
for prose. No job title heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Keep substantive info. We need to parse the posting. Content: - Title: Government Accounting Analyst | Tyson Corner - On Site (ignore as heading) - Intro paragraph: "Are you an accounting professional looking to grow your career in government contracting, billing, and compliance? We’re seeking a Government Accounting Analyst to support billing operations, corporate accounting, and contract compliance activities in a dynamic and growth-focused environment." - Next paragraph: "This is an excellent opportunity for someone who wants to build deeper expertise in government contract accounting, indirect rates, incurred cost submissions, DCAA audits, and contract closeout activities while partnering with Accounting, Contracts, and Program Management teams." - Section "Why This Role Stands Out": heading? It's a heading in posting. Should we include? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. "Why This Role Stands Out" could be considered "About the role" or maybe we treat as a section heading. But they gave examples; we can use any appropriate heading. Likely we should use headings like "About the role", "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to include a section only when posting has real specific content.
We have content about responsibilities: "Key Responsibilities" with sub-sections: Billing & Contract Administration, Corporate Accounting, Government Contract Accounting & Compliance. Under each bullet list.
We have qualifications: "Required Qualifications" and "Preferred Qualifications". Also maybe "Skills" could be derived from required qualifications (Excel skills, analytical, etc). But we can treat "Required Qualifications" as a section heading (maybe "Qualifications") and list items.
We have "Preferred Qualifications" maybe also under Qualifications or separate? Could combine.
We have benefits: later in boilerplate: "Benefits are available to contract/temporary professionals, including medical, vision, dental, and life and disability insurance. Hired contract/temporary professionals are also eligible to enroll in our company 401(k) plan." That's substantive benefits info. So we should include a Benefits section.
Pay: not mentioned. So we should not include Pay section.
Schedule: not mentioned (maybe On Site? The title says Tyson Corner - On Site. That indicates location and possibly schedule (on-site). Could treat as Schedule? But they said only include if posting actually states them. The posting says "Tyson Corner - On Site". That indicates work location and that it's on-site. Could be considered schedule? Not exactly schedule (like full-time, part-time). Might be considered location. Since they didn't ask for location heading, we could incorporate into a short paragraph maybe under About the role. But we shouldn't invent a Schedule heading if not explicit about hours. So we skip Schedule.
We also have info about Robert Half etc. That's boilerplate; we should remove navigation/legal/EEO etc. The benefits paragraph is part of Robert Half boilerplate but still substantive about benefits. We'll keep that.
We need to remove duplicated lines, application instructions like "Apply directly to this post for immediate consideration. Direct additional questions to Lee Chernett, VP at Robert Half Finance & Accounting, via LinkedIn". Also Robert Half description etc. Those are boilerplate; we should remove.
We need to preserve ALL substantive information; do not invent or summarize away detail.
Thus we need to extract substantive content:
- Intro paragraphs (two paragraphs) about role and opportunity.
- Why This Role Stands Out paragraph.
- Responsibilities: three categories with bullet points.
- Required Qualifications: list.
- Preferred Qualifications: list.
- Benefits: medical, vision, dental, life and disability insurance, 401(k) plan.
Potentially also mention that it's contract/temporary professionals? The benefits are for contract/temporary professionals. That's substantive.
We should not include the Robert Half promotional text about being world's first etc. That's boilerplate.
We need to format with headings.
Potential sections:
- About the role (could combine intro and why this role stands out). But we have separate "Why This Role Stands Out" heading; we could treat that as About the role.
Better: Use About the role
containing the intro paragraphs and the "Why This Role Stands Out" paragraph.
Then Responsibilities
with subheadings? The instruction only says use for section headings; not forbid using or other? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use for each main section and within responsibilities we can use
About the role
containing the intro paragraphs and the "Why This Role Stands Out" paragraph. ThenResponsibilities
with subheadings? The instruction only says use for section headings; not forbid using or other? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use for each main section and within responsibilities we can use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can just use for each main section and within responsibilities we can use
for subheadings maybe bold? But we can't use markdown. We could embed subheadings as within . But maybe better to just list all responsibilities under a single for intro then Required: maybe.
But we should not include the copyright line, EEO statement, etc.
Thus final HTML fragment:
Are you an accounting professional looking to grow your career in government contracting, billing, and compliance? We’re seeking a Government Accounting Analyst to support billing operations, corporate accounting, and contract compliance activities in a dynamic and growth-focused environment. This is an excellent opportunity for someone who wants to build deeper expertise in government contract accounting, indirect rates, incurred cost submissions, DCAA audits, and contract closeout activities while partnering with Accounting, Contracts, and Program Management teams. Why This Role Stands Out: This position offers strong career development for professionals who want hands-on exposure across billing, corporate accounting, and government contract compliance. You’ll gain valuable experience supporting the financial operations of a growing government contractor and expand your knowledge of the full contract lifecycle with an organization that has a strong history of developing their people and promoting from within. with items that include the subcategory text. However we need to preserve structure; but we can incorporate subcategory as part of list item text.
Simplify: Under Responsibilities, we can have a
with items like:
- Billing & Contract Administration: Prepare and review customer invoices for Cost-Plus, Time & Materials (T& M), and fixed-price contracts; Validate labor, subcontractor, and other direct costs for billing accuracy and contract compliance; Perform billing reconciliations and analyze unbilled receivables; Assist with final invoices, final vouchers, and contract closeout documentation; Monitor contract funding limits and help resolve billing discrepancies; Partner with Contracts and Program Management to ensure timely, accurate billing.
- Corporate Accounting: Support month-end and year-end close activities; Prepare journal entries, account reconciliations, and supporting schedules; Assist with balance sheet analyses and financial reporting; Support external audits and annual reporting requirements; Maintain accounting records in line with internal controls and company policies; Participate in process improvement initiatives across accounting and finance.
- Government Contract Accounting & Compliance: Assist with preparation of annual Incurred Cost Submissions (ICS); Support indirect rate calculations, reconciliations, and true-up analyses; Apply FAR Part 31 cost principles in reviewing allowable and unallowable costs; Prepare schedules and supporting documentation for DCAA audits and compliance reviews; Assist with final indirect rate settlements and contract closeout activities; Help maintain government accounting policies, procedures, and controls.
That preserves details.
Then Qualifications: we can have
Qualifications
with two sub-sections maybe Required and Preferred. Could use for each.
We could do:
Required Qualifications
Preferred Qualifications
But the instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list Required Qualifications or Preferred Qualifications as examples, but we can still use
for those headings; it's still a section heading. It's okay.
Alternatively combine into Qualifications with subheadings
Benefits
We need to ensure we don't include boilerplate like "Visit roberthalf.gobenefits.net for more information." That's a link; maybe we can keep as part of benefits? It's a reference for more info; but it's still substantive? It's a URL; could be considered boilerplate but it's providing info. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The URL is not necessarily boilerplate; it's a reference for benefits info. Might be okay to keep. But we could drop it as it's not essential detail; but we should preserve ALL substantive information. The URL is substantive info about where to get more info. I'd keep it as a About the role
Responsibilities
Required Qualifications