Capex Accounting Manager
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting.
First, we need to decide which sections have content.
The posting includes:
- Intro paragraph about GFiber, mission, etc. Could be "About the role"? Actually "About the role" heading is for description of role. The posting includes "Role Description:" then description. So we can put that under About the role
maybe.
But also there is a paragraph about GFiber mission etc. Could be considered "About the role" or maybe "About the company". Since only allowed headings are those listed, we can put company overview under About the role? Might be okay.
Responsibilities: bullet list after "In this role, you’ll:" includes items. Those are responsibilities.
Requirements: "At a minimum we’d like you to have:" list of qualifications (education, CPA, years experience). Those are requirements.
Qualifications: maybe "It’s preferred if you have:" list of preferred qualifications. Could be Qualifications or Skills? The allowed headings include Qualifications and Skills. We could treat "It’s preferred if you have:" as Qualifications (preferred) or Skills. Since they are capabilities, maybe Skills. But we have both Qualifications and Skills headings allowed. We need to decide.
We have "Data and analytics capability (SQL or BigQuery) to own pipelines, automation, and large-scale reconciliations." etc. Those are skills/preferred qualifications.
We also have "Ability to self-direct..." etc.
Thus we could have a Skills section for those.
Pay: The posting includes salary range: "The US base salary range for this full-time position is between $142,400 - $209,400 + bonus + benefits." Also mentions pay varies by location. So we have Pay content.
Benefits: Not explicitly listed besides "+ bonus + benefits". No detail about benefits. So we should not create Benefits section because no specific benefits listed.
Schedule: Not mentioned. So omit.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (maybe preferred), Skills, Pay.
But we need to avoid duplication. Let's map:
- About the role: include company overview and role description paragraph before responsibilities? The role description includes the paragraph starting "On the Controllership team you are a critical part..." plus maybe the intro about GFiber. We'll combine.
Better: About the role: include the introductory paragraphs about GFiber mission and the role description paragraph (starting "On the Controllership team...").
Responsibilities: bullet list after "In this role, you’ll:" (the list of items).
Requirements: bullet list after "At a minimum we’d like you to have:" (the list of minimum qualifications).
Qualifications: maybe we could treat "It’s preferred if you have:" as Qualifications (preferred). But we also have Skills heading for data analytics etc. However the preferred list includes both skills and experience. Could split: Qualifications for preferred qualifications (like track record, familiarity with group/composite-asset method, ability to self-direct). Skills for data and analytics capability (SQL or BigQuery). But the allowed headings are limited; we can decide to put all preferred items under Qualifications and not create Skills if we think it's redundant. However we need to follow instruction: "Prefer a few substantive sections over many thin ones." So maybe combine preferred qualifications and skills into one Qualifications section. But we also have a Skills heading allowed; we could use it for the data analytics capability. But that would be thin (just one bullet). Better to combine.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Pay.
Check if any content for Benefits or Schedule: none, so omit.
Now we need to output HTML fragment only, no /. Use for each heading, then content: either
for prose,
- for lists.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting.
Let's extract content.
About the role:
- Intro: "At GFiber, we believe that great internet has the power to drive innovation, strengthen communities, enable the impossible, and do all the everyday things that make all of our world go round. And the job of creating better internet is never done - so we’re growing! Our team is committed to building a place where people who want to make a difference can grow their careers and find their spot to belong. GFiber is an Alphabet company that brings Google Fiber and Google Fiber Webpass internet services to homes and businesses across the United States. Our teams are expanding as we connect more cities and people to exceptional internet."
- Then "The application window will be open until at least July 26, 2026. This opportunity will remain online based on business needs which may be before or after the specified date." This is metadata about application window; we should fold minor metadata into a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." This is about application window; we can include as a short paragraph maybe under About the role or separate? It's not a heading; we can include as a
after the intro. But we must not repeat the job title as a heading (the page already shows it). No job title given explicitly; we can ignore. Thus About the role section will contain two paragraphs: first the mission/intro, second the application window note. Then after that, we have "Role Description:" then the paragraph: "On the Controllership team you are a critical part of setting up the company for future financial success — enabling the business to move fast, while playing in control. You own the accounting for GFiber’s capital program: a multi-billion-dollar fiber network, from how a cost is coded at the PO through capitalization, close, disclosure, and audit. You set policy before transactions go live, own the systems and data that make capitalization correct upstream, and are the partner FP&A, Operations, and Tax rely on to avoid surprises." We could include that as part of About the role as well (maybe as a third paragraph). Or we could treat Role Description as part of About the role. Since we already have About the role heading, we can include all descriptive prose under it. Thus About the role will have multiple
elements. Now Responsibilities: list after "In this role, you’ll:" includes: - Own end-to-end ASC 360 PP&E and lease accounting, from capitalization costing (labor, material, allocations) through the full asset lifecycle to month-end close and reconciliations. - Maintain the capex-to-opex bridge to eliminate EBITDA surprises, support external audits, and partner cross-functionally with FP&A, Tax, and Ops on forecasting and commissioning. - Own lease accounting under ASC 842, from classification and ROU/lease-liability accounting through build-to-suit and financing analysis, modifications, and disclosures. - Own the SAP footprint behind the accounting, including Asset Accounting (FI-AA), Project System (PS) for WBS and network structures and AuC settlement, and Materials Management (MM) for inventory, along with the PO-coding architecture that drives correct capitalization, tax location, and managerial reporting at the point of PO creation. - Build and run the data and reporting layer, including SQL/BigQuery pipelines, accrual automation, large-scale reconciliations, and management reporting. - Grow, mentor and develop your team. We need to preserve all detail. So each bullet as
- . Now Requirements: after "At a minimum we’d like you to have:" list: - Bachelor’s degree or equivalent practical experience. - Certified Public Accountant (CPA) or Chartered Accountant (CA) - 10 years of progressive accounting experience in a capital-intensive industry, including ownership of PP&E and lease accounting (ASC 360 and ASC 842). - 5 years of direct people management experience. - 2 years of experience operating SAP Asset Accounting (FI-AA), Project System (PS), and Materials Management (MM). - 5 years of experience owning a month-end close and supporting external audits under US GAAP. We need to keep each as
- . Now Qualifications (preferred): after "It’s preferred if you have:" list: - Data and analytics capability (SQL or BigQuery) to own pipelines, automation, and large-scale reconciliations. - A track record of standing up and scaling a fixed-asset and lease function, and of influencing upstream contract and PO terms before signature. - Familiarity with the group/composite-asset method, cost or Manufacturing Overhead and labor capitalization, and business combinations (ASC 805) - Ability to self-direct in an unstructured environment that moves quickly, navigate ambiguity, and define your own agenda. We need to keep each as
- .
Now Pay: "The US base salary range for this full-time position is between $142,400 - $209,400 + bonus + benefits. As pay varies by location, your recruiter will share more about the specific salary range for your targeted location during the hiring process."
We need to preserve that as prose
. Now we must not include Benefits or Schedule sections. We also need to remove boilerplate: EEO statements, accommodation request, etc. So we will omit those paragraphs. Now ensure we do not include any filler like "commensurate with experience". Not present. Now output HTML fragment. Structure:
About the role
...
...
...
(maybe three paragraphs)Responsibilities
- ... ...
Requirements
- ...
Qualifications
- ...
Pay
...
Make sure no extra whitespace? It's fine. Now craft the paragraphs exactly as in text, preserving punctuation. Let's copy the About the role paragraphs: Paragraph1: "At GFiber, we believe that great internet has the power to drive innovation, strengthen communities, enable the impossible, and do all the everyday things that make all of our world go round. And the job of creating better internet is never done - so we’re growing! Our team is committed to building a place where people who want to make a difference can grow their careers and find their spot to belong. GFiber is an Alphabet company that brings Google Fiber and Google Fiber Webpass internet services to homes and businesses across the United States. Our teams are expanding as we connect more cities and people to exceptional internet." Paragraph2: "The application window will be open until at least July 26, 2026. This opportunity will remain online based on business needs which may be before or after the specified date." Paragraph3 (role description): "On the Controllership team you are a critical part of setting up the company for future financial success — enabling the business to move fast, while playing in control. You own the accounting for GFiber’s capital program: a multi-billion-dollar fiber network, from how a cost is coded at the PO through capitalization, close, disclosure, and audit. You set policy before transactions go live, own the systems and data that make capitalization correct upstream, and are the partner FP&A, Operations, and Tax rely on to avoid surprises." Now Responsibilities bullets exactly as given. Let's copy each bullet: - Own end-to-end ASC 360 PP&E and lease accounting, from capitalization costing (labor, material, allocations) through the full asset lifecycle to month-end close and reconciliations. - Maintain the capex-to-opex bridge to eliminate EBITDA surprises, support external audits, and partner cross-functionally with FP&A, Tax, and Ops on forecasting and commissioning. - Own lease accounting under ASC 842, from