Project Accountant I

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. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, duplicated lines, application instructions, EEO etc. Must not create sections with filler like "commensurate with experience". Must only include sections where posting has real specific content. Let's parse the posting. First paragraph: "As the Project Accountant, you will play a key role..." This is description of role. Could be "About the role". So we can have

About the role

with paragraph(s) summarizing that description. Then "What You Bring:" with Must Haves and Nice To Haves. That's qualifications/requirements/skills. We need to split into sections: Requirements (must haves), Qualifications (maybe same), Skills (maybe separate). But we need to follow instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections to include based on content. We have responsibilities: "What You Will Do:" list of duties. That's Responsibilities. We have "What We Offer:" benefits. That's Benefits. We have pay range: "The rate for this position generally ranges between $60,000 to 72,000 annually." That's Pay. Schedule? Not mentioned explicitly. There's mention of "Regular Full-Time & Part-Time Employees Working 30+ Hours/Week" and "Additional benefits available to FT Employees Working 40+ Hours/Week". That implies schedule info: full-time 30+ hours, part-time etc. Could be considered schedule. But we should only include Schedule if posting actually states them. It does mention hours expectations. So we could include Schedule section with that info. We must not include boilerplate like EEO, etc. Must remove those lines. We must not include duplicated lines. We must not include application instructions. We must not include "What Does It Look Like Working Here?" (culture) maybe could be considered part of About the role or maybe separate but not a prescribed heading. Since only allowed headings are those list, we should not create extra headings. Could we incorporate that paragraph into About the role? It's about culture, not strictly role. But we could include it in About the role as extra prose. However we must preserve all substantive information; we cannot drop it. So we need to include that culture description somewhere. Since we cannot create a new heading, we could put it under About the role as additional paragraph. Similarly, "What Does It Look Like Working Here?" includes collaboration, family, fun, etc. That's substantive. We'll include under About the role. Now we need to format lists with

• . For responsibilities, requirements, qualifications, skills, benefits. We need to decide which headings to use. We have: - About the role: includes initial description + culture description. - Responsibilities: from "What You Will Do:" list. - Requirements: Must Haves (bullet list). Could also include Nice To Haves? Might be Qualifications or Skills. But we have separate headings for Qualifications and Skills. We could put Must Haves under Requirements, Nice To Haves under Qualifications, and maybe skills like Excel under Skills. However the posting already separates Must Haves (education, experience, etc.) and Nice To Haves (industry experience, contract management, revenue recognition). Also there is a list of skills within Must Haves: "Strong understanding of project accounting principles, budgeting, forecasting, billing, and revenue recognition. Experience working with ERP/accounting systems. Advanced proficiency in Microsoft Excel. Excellent analytical, organizational, and problem-solving skills. Strong verbal and written communication skills. Ability to manage multiple priorities in a fast-paced environment." Those could be considered Skills. But we can also keep them under Requirements. Given we have three headings: Requirements, Qualifications, Skills. We need to decide distribution to avoid thin sections. Perhaps combine Must Haves into Requirements, Nice To Haves into Qualifications, and the specific skill items (Excel, analytical, etc.) into Skills. But that may split thin. Alternatively, we could just use Requirements for all Must Haves and Nice To Haves, and not use Qualifications or Skills headings (since we should only include sections when posting has real specific content). If we don't have distinct content for Qualifications or Skills, we should omit those headings. The instruction: "Prefer a few substantive sections over many thin ones." So we can omit Qualifications and Skills if not needed. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Check if we have content for each: - About the role: yes. - Responsibilities: yes. - Requirements: yes (Must Haves + Nice To Haves). Could combine. - Benefits: yes. - Pay: yes. - Schedule: yes (hours info). Now we need to extract content precisely, preserving all substantive info, no invention. Let's gather text. About the role: The first paragraph: "As the Project Accountant, you will play a key role in managing the full project accounting lifecycle. From initial project setup through closeout, you will oversee the financial management of projects, ensuring accurate budgeting, billing, revenue recognition, forecasting, financial reporting, and compliance with contractual requirements. You will work closely with Project Managers, Operations, and Finance leadership to monitor project financial performance, identify opportunities to support profitability, and ensure financial accuracy and integrity throughout the project lifecycle. Your attention to detail and ability to collaborate across teams will be critical to the overall success of each project." Then culture paragraph: "What Does It Look Like Working Here? We believe that building a strong community is about establishing a prevailing sense of fellowship among our team members, friends, and neighbors. Collaboration – working with others towards the best solution, placing great emphasis on the collective wisdom of our internal teams. Family – celebrating others’ successes, genuinely caring about the happiness and well-being of our team members and recognizing their own families as extensions of the CPL family. Fun – not taking oneself too seriously, fully understanding that fun at work is conducive to productivity. Inspiration – contributing to an uplifting workplace that facilitates growth and success by maintaining a positive, upbeat attitude. Integrity – doing what is ethically right and providing reliable follow-through on commitments. Ingenuity – seeking new opportunities and consistently identifying unexpected and practical ways to solve problems." We should include that as prose under About the role. Now Responsibilities: list from "What You Will Do:" includes: - Set up new projects in the accounting system and ensure accurate financial data. - Review contracts and project terms to ensure compliance with company policies and customer agreements. - Develop and maintain project budgets, forecasts, and cost projections. - Monitor project performance, costs, revenue, and profitability. - Prepare and process customer billings in accordance with contract terms. - Manage revenue recognition and ensure compliance with accounting standards. - Track accounts receivable, support collections efforts, and resolve billing issues. - Prepare monthly project financial reports, variance analyses, and forecasts. - Collaborate with Project Managers to identify financial risks and opportunities. - Process project modifications, change orders, and contract amendments. - Perform project closeout activities, including final billing, reconciliations, and documentation. - Support internal and external audits as needed. We need to put each as
• . Now Requirements: Must Haves and Nice To Haves. Must Haves: - Bachelor's degree in Accounting, Finance, Business Administration, or a related field. - Minimum of 3 years of project accounting experience. - Demonstrated experience managing projects through the full life cycle, from project setup to project closeout. - Strong understanding of project accounting principles, budgeting, forecasting, billing, and revenue recognition. - Experience working with ERP/accounting systems. - Advanced proficiency in Microsoft Excel. - Excellent analytical, organizational, and problem-solving skills. - Strong verbal and written communication skills. - Ability to manage multiple priorities in a fast-paced environment. Nice To Haves: - Experience in engineering, construction, professional services, or project-based environments. - Knowledge of contract management and project financial controls. - Experience with percentage-of-completion and other project revenue recognition methods. We'll combine into one list under Requirements. Now Benefits: from "What We Offer:" includes: - Benefits for Regular Full-Time & Part-Time Employees Working 30+ Hours/Week - Healthcare for you and your family: Medical, Dental & Vision insurance - Single HDHP Medical plan with 100% paid premium - Health Savings Account (HSA) with employer match - Medical and Dependent Care Flexible Spending Accounts - FREE Life Insurance and AD&D Insurance - Voluntary Life Insurance for you and your family - FREE Short-Term and Long-Term Disability Insurance - PTO + Sick Time + 8 Holidays per year - Retirement Savings Plan with contribution from CPL to grow your retirement funds - Internal Mobility & Career Advancement - Licensure Assistance - Additional benefits available to FT Employees Working 40+ Hours/Week - Tuition Assistance: You may be eligible for continuing education assistance - Student Loan Assistance Program: CPL will contribute up to $100/month for 5 years ($6,000 total) toward student loan debt We need to preserve all substantive info. We'll format as list items; some items have sub-details (like colon). We'll keep as plain text. Now Pay: "The rate for this position generally ranges between $60,000 to 72,000 annually. This range is a good faith estimate provided pursuant to the New York Pay Transparency Law. It is based on what a successful New York applicant might be paid and assumes that the successful candidate will be in New York or perform the position from New York. Similar positions located outside of New York will not necessarily receive the same compensation. Actual pay rates may vary from the range, as permitted by New York Equal Pay Transparency Law. Compensation offers will be based on various factors, including operational needs, individual education, qualifications and experience, work location and comparison to employees already in the role, as well as other considerations permitted by law. A potential new employee's pay history will not be used in compensation decisions." We need to keep all that. It's a bit long but we must preserve. Now Schedule: from benefits we have mention of hours: "Benefits for Regular Full-Time & Part-Time Employees Working 30+ Hours/Week" and "Additional benefits available to FT Employees Working 40+ Hours/Week". So schedule info: Full-time 30+ hours/week, Part-time also 30+? Actually says Regular Full-Time & Part-Time Employees Working 30+ Hours/Week. So both full-time and part-time work at least 30 hours/week. Additional benefits for FT Employees Working 40+ Hours/Week. So we can summarize: Position is full-time (minimum 30 hours/week) with additional benefits for those working 40+ hours/week. We'll keep that as prose. Now we must ensure we do not include any boilerplate: EEO statement, unsolicited resumes, etc. Must remove those lines at end. Now produce HTML fragment. We'll wrap each section in

  heading then content. For About the role: two paragraphs: first paragraph from role description, second paragraph from culture. We'll put them as

  elements. For Responsibilities:

  Responsibilities

  then
  • ... each. For Requirements:

    Requirements

    then
    • ... each. For Benefits:

      Benefits

      then
      • ... each. For Pay:

        Pay

        then

        ... the pay paragraph(s). Could be multiple paragraphs but we can combine into one

        with line breaks? Better to keep as

        preserving sentences. For Schedule: