Jobs · Finance · Colorado

Project Cost Controls Specialist (Overland Park, KS)

Quanta Infrastructure Solutions Group · Denver, CO · 1 mo ago
On-siteFinanceFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us" and "About This Role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. So we need to parse content. We have: - About Us: description of QISG. Could be considered "About the role"? Actually "About Us" is company description. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map sections accordingly. We have "About This Role": includes location, onsite Monday-Friday, 15% domestic travel, address, role description. That could be "About the role". We'll put that under

About the role

. Then "What You'll Do": responsibilities. That's Responsibilities. Then "What You'll Bring": requirements/qualifications/skills. Could split into Requirements and Qualifications and Skills. But we can combine? The instruction: prefer a few substantive sections over many thin ones. So we could have one section for Requirements/Qualifications/Skills combined? But they ask to use headings like Requirements, Qualifications, Skills. We could decide to have separate sections if content distinct. Let's see content: "What You'll Bring" includes: 1-6 years in cost management and project controls. Expertise in forecasting, cost control, change management, and risk analysis. Convert complex financials into clear, actionable insights. Proficient in JDE, EcoSys, Procore, Excel, Power BI. Bachelor’s in Construction Management, Business, Finance, or equivalent experience. Willing to travel up to 15% domestically. Full-time, onsite position in Overland Park, KS. That includes experience, expertise, skills (tools), education, travel willingness. Could be split: Requirements (experience, education), Skills (tools proficiency), Qualifications maybe overlapping. But to avoid thin sections, maybe combine into one "Requirements" section covering all. However instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't require all; we can omit if not substantive. So we could have: - About the role (from About This Role) - Responsibilities (What You'll Do) - Requirements (What You'll Bring) maybe also include Skills within same? But we could also have Skills separate if we want. Let's see if we have enough content for Skills: tools proficiency (JDE, EcoSys, Procore, Excel, Power BI). That's substantive. Could make a Skills section. Qualifications: education (Bachelor’s in Construction Management, Business, Finance, or equivalent experience). Could be Qualifications. Thus we can have:

About the role

Onsite Monday-Friday, with 15% domestic travel. 7101 College Blvd., Suite 1500, Overland Park, KS 66210. As a Cost Specialist at QISG, you will be a key member of the Project Controls team, responsible for monitoring project financial performance throughout the project lifecycle. You'll develop and maintain budgets, track actual costs, perform variance analysis, prepare forecasts, and provide leadership with accurate reporting to support strategic decision-making. Your work will directly contribute to the successful execution of large-scale utility, power generation, and renewable energy EPC projects across North America.

But note: The "About This Role" also includes the location and travel. We'll incorporate. Then Responsibilities: list bullet points from "What You'll Do". We'll make
  • each. Then Qualifications: education: Bachelor’s in Construction Management, Business, Finance, or equivalent experience. Then Skills: proficiency in JDE, EcoSys, Procore, Excel, Power BI; also expertise in forecasting, cost control, change management, risk analysis; ability to convert complex financials into clear insights. Then Requirements: maybe experience 1-6 years, willingness to travel up to 15% domestically, full-time onsite. But we might have overlapping. Could combine experience and travel into Requirements. Let's decide: - About the role - Responsibilities - Qualifications (education) - Skills (tools and expertise) - Requirements (experience, travel, full-time) Benefits: we have "What You'll Get" section with benefits: Competitive base salary, Generous PTO & paid holidays, 401(k) with generous match, Comprehensive benefits – medical, dental, vision, and life insurance, Weekly pay, Great mentoring & career growth opportunities. That's substantive benefits. So we should include Benefits section. Pay: they mention Competitive base salary but not specific number. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state "Competitive base salary" which is a statement about pay, albeit not specific. Is that enough? It says "Competitive base salary". That is a statement about pay. So we could include Pay section with that sentence. However they also say "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Competitive base salary" is not exactly placeholder like those, but it's vague. Might be considered filler? The instruction says avoid filler/placeholder text like "commensurate with experience", "not specified", etc. "Competitive base salary" is somewhat generic but not explicitly listed as forbidden. I'd lean to include Pay section with that sentence. Schedule: they mention Onsite Monday-Friday, with 15% domestic travel. That's schedule info. So we could include Schedule section. However schedule info is also in About the role. But we could still have Schedule section with that detail. But we must avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we incorporate schedule into About the role or Responsibilities? But they said use headings like Schedule. If we have schedule info, we could include Schedule section. However we already have About the role includes location and travel. Might be okay to have Schedule separate. But we need to avoid repeating same content. Let's think: About the role currently includes location and travel. If we also have Schedule section repeating that, it's duplication. Better to put schedule in Schedule section and maybe remove from About the role? But About the role also includes role description. We could keep About the role focusing on role description, and move location/travel to Schedule. However the instruction says include a section ONLY when the posting has real, specific content for it. The posting does have schedule info (Onsite Monday-Friday, with 15% domestic travel). So we can have Schedule section. Thus we can restructure: - About the role: description of role (key member of Project Controls team, responsibilities high-level). Could be short paragraph. - Responsibilities: detailed list. - Qualifications: education. - Skills: tools and expertise. - Requirements: experience 1-6 years, willingness to travel up to 15% domestically, full-time onsite. - Benefits: list. - Pay: Competitive base salary. - Schedule: Onsite Monday-Friday, with 15% domestic travel. (maybe also location? Could include address? The address is location; schedule is about days and travel. Could include address in About the role or maybe separate? But we already have location in About the role? We'll decide to put address in About the role maybe. Let's keep address in About the role. Thus About the role: includes address and role description. Schedule: Onsite Monday-Friday, with 15% domestic travel. Now check for duplication: About the role includes address and role description; Schedule includes days/travel. No duplication. Now Benefits: list items. Pay: Competitive base salary. Now we need to output HTML fragment only, no /. Use

    for headings,
    • for lists,

      for prose. Let's craft. About the role paragraph: "Located at 7101 College Blvd., Suite 1500, Overland Park, KS 66210. As a Cost Specialist at QISG, you will be a key member of the Project Controls team, responsible for monitoring project financial performance throughout the project lifecycle. You'll develop and maintain budgets, track actual costs, perform variance analysis, prepare forecasts, and provide leadership with accurate reporting to support strategic decision-making. Your work will directly contribute to the successful execution of large-scale utility, power generation, and renewable energy EPC projects across North America." But note that some of that overlaps with responsibilities (develop budgets etc). Might be duplication. However About the role is supposed to be high-level description; we can keep it brief: maybe just location and that you are a Cost Specialist in Project Controls team. Let's keep short. Better: About the role: "Located at 7101 College Blvd., Suite 1500, Overland Park, KS 66210. As a Cost Specialist at QISG, you will be a key member of the Project Controls team." That's enough. Now Responsibilities list: from What You'll Do bullet points. Let's extract each sentence as bullet: - Track, analyze, and control project costs for EPC energy and utility infrastructure projects, including transmission, substations, renewables, and utility construction. - Monitor project budgets, actual costs, forecasts, and cost trends across complex, multi-year projects. - Develop and maintain Estimates at Completion (EAC) and Estimates to Complete (ETC) to support accurate project forecasting. - Apply Earned Value Management (EVM) principles (highly preferred) to evaluate project performance, identify cost/schedule variances, and support proactive decision-making. - Identify cost risks, trends, and deviations while escalating potential issues to Project Managers and leadership. - Support change management activities, including change orders, budget transfers, and evaluation of cost impacts. - Partner with Project Managers, Operations Directors, and technical teams to align financial performance with project execution plans. - Prepare accurate cost reports, dashboards, and forecasts for leadership and project stakeholders. - Support Project Controls Execution Plans and ensure compliance with company processes and standards. - Utilize tools such as JDE, EcoSys, Procore, Excel, and Power BI for job cost tracking, analysis, and reporting. - Act as a trusted cost control resource for assigned projects and contribute to continuous improvement initiatives. Now Qualifications: Bachelor’s in Construction Management, Business, Finance, or equivalent experience. Skills: Expertise in forecasting, cost control, change management, and risk analysis. Convert complex financials into clear, actionable insights. Proficient in JDE, EcoSys, Procore, Excel, Power BI. We could split into two bullet lists? But we can just put in

      or

        . Since it's a list of skills, better
          . Requirements: 1-6 years in cost management and project controls. Willing to travel up to 15% domestically. Full-time, onsite position in Overland Park, KS. But note location already in About the role; we could still mention onsite. Benefits: list: - Competitive base salary - Generous PTO & paid holidays to maintain work-life balance - 401(k) with a generous match to plan for your future - Comprehensive benefits – medical, dental, vision, and life insurance - Weekly pay for consistent, reliable compensation - Great mentoring & career growth opportunities – we invest in your development Pay: Competitive base salary (maybe we already have in Benefits; but we can still have Pay section with that sentence). However to avoid duplication, maybe we omit Pay section because benefits already includes Competitive base salary. But instruction: include Pay section only if posting actually states them. It does state Competitive base salary. But we already have it in Benefits. Could

Similar jobs