Controller
ASRC Energy Services, LLC · Anchorage, AK · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: JOB SUMMARY (we can treat as About the role). ESSENTIAL DUTIES (Responsibilities). REQUIRED EXPERIENCE (Requirements/Qualifications/Skills). TOTAL REWARDS (Benefits). No explicit Pay or Schedule info. So we should not include Pay or Schedule sections. Also maybe include "Why work with us" but not required heading; we could incorporate into About the role or maybe as a separate section like "Company Overview" but not in allowed headings list. The instruction says use those headings for section headings; we can only use those headings. So we can map:
- About the role: from JOB SUMMARY (maybe also include WHY WORK WITH US? but that's not required; we could include as part of About the role prose.)
- Responsibilities: ESSENTIAL DUTIES.
- Requirements: REQUIRED EXPERIENCE (maybe also include education etc.)
- Qualifications: maybe same as Requirements? But we should not duplicate. Could combine Requirements and Qualifications into one? But we need to follow instruction: Use headings only when posting has real specific content for it. We have content for Requirements (education, experience). Qualifications maybe also covered (skills). Could split: Requirements: education + experience; Qualifications: knowledge of GAAP, analytical skills, Oracle Cloud a plus. Skills: maybe same. But we risk thin sections. Better to have a few substantive sections: About the role, Responsibilities, Requirements (which includes education, experience, qualifications, skills). Benefits: TOTAL REWARDS.
Thus we will output:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It doesn't explicitly forbid other headings, but says use those for section headings. Safer to stick to those. Physical demands could be placed under Responsibilities? Not really. Could be under About the role as part of role description. Might be okay.
We must not include duplicated lines. We'll need to parse the posting.
Let's extract content.
JOB SUMMARY:
"The Controller is responsible for leading accounting operations and financial reporting functions, ensuring the accuracy, integrity, and timeliness of financial information in accordance with GAAP, FAR requirements, and company policies. This role provides senior-level oversight of the financial close processes, internal controls, annual audit, and compliance activities, while partnering with FP&A, operations, and executive leadership to support strategic business decision-making. The Controller will also play a critical role in process efficiency and AI initiatives for system and process optimization."
ESSENTIAL DUTIES (list):
- Provide senior leadership and oversight of accounting functions for multi-segment operation
- Lead the monthly, quarterly and annual financial close and reporting process
- Partner with Operations and FP&A to support business line operational financial reporting
- Establish and strengthen process and project controls frameworks that improve operational performance, governance and process improvements
- Partner with in-house AI team to identify and expand AI initiatives for system optimization, automation, data visualization and process efficiency
- Engage in monthly business line financial and operational reviews, including RFP support, pricing, and contracting strategy
- Oversee account reconciliations, journal entries, financial statement preparation, management reporting, and supporting schedules to ensure accuracy and completeness
- Maintain strong corporate governance through effective internal controls, accounting policies and procedures
- Ensure financial reporting compliance with US GAAP, FAR requirements, company policies, and applicable contract requirements
- Lead, coach, and develop accounting team members while promoting accountability, performance, and professional growth
- Drive cross-functional collaboration to improve financial processes and objectives
- Support AES zero-incident safety culture and assume personal accountability and responsibility for safe work practices in all projects, activities, and operations.
- Other duties will be assigned to this position as needed.
REQUIRED EXPERIENCE:
- Bachelor’s degree in Accounting (CPA required)
- Minimum 10+ years of accounting experience, including leadership roles
- Strong knowledge of GAAP and financial reporting standards
- Excellent analytical, organizational, and communication skills
- Oracle Cloud experience a plus (ERP is fully implemented)
TOTAL REWARDS (Benefits):
- Comprehensive medical coverage through the Federal Employee Health Benefits Plan (FEHB), as well as dental and vision insurance.
- Employees are eligible to participate in a 401(k) program with a company match of up to 4% and immediate vesting after just two pay periods.
- Access to an Employee Assistance Program (EAP)
- Wide range of supplemental insurance options including voluntary life insurance, short- and long-term disability, accidental death and dismemberment (AD&D), pet insurance, legal services, identity theft protection, hospital indemnity, accident insurance, and critical illness coverage.
- Tuition reimbursement opportunities and internal learning resources through our ASPIRE Academy.
- (Also mention "To learn more about our full suite of benefits, please visit our benefits page.") That's a link; we can include as sentence.
WHY WORK WITH US (could be part of About the role):
- At ASRC Energy, people come first. We collaborate, value every contribution, and invest in the success of our employees, families, and communities. If you’re looking for meaningful work with a company that values safety, integrity, and growth, start your career with ASRC Energy and ASPIRE with us.
- Then list values: Absolute Integrity, Safety, People First, Iñupiat Heritage, Resilient Family, Exceptional Service Quality. Each with description.
PHYSICAL DEMANDS AND WORK ENVIRONMENT:
- A post-offer, pre-hire Functional Capacity Evaluation (FCE) will be conducted to ensure an employee’s ability to safely meet job standards. Reasonable accommodation may be made to enable individuals with disabilities to perform these functions.
- Candidates must be able to comply with the ASRC Energy Driving Records and Motor Vehicle Use Policy, successfully pass a pre-employment drug test which may include both urinalysis and hair testing, and meet the physical requirements of working in a remote location under arctic conditions.
- In addition, candidates will be required to pass a Fit-for-Duty Exam, complete a background check, and obtain and maintain an access badge for the work location.
- The availability of this position is contingent upon the Company’s continued operational needs once training is completed.
- If you need assistance or reasonable accommodation to apply for this position, please contact the ASRC Energy Human Resources Team at (907) 334-1688.
We need to decide where to put physical demands. Could be part of About the role or Responsibilities? Probably better as part of About the role (role description). But it's more about hiring process. Could be a separate section like "Requirements" but we already have that for qualifications. Could add a bullet under Requirements about physical demands? Might be okay.
But we must not invent or summarize away detail. We need to preserve all substantive information. If we put physical demands under Requirements, we must include all those details.
Thus Requirements section could include education, experience, knowledge, skills, Oracle Cloud, plus physical demands, background check, drug test, etc. That would be a long list but okay.
Alternatively we could create a separate section "Qualifications" for knowledge/skills, and "Requirements" for education/experience, and maybe "Benefits". But we risk thin sections.
Given instruction: "Prefer a few substantive sections over many thin ones." So better to combine into few sections: About the role, Responsibilities, Requirements (including education, experience, qualifications, skills, physical demands, etc.), Benefits.
Thus we will not have separate Qualifications, Skills, Pay, Schedule.
Now we need to format as HTML fragment.
We'll produce:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: JOB SUMMARY (we can treat as About the role). ESSENTIAL DUTIES (Responsibilities). REQUIRED EXPERIENCE (Requirements/Qualifications/Skills). TOTAL REWARDS (Benefits). No explicit Pay or Schedule info. So we should not include Pay or Schedule sections. Also maybe include "Why work with us" but not required heading; we could incorporate into About the role or maybe as a separate section like "Company Overview" but not in allowed headings list. The instruction says use those headings for section headings; we can only use those headings. So we can map:
- About the role: from JOB SUMMARY (maybe also include WHY WORK WITH US? but that's not required; we could include as part of About the role prose.)
- Responsibilities: ESSENTIAL DUTIES.
- Requirements: REQUIRED EXPERIENCE (maybe also include education etc.)
- Qualifications: maybe same as Requirements? But we should not duplicate. Could combine Requirements and Qualifications into one? But we need to follow instruction: Use headings only when posting has real specific content for it. We have content for Requirements (education, experience). Qualifications maybe also covered (skills). Could split: Requirements: education + experience; Qualifications: knowledge of GAAP, analytical skills, Oracle Cloud a plus. Skills: maybe same. But we risk thin sections. Better to have a few substantive sections: About the role, Responsibilities, Requirements (which includes education, experience, qualifications, skills). Benefits: TOTAL REWARDS.
Thus we will output:
About the role
... (job summary + why work with us maybe)
Responsibilities
- ... each duty
Requirements
- ... each requirement
Benefits
- ... each benefit
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It doesn't explicitly forbid other headings, but says use those for section headings. Safer to stick to those. Physical demands could be placed under Responsibilities? Not really. Could be under About the role as part of role description. Might be okay.
We must not include duplicated lines. We'll need to parse the posting.
Let's extract content.
JOB SUMMARY:
"The Controller is responsible for leading accounting operations and financial reporting functions, ensuring the accuracy, integrity, and timeliness of financial information in accordance with GAAP, FAR requirements, and company policies. This role provides senior-level oversight of the financial close processes, internal controls, annual audit, and compliance activities, while partnering with FP&A, operations, and executive leadership to support strategic business decision-making. The Controller will also play a critical role in process efficiency and AI initiatives for system and process optimization."
ESSENTIAL DUTIES (list):
- Provide senior leadership and oversight of accounting functions for multi-segment operation
- Lead the monthly, quarterly and annual financial close and reporting process
- Partner with Operations and FP&A to support business line operational financial reporting
- Establish and strengthen process and project controls frameworks that improve operational performance, governance and process improvements
- Partner with in-house AI team to identify and expand AI initiatives for system optimization, automation, data visualization and process efficiency
- Engage in monthly business line financial and operational reviews, including RFP support, pricing, and contracting strategy
- Oversee account reconciliations, journal entries, financial statement preparation, management reporting, and supporting schedules to ensure accuracy and completeness
- Maintain strong corporate governance through effective internal controls, accounting policies and procedures
- Ensure financial reporting compliance with US GAAP, FAR requirements, company policies, and applicable contract requirements
- Lead, coach, and develop accounting team members while promoting accountability, performance, and professional growth
- Drive cross-functional collaboration to improve financial processes and objectives
- Support AES zero-incident safety culture and assume personal accountability and responsibility for safe work practices in all projects, activities, and operations.
- Other duties will be assigned to this position as needed.
REQUIRED EXPERIENCE:
- Bachelor’s degree in Accounting (CPA required)
- Minimum 10+ years of accounting experience, including leadership roles
- Strong knowledge of GAAP and financial reporting standards
- Excellent analytical, organizational, and communication skills
- Oracle Cloud experience a plus (ERP is fully implemented)
TOTAL REWARDS (Benefits):
- Comprehensive medical coverage through the Federal Employee Health Benefits Plan (FEHB), as well as dental and vision insurance.
- Employees are eligible to participate in a 401(k) program with a company match of up to 4% and immediate vesting after just two pay periods.
- Access to an Employee Assistance Program (EAP)
- Wide range of supplemental insurance options including voluntary life insurance, short- and long-term disability, accidental death and dismemberment (AD&D), pet insurance, legal services, identity theft protection, hospital indemnity, accident insurance, and critical illness coverage.
- Tuition reimbursement opportunities and internal learning resources through our ASPIRE Academy.
- (Also mention "To learn more about our full suite of benefits, please visit our benefits page.") That's a link; we can include as sentence.
WHY WORK WITH US (could be part of About the role):
- At ASRC Energy, people come first. We collaborate, value every contribution, and invest in the success of our employees, families, and communities. If you’re looking for meaningful work with a company that values safety, integrity, and growth, start your career with ASRC Energy and ASPIRE with us.
- Then list values: Absolute Integrity, Safety, People First, Iñupiat Heritage, Resilient Family, Exceptional Service Quality. Each with description.
PHYSICAL DEMANDS AND WORK ENVIRONMENT:
- A post-offer, pre-hire Functional Capacity Evaluation (FCE) will be conducted to ensure an employee’s ability to safely meet job standards. Reasonable accommodation may be made to enable individuals with disabilities to perform these functions.
- Candidates must be able to comply with the ASRC Energy Driving Records and Motor Vehicle Use Policy, successfully pass a pre-employment drug test which may include both urinalysis and hair testing, and meet the physical requirements of working in a remote location under arctic conditions.
- In addition, candidates will be required to pass a Fit-for-Duty Exam, complete a background check, and obtain and maintain an access badge for the work location.
- The availability of this position is contingent upon the Company’s continued operational needs once training is completed.
- If you need assistance or reasonable accommodation to apply for this position, please contact the ASRC Energy Human Resources Team at (907) 334-1688.
We need to decide where to put physical demands. Could be part of About the role or Responsibilities? Probably better as part of About the role (role description). But it's more about hiring process. Could be a separate section like "Requirements" but we already have that for qualifications. Could add a bullet under Requirements about physical demands? Might be okay.
But we must not invent or summarize away detail. We need to preserve all substantive information. If we put physical demands under Requirements, we must include all those details.
Thus Requirements section could include education, experience, knowledge, skills, Oracle Cloud, plus physical demands, background check, drug test, etc. That would be a long list but okay.
Alternatively we could create a separate section "Qualifications" for knowledge/skills, and "Requirements" for education/experience, and maybe "Benefits". But we risk thin sections.
Given instruction: "Prefer a few substantive sections over many thin ones." So better to combine into few sections: About the role, Responsibilities, Requirements (including education, experience, qualifications, skills, physical demands, etc.), Benefits.
Thus we will not have separate Qualifications, Skills, Pay, Schedule.
Now we need to format as HTML fragment.
We'll produce:
About the role
... (job summary + why work with us + values)
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...