Project Controls Analyst

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. Remove boilerplate. Preserve all substantive info. We need to parse the job posting. Job Overview: description about role. That could go under "About the role". Should we include "Job Overview" as content? Yes. Responsibilities: list of responsibilities. Use

• . Requirements: maybe "Basic Qualifications". That's requirements. Qualifications: maybe "Basic Qualifications" also? Actually they have "Basic Qualifications". Could map to Requirements or Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide where each piece goes. We have: - About the role: Job Overview paragraph(s). Also maybe "About APTIM" and "What You Can Expect From APTIM" could be part of About the role or separate? Probably include in About the role. - Responsibilities: "Key Responsibilities/Accountabilities" bullet list. - Requirements: maybe "Basic Qualifications" list. - Qualifications: maybe not separate; could be same as Requirements? But we need to avoid empty sections. If we don't have distinct qualifications beyond requirements, we could omit Qualifications heading. - Skills: maybe list of skills from qualifications: technical concepts, communication, attention to detail, etc. Could extract. - Benefits: "Employee Benefits" section. - Pay: "As of the date of this posting, a good faith estimate of the current pay range for this position is $38.46 - $60.00 Per Hour." plus explanation. - Schedule: "This role will require 40 hours per week." That's schedule. We must not include filler like "commensurate with experience". Not present. We must not include application instructions, cookie/navigation/legal/EEO etc. There's none. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Job Overview paragraphs: "As a Project Controls Analyst with APTIM, you will have the chance to work on project teams using expertise in forecasting, change management, cost management, project budget analysis, and other financial reporting tools. In some cases, you could also have the chance to work on project teams which require expertise in earn value analysis, risk management, proposal support, estimate development, and cashflow. You will manage the overall project/program cost controls and financial reporting by providing client management documentation, updates, and presentations for projects generally under $5M in value. This position will primarily support the Environmental & Energy Solutions team. This role will require 40 hours per week. Environmental project portfolios may include a large volume of projects and task orders performed for federal, state, municipal, commercial, and industrial clients under a variety of contract structures. The Project Controls Analyst must therefore be able to effectively prioritize responsibilities, analyze project performance at both the individual project and program/portfolio level, and proactively communicate issues requiring management attention. The position serves as a financial and project controls business partner to Project and Program Managers, helping ensure projects are financially sound, accurately forecasted, compliant with contractual requirements, and positioned to achieve established financial objectives." Note: The schedule line "This role will require 40 hours per week." appears also in Job Overview; we might still include schedule separately but we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but better to avoid duplication. However schedule is a separate section; we could keep schedule line there and maybe remove from About the role? But that would be removing substantive info. We could keep it in both places? Might be considered duplication but not invented. Safer to keep it only under Schedule and remove from About the role? That would be removing detail from About the role (the schedule line). That would lose info. Better to keep it in About the role and also include Schedule section with same info? That duplicates but preserves all info. The instruction didn't forbid duplication. However they said "Prefer a few substantive sections over many thin ones." Duplication may be okay but could be considered thin? I'd rather keep schedule only under Schedule and keep the rest of About the role without that sentence. But then we lose the schedule detail from About the role. However the schedule detail is still present in Schedule section, so overall preserved. The About the role section would be missing that sentence, but it's still present elsewhere. Is that considered removing substantive information? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we move the sentence to another section, we still preserve it, not removed. So it's okay. Thus we can extract schedule line and put under Schedule heading. Now Responsibilities: list from "Key Responsibilities/Accountabilities". Let's capture each bullet. List: - Establish and maintain project financial structures, budgets, forecasts, and cost controls consistent with contract requirements and approved project plans. - Support project setup, including project/task structures, work breakdown structures, funding, budgets, billing requirements, and financial parameters. - Monitor project revenue, costs, contribution margin, labor performance, funding, commitments, and profitability throughout the project lifecycle. - Review project performance against budget, forecast, and prior-period results and identify significant variances. - Partner with Project Managers to develop and maintain accurate Estimate to Complete (ETC) and Estimate at Completion (EAC) forecasts. - Evaluate remaining project scope, staffing requirements, subcontractor costs, expenses, and other anticipated costs when developing forecasts. - Monitor project financial performance and identify emerging risks, opportunities, unfavorable trends, and potential margin erosion. - Recommend corrective actions and work with Project Managers to improve project financial performance. - Support financial management of projects from initial setup through final financial closeout. - Coordinate with Project Managers to review and update ETCs, revenue forecasts, costs, staffing assumptions, and project completion estimates. - Review current-month financial activity for completeness, accuracy, and reasonableness. - Analyze Month-to-Date (MTD), Year-to-Date (YTD), and Inception-to-Date (ITD) project performance. - Identify and investigate significant month-over-month, budget-to-actual, and forecast-to-actual variances. - Coordinate required corrections, reclasses, or financial adjustments with Finance and Accounting. - Provide timely explanations of material project financial variances to Project Managers and management. - Support annual budgeting and periodic forecasting activities for assigned environmental programs and portfolios - Utilize ERP, project management, and financial systems to extract, validate, reconcile, and analyze project information. - Develop and maintain advanced Microsoft Excel reporting and analytical tools. Note: Some lines may have line breaks; we keep as is. Now Basic Qualifications: list. "Minimum of 2-5 Years experience working in project controls" "Must have a bachelor's degree" "Demonstrated ability to Use technical concepts and industry standard project management tools and techniques to effectively coordinate project control activities and functions to creatively and effectively solve complex problems and identify correlated data to inform decision making." "Strong written and verbal communication skills." "Strong attention to detail and commitment to financial data accuracy." "Ability to work across discipline teams to assimilate project data from various sources" "Ability to maintain a high level of confidentiality." "Understands the basic grammar/concepts of multiple professional disciplines and can work across discipline siloed teams to solve complex interrelated problems." "Understanding of various contract structures Fixed Price, Unit Price, Cost Reimbursable and the implications that these structures have on project cost and revenue." "Understanding of the fundamental concepts of accrual basis and double entry accounting." "Proficient in Microsoft Office, especially Excel." "Familiarity with Power BI Data and extraction of datasets" "Proficient working in JD Edwards or other ERP System" "Communicating with internal and external project stakeholders and Interpreting project cost data at multiple levels of the organization." We could split into Requirements and Qualifications and Skills. But we have headings: Requirements, Qualifications, Skills. We need to decide distribution. Maybe: - Requirements: Minimum experience, bachelor's degree. - Qualifications: Understanding of contract structures, accrual basis, proficiency in Excel, Power BI, JD Edwards, etc. - Skills: Communication, attention to detail, ability to work across teams, confidentiality, etc. But we must not invent headings without content. We have content for each. Let's parse: Requirements (basic qualifications that are mandatory): "Minimum of 2-5 Years experience working in project controls", "Must have a bachelor's degree". Could also include "Demonstrated ability to Use technical concepts..." but that's more skill. Qualifications: maybe the technical knowledge: "Understanding of various contract structures...", "Understanding of the fundamental concepts of accrual basis and double entry accounting.", "Proficient in Microsoft Office, especially Excel.", "Familiarity with Power BI Data and extraction of datasets", "Proficient working in JD Edwards or other ERP System". Skills: "Strong written and verbal communication skills.", "Strong attention to detail and commitment to financial data accuracy.", "Ability to work across discipline teams to assimilate project data from various sources", "Ability to maintain a high level of confidentiality.", "Understands the basic grammar/concepts of multiple professional disciplines and can work across discipline siloed teams to solve complex interrelated problems.", "Communicating with internal and external project stakeholders and Interpreting project cost data at multiple levels of the organization." But note some overlap; we just need to ensure we don't lose any. Now Benefits: from "Employee Benefits" paragraph. We need to capture all details: "APTIM Corporate is committed to providing an extensive range of benefits that protect and promote the health and financial well-being of our employees and their families through the APTIM Benefits Marketplace https://aptim.makeityoursource.com/. Medical, vision, and dental insurance: Through the marketplace, our employees can choose benefits from five metallic levels and several carriers to find the right benefits that work for them in their location. Company paid and optional Life insurance Short-term and long-term disability insurance Accident, Critical Illness, and Hospital Indemnity coveragePaid holidays, vacation, and sick leave (eligibility based on company policy and applicable law)401(k) APTIM offers three 401k plans through the Aon Pooled Employer Plan (PEP). The specific plan you are eligible for depends on the business unit you are in. The details of the largest plan are found here: APTIM 401(k) GuideAPTIM - Helpful Documents Watch Our Video About APTIM - In Pursuit of Better" We need to preserve all that. Note there are some missing spaces: "coveragePaid" etc. We'll keep as is. Pay: "As of the date of this posting, a good faith estimate of the current pay range for this position is $38.46 - $60.00 Per Hour. Compensation depends on several factors including: experience, education, key skills, geographic location of the position, client requirements, external market competitiveness, and internal equity among other employees within APTIM." Schedule: "This role will require 40 hours per week." Now About the role: we need to include the Job Overview paragraph(s) minus the schedule line. Also maybe include "About APTIM" and "What You Can Expect From APTIM" as part of About the role? Those are descriptive of company and expectations. Could be considered part of About the role. We'll include them. Thus About the role content: - Job Overview (without schedule line) - About APTIM paragraph - What You Can Expect From APTIM bullet list (the lines after "What You Can Expect From APTIM"). Let's extract: About APTIM: "APTIM enhances the quality of the environment, wellbeing of people, resilience of communities, and opportunity for