Experienced Professional, Project Accounting
WSP in the U.S. · Arlington, VA · 4 wk ago
AccountingFull-time
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: About the role? There's a paragraph at start: "This Opportunity WSP is searching for an Experienced Professional, Project Accounting in the United States ...". That could be "About the role". Also there is "Responsibilities" section with many bullet-like sentences. There's "Qualifications" with Required Qualifications and Preferred Qualifications. There's "Benefits" with description. There's no explicit Pay or specific Pay or Schedule info. So we should not include Pay or Schedule sections. Also maybe "Skills" could be derived from qualifications but we have no separate skills section; we could combine into Qualifications or maybe we can create a Skills section if there is explicit skill list: proficiency with MS Excel etc. But the instruction: Prefer a few substantive sections over many thin ones. We could include Skills as part of Qualifications, but we could also make a Skills section if there is explicit list. The qualifications list includes many skills: analytical mindset, interpersonal skills, self-leadership, ability to learn new techniques, proficiency with technical writing, office automation and accounting software, technology, math principles, spreadsheets, MS Excel, pivot tables, formulas, data format/sort/filter, VLOOKUP, predictive models, and tools. Critical thinking, problem-solving, awareness of WSP handbook, etc. That could be a Skills section. However we already have Qualifications section containing required and preferred qualifications. Might be okay to keep Qualifications only. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples; we can choose which to include. We should include sections that have real content. We have About the role (intro), Responsibilities, Qualifications, Benefits. Possibly also Requirements? The Qualifications section includes required qualifications; we could rename that to Requirements? But they gave both Requirements and Qualifications as possible headings. The posting has "Qualifications Who You Are Required Qualifications". So we could use "Qualifications" heading. Could also include "Requirements" as a subsection? Better to just have Qualifications.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions. The posting includes "Are you ready to get started?" and some EEO statement; we should remove those.
We need to preserve all substantive information. So we need to include all responsibilities sentences, qualifications details, benefits description, about the role paragraph.
We need to format using
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: About the role? There's a paragraph at start: "This Opportunity WSP is searching for an Experienced Professional, Project Accounting in the United States ...". That could be "About the role". Also there is "Responsibilities" section with many bullet-like sentences. There's "Qualifications" with Required Qualifications and Preferred Qualifications. There's "Benefits" with description. There's no explicit Pay or specific Pay or Schedule info. So we should not include Pay or Schedule sections. Also maybe "Skills" could be derived from qualifications but we have no separate skills section; we could combine into Qualifications or maybe we can create a Skills section if there is explicit skill list: proficiency with MS Excel etc. But the instruction: Prefer a few substantive sections over many thin ones. We could include Skills as part of Qualifications, but we could also make a Skills section if there is explicit list. The qualifications list includes many skills: analytical mindset, interpersonal skills, self-leadership, ability to learn new techniques, proficiency with technical writing, office automation and accounting software, technology, math principles, spreadsheets, MS Excel, pivot tables, formulas, data format/sort/filter, VLOOKUP, predictive models, and tools. Critical thinking, problem-solving, awareness of WSP handbook, etc. That could be a Skills section. However we already have Qualifications section containing required and preferred qualifications. Might be okay to keep Qualifications only. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples; we can choose which to include. We should include sections that have real content. We have About the role (intro), Responsibilities, Qualifications, Benefits. Possibly also Requirements? The Qualifications section includes required qualifications; we could rename that to Requirements? But they gave both Requirements and Qualifications as possible headings. The posting has "Qualifications Who You Are Required Qualifications". So we could use "Qualifications" heading. Could also include "Requirements" as a subsection? Better to just have Qualifications.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove application instructions. The posting includes "Are you ready to get started?" and some EEO statement; we should remove those.
We need to preserve all substantive information. So we need to include all responsibilities sentences, qualifications details, benefits description, about the role paragraph.
We need to format using for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide what constitutes a list. The responsibilities are many sentences; we could turn each responsibility into a
- within a
. Similarly, qualifications could be a list. Benefits could be a list.
We must not invent or summarize away detail. So we need to keep all details.
Let's extract the substantive content.
First, intro/about the role:
"This Opportunity WSP is searching for an Experienced Professional, Project Accounting in the United States This position is contingent upon the ability to obtain and maintain a national security clearance. The ideal candidate will be providing accounting and financial specialist support to one or more Project Managers and project teams. Responsibilities include developing project work breakdown structures, project budgets, margin analysis, and creating associated funding in Oracle for larger and more complex projects. Additional duties include evaluating project charges, completing cost transfers, maintaining accurate project data in Oracle, generating robust project accounting reports, and partnering with project leadership to develop corrective strategies for problem projects. You will also collaborate closely with Billing and Project Managers on pre-billing reviews, cost estimates, and invoicing. This position supports the delivery of future-ready solutions to clients while maintaining high standards of quality and financial stewardship."
Note there is a typo: "in t he United States". We'll keep as is? Probably we should keep original text but maybe fix spacing? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say we must keep typos exactly; but we should not change meaning. Fixing a space is minor but could be considered altering. Safer to keep as is? The original: "in t he United States". That's weird. I'd keep exactly as given? Might be considered a typo but it's part of the posting. I'd keep it as is to preserve. However readability may suffer but it's okay.
Now Responsibilities section: The posting has a heading "Responsibilities Your Impact". Then a paragraph: "For assigned project(s), manage and analyze the collection, recording, and allocating of project costs and revenue, ensuring accurate project profit and loss calculations, and communicating project financial performance and profitability to project/program management." Then many sentences each starting with a verb. We'll treat each as a list item.
Let's list them:
- For assigned project(s), manage and analyze the collection, recording, and allocating of project costs and revenue, ensuring accurate project profit and loss calculations, and communicating project financial performance and profitability to project/program management.
- Responsible for lifecycle project accounting from creating project accounts in Oracle, to tracking projects and project budget, validating invoicing, project close-out, and reconciling overall project payables and receivables to project budgets.
- Perform detailed and involved accounting tasks related to managing project contract, billing events and billing transaction exceptions revenue for medium-sized and/or moderate-level complex projects.
- Partner with the Project Manager and project team to establish the project budget, updating budgets, and making project accounting recommendations as needed when contract modifications or budget changes arise.
- Generate project financial reports, evaluating the reports for any items, including labor breakage, that need to be escalated for review by the Project Manager as necessary.
- Authorize access to project accounts, and the transfer of expenses into and out of project-related accounts in compliance with established accounting practices and guidelines.
- Maintain quality control standards and procedures for generating accurate and precise project-related financial records using Oracle, spreadsheets, and software.
- For assigned projects, apply learned accounting expertise relating to project resources, labor and expenses, investigating project variances and submitting variance reports to management.
- Verify contract and change order characteristics for projects that are medium-sized and/or of a moderate-level of complexity, including reading and interpreting contract language, method of compensation, modifications, purchase orders, and subcontract/consultant terms.
- Monitor key indicators for managing and analyzing problem projects, keeping project managers and/or project accounting manager informed on any noted concerns.
- Responsible for ensuring draft invoices from billing are accurate based on the contract requirements agreed upon with the client; identifying any needed corrections, obtains Project Manager documentation and signature.
- Finalizes the invoice approval with the Project Manager/billing team and submits the invoice to the client.
- Subcontract management and coordination with Contract Administrators. This includes evaluating subconsultant invoice submittals for accuracy, establish and maintain purchase orders for subconsultants, and requests and follows up on subcontractor payment requests with Accounts Payable.
- Identify and record unpaid contract billings, following up on any delinquent accounts receivable and/or unbilled costs.
- Respond to requests for more detail from clients, investigate all project expenses not billed to clients, and review and approve all project-related billings to clients.
- Attend project-related meetings to inform the team regarding the current status of project financials, articulating problem projects and following up on any identified actions as discussed.
- Create and submit government reports related to projects.
- Compile information for review by a more Senior Consultant prior to submitting for internal and external auditors as required.
- Interact with regulatory agencies, subcontractors, and clients in a confident and professional manner.
- Remain current in latest project accounting principles and subject matter.
- Exercise responsible and ethical decision-making regarding company funds, resources and conduct, and adhere to WSP’s Code of Conduct and related policies and procedures.
- Perform additional responsibilities as required by business needs.
Now Qualifications section: There's "Qualifications Who You Are Required Qualifications" then bullet-like sentences.
Let's extract:
Required Qualifications:
- Bachelor’s Degree in Accounting , Business, or closely-related discipline (or demonstrated proven equivalent experience).
- 3 to 5 years of relevant post-education experience in accounting, project contracts and change management documents.
- Working knowledge of project accounting principles, practices, and methods and their application to project work-related issues.
- Analytical mindset with an ability to exercise sound independent judgement in evaluating situations and making decisions with financial implications to the company.
- Ability to initiate and coordinate efforts with various stakeholders around contract and project requirements.
- Effective/Strong Capable interpersonal and communication skills when interacting with others, expressing ideas effectively and professionally to an accounting and non-accounting audience.
- Effective self-leadership with attention to detail, results orientation, and managing multiple priorities in a dynamic work environment.
- Ability to learn new techniques, perform multiple tasks simultaneously, follow instruction, work independently, and comply with company policies.
- Proficiency with technical writing, office automation and accounting software, technology, math principles, spreadsheets, MS Excel, pivot tables, formulas, data format/sort/filter, VLOOKUP, predictive models, and tools.
- Critical thinking and problem-solving skills required to apply learned subject matter and technical knowledge to reach conclusions from data collation, documentation, statistical analysis, and arriving at the most effective, economical, and logical solution.
- Awareness of and adherence to WSP USA’s Project Delivery Handbook.
- Proven track record of upholding workplace safety and ability to abide by WSP’s health, safety and drug/alcohol and harassment policies.
- This is a professional role and as such work deadlines and work hours may extend beyond a typical workday.
- Occasional travel may be required depending on project-specific requirements.
- Due to client/project requirements, US Citizenship is required.
- Ability to obtain and maintain a US Government issued Secret level Security Clearance.
Preferred Qualifications:
- Familiarity with Oracle preferred (but not required).
Now Benefits section: "WSP Benefits: WSP provides a comprehensive suite of benefits focused on a providing health and financial stability throughout the employee’s career. These benefits include coverage related to medical, dental, vision, disability, and life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; and paid time off for purposes of bereavement, voting, and/or attendance at naturalization proceedings."
Also later: "WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career." This is somewhat duplicated; we should preserve all substantive info but avoid duplication? The instruction: Remove duplicated lines. So we need to deduplicate. The second sentence repeats similar benefits; we can combine or keep one. We'll keep the first benefits paragraph and maybe note flexible workplace model as additional info. The second sentence also mentions flexible and agile workplace model. That's substantive not in first. So we should include that as part of Benefits section.
Thus Benefits content:
- WSP provides a comprehensive suite of benefits focused on providing health and financial stability throughout the employee’s career. These benefits include coverage related to medical, dental, vision, disability, and life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; and paid time off for purposes of bereavement, voting, and/or attendance at naturalization proceedings.
- WSP provides a flexible and agile workplace model while meeting client needs.
We could make each as list items.
Now About the role: we have the intro paragraph. Could also include "About WSP" section? There's a paragraph about WSP USA description. That is substantive. Should we include as a section? Possibly "About WSP" but not in the list of headings examples; but we could treat as "About the role" already includes some. However there is a distinct "About WSP" paragraph
- for any list of duties/requirements/benefits, and
for prose. We need to decide what constitutes a list. The responsibilities are many sentences; we could turn each responsibility into a
- within a
- . Similarly, qualifications could be a list. Benefits could be a list.
We must not invent or summarize away detail. So we need to keep all details.
Let's extract the substantive content.
First, intro/about the role:
"This Opportunity WSP is searching for an Experienced Professional, Project Accounting in the United States This position is contingent upon the ability to obtain and maintain a national security clearance. The ideal candidate will be providing accounting and financial specialist support to one or more Project Managers and project teams. Responsibilities include developing project work breakdown structures, project budgets, margin analysis, and creating associated funding in Oracle for larger and more complex projects. Additional duties include evaluating project charges, completing cost transfers, maintaining accurate project data in Oracle, generating robust project accounting reports, and partnering with project leadership to develop corrective strategies for problem projects. You will also collaborate closely with Billing and Project Managers on pre-billing reviews, cost estimates, and invoicing. This position supports the delivery of future-ready solutions to clients while maintaining high standards of quality and financial stewardship."
Note there is a typo: "in t he United States". We'll keep as is? Probably we should keep original text but maybe fix spacing? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't say we must keep typos exactly; but we should not change meaning. Fixing a space is minor but could be considered altering. Safer to keep as is? The original: "in t he United States". That's weird. I'd keep exactly as given? Might be considered a typo but it's part of the posting. I'd keep it as is to preserve. However readability may suffer but it's okay.
Now Responsibilities section: The posting has a heading "Responsibilities Your Impact". Then a paragraph: "For assigned project(s), manage and analyze the collection, recording, and allocating of project costs and revenue, ensuring accurate project profit and loss calculations, and communicating project financial performance and profitability to project/program management." Then many sentences each starting with a verb. We'll treat each as a list item.
Let's list them:
- For assigned project(s), manage and analyze the collection, recording, and allocating of project costs and revenue, ensuring accurate project profit and loss calculations, and communicating project financial performance and profitability to project/program management.
- Responsible for lifecycle project accounting from creating project accounts in Oracle, to tracking projects and project budget, validating invoicing, project close-out, and reconciling overall project payables and receivables to project budgets.
- Perform detailed and involved accounting tasks related to managing project contract, billing events and billing transaction exceptions revenue for medium-sized and/or moderate-level complex projects.
- Partner with the Project Manager and project team to establish the project budget, updating budgets, and making project accounting recommendations as needed when contract modifications or budget changes arise.
- Generate project financial reports, evaluating the reports for any items, including labor breakage, that need to be escalated for review by the Project Manager as necessary.
- Authorize access to project accounts, and the transfer of expenses into and out of project-related accounts in compliance with established accounting practices and guidelines.
- Maintain quality control standards and procedures for generating accurate and precise project-related financial records using Oracle, spreadsheets, and software.
- For assigned projects, apply learned accounting expertise relating to project resources, labor and expenses, investigating project variances and submitting variance reports to management.
- Verify contract and change order characteristics for projects that are medium-sized and/or of a moderate-level of complexity, including reading and interpreting contract language, method of compensation, modifications, purchase orders, and subcontract/consultant terms.
- Monitor key indicators for managing and analyzing problem projects, keeping project managers and/or project accounting manager informed on any noted concerns.
- Responsible for ensuring draft invoices from billing are accurate based on the contract requirements agreed upon with the client; identifying any needed corrections, obtains Project Manager documentation and signature.
- Finalizes the invoice approval with the Project Manager/billing team and submits the invoice to the client.
- Subcontract management and coordination with Contract Administrators. This includes evaluating subconsultant invoice submittals for accuracy, establish and maintain purchase orders for subconsultants, and requests and follows up on subcontractor payment requests with Accounts Payable.
- Identify and record unpaid contract billings, following up on any delinquent accounts receivable and/or unbilled costs.
- Respond to requests for more detail from clients, investigate all project expenses not billed to clients, and review and approve all project-related billings to clients.
- Attend project-related meetings to inform the team regarding the current status of project financials, articulating problem projects and following up on any identified actions as discussed.
- Create and submit government reports related to projects.
- Compile information for review by a more Senior Consultant prior to submitting for internal and external auditors as required.
- Interact with regulatory agencies, subcontractors, and clients in a confident and professional manner.
- Remain current in latest project accounting principles and subject matter.
- Exercise responsible and ethical decision-making regarding company funds, resources and conduct, and adhere to WSP’s Code of Conduct and related policies and procedures.
- Perform additional responsibilities as required by business needs.
Now Qualifications section: There's "Qualifications Who You Are Required Qualifications" then bullet-like sentences.
Let's extract:
Required Qualifications:
- Bachelor’s Degree in Accounting , Business, or closely-related discipline (or demonstrated proven equivalent experience).
- 3 to 5 years of relevant post-education experience in accounting, project contracts and change management documents.
- Working knowledge of project accounting principles, practices, and methods and their application to project work-related issues.
- Analytical mindset with an ability to exercise sound independent judgement in evaluating situations and making decisions with financial implications to the company.
- Ability to initiate and coordinate efforts with various stakeholders around contract and project requirements.
- Effective/Strong Capable interpersonal and communication skills when interacting with others, expressing ideas effectively and professionally to an accounting and non-accounting audience.
- Effective self-leadership with attention to detail, results orientation, and managing multiple priorities in a dynamic work environment.
- Ability to learn new techniques, perform multiple tasks simultaneously, follow instruction, work independently, and comply with company policies.
- Proficiency with technical writing, office automation and accounting software, technology, math principles, spreadsheets, MS Excel, pivot tables, formulas, data format/sort/filter, VLOOKUP, predictive models, and tools.
- Critical thinking and problem-solving skills required to apply learned subject matter and technical knowledge to reach conclusions from data collation, documentation, statistical analysis, and arriving at the most effective, economical, and logical solution.
- Awareness of and adherence to WSP USA’s Project Delivery Handbook.
- Proven track record of upholding workplace safety and ability to abide by WSP’s health, safety and drug/alcohol and harassment policies.
- This is a professional role and as such work deadlines and work hours may extend beyond a typical workday.
- Occasional travel may be required depending on project-specific requirements.
- Due to client/project requirements, US Citizenship is required.
- Ability to obtain and maintain a US Government issued Secret level Security Clearance.
Preferred Qualifications:
- Familiarity with Oracle preferred (but not required).
Now Benefits section: "WSP Benefits: WSP provides a comprehensive suite of benefits focused on a providing health and financial stability throughout the employee’s career. These benefits include coverage related to medical, dental, vision, disability, and life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; and paid time off for purposes of bereavement, voting, and/or attendance at naturalization proceedings."
Also later: "WSP provides a flexible and agile workplace model while meeting client needs. Employees are also afforded a comprehensive suite of benefits including medical, dental, vision, disability, life, and retirement savings focused on providing health and financial stability throughout the employee’s career." This is somewhat duplicated; we should preserve all substantive info but avoid duplication? The instruction: Remove duplicated lines. So we need to deduplicate. The second sentence repeats similar benefits; we can combine or keep one. We'll keep the first benefits paragraph and maybe note flexible workplace model as additional info. The second sentence also mentions flexible and agile workplace model. That's substantive not in first. So we should include that as part of Benefits section.
Thus Benefits content:
- WSP provides a comprehensive suite of benefits focused on providing health and financial stability throughout the employee’s career. These benefits include coverage related to medical, dental, vision, disability, and life; retirement savings; paid sick leave; paid vacation (or other personal time); paid parental leave; and paid time off for purposes of bereavement, voting, and/or attendance at naturalization proceedings.
- WSP provides a flexible and agile workplace model while meeting client needs.
We could make each as list items.
Now About the role: we have the intro paragraph. Could also include "About WSP" section? There's a paragraph about WSP USA description. That is substantive. Should we include as a section? Possibly "About WSP" but not in the list of headings examples; but we could treat as "About the role" already includes some. However there is a distinct "About WSP" paragraph