Senior Finance Analyst, NACF Reporting and Analytics, NACF Reporting and Analytics
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate (EEO, etc). Must preserve all substantive info.
We need to parse the description.
Key sections:
- About the role: description of role, maybe first paragraph: "Amazon’s North American Customer Fulfillment (NACF) Finance is looking for a Senior Finance Analyst to be the trusted finance partner supporting finance reporting and analytics." plus description of Amazon network etc. Could be "About the role" or "About the team"? The posting includes "About The Team". We'll treat that as "About the team". Also there is "A day in the life". Could be separate section? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We have:
- Responsibilities: "Key job responsibilities" repeated multiple times. We need to extract responsibilities bullet points.
- Qualifications: BASIC QUALIFICATIONS and PREFERRED QUALIFICATIONS.
- Skills: maybe from preferred qualifications: knowledge of Tableau, SQL, etc.
- Benefits: description of benefits: health insurance, 401(k) matching, paid time off, parental leave, etc. Also mention sign-on payments and RSUs.
- Pay: salary ranges per location.
- Schedule: maybe mention "Some travel may be required as part of this role." Not exactly schedule. Could be "Schedule" not present. So we should not include Schedule unless there is real content. There's no explicit schedule like full-time, etc. So omit.
- About the role: maybe combine initial description and "About The Team" and "A day in the life". Could be separate sections: "About the role" and "About the team". But instruction says prefer few substantive sections over many thin ones. We could combine role description and team info into "About the role". Or we could have "About the role" and "About the team" as separate if both have content. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have both if they have content.
We need to avoid duplication. The posting repeats many paragraphs. We need to preserve all substantive information but not duplicate lines. So we need to deduplicate.
Let's extract unique substantive sentences.
First paragraph: "Amazon’s North American Customer Fulfillment (NACF) Finance is looking for a Senior Finance Analyst to be the trusted finance partner supporting finance reporting and analytics. Amazon operates the most complex retail networks in the world, delivering billions of packages to hundreds of millions of homes and businesses annually – and we have nearly doubled the size of our fulfillment network over the last two years! Come be part of transforming how finance supports the business and join a dedicated team committed to building the skills, tools and processes enabling our finance teams to navigate the worlds most sophisticated supply chain!"
Second paragraph: "Key job responsibilities Business Finance Support: Leverage operations finance expertise to lead reporting and uphold financial data accuracy. Partner with cross-functional teams on process/product requirements. Provide analytical insights and recommendations to leadership. Identify opportunities to optimize processes while raising the bar. Controllership: Lead reporting, drive data accuracy, provide deeper insight, drive partnership with OPS, Field finance and PE Teams. Resolve complex data integrity issues through collaboration. Design and implement scalable, auditable data analysis processes. Communication: Communicate financial data and reports effectively through active listening and audience-appropriate delivery. Build strategic partnerships with Finance Leaders, Operations Stakeholders, and Program/Product Managers."
Then "A day in the life As a Senior Finance Analyst in the NACF Finance reporting and analytics Team, you will work in a fast-paced, high-energy environment. You’ll partner with various OPs, Finance and PE teams in NA to drive (1) finance reporting with continuous improvements (2) deep dive into data to ensure accuracy (3) lead implementation, change management and adoption of new tools and processes. Some travel may be required as part of this role."
Then "About The Team This role will partner closely within finance teams in North America, Operations, PE finance teams, Planning teams of Under The Roof Operations Finance. This role plays a critical role in leading Financial reporting, data upholding, deep diving, developing scalable reporting structure (including dashboards, automated reports). Additionally this role will lead process changes within finance to enable better reporting, insights to allow leaders to take strategic decisions."
Then repeated "Key job responsibilities ..." again (duplicate). Then repeated "Communication:" etc. Then repeated "A day in the life". Then repeated "About The Team". So we need to deduplicate.
Then "BASIC QUALIFICATIONS 3+ years of tax, finance or a related analytical field experience Bachelor's degree"
Then "PREFERRED QUALIFICATIONS 4+ years of participating in continuous improvement projects in your team to scale and improve controllership with measurable results experience MBA, or CPA Knowledge of Tableau Experience working with large-scale data mining and reporting tools (examples: SQL, MS Access, Essbase, Cognos) and other financial systems (examples: Oracle, SAP, Lawson, JD Edwards)"
Then EEO boilerplate to remove.
Then compensation: "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location salary ranges: list of USA, state, city - range.
Then "Company - Amazon.com Services LLC Job ID: A10539879" (remove Job ID).
We need to output HTML with sections.
Potential sections:
- About the role (maybe combine initial description and "A day in the life" and "About The Team"? But we could separate: About the role (initial description), Responsibilities, A day in the life (maybe under Responsibilities?), About the team, Qualifications, Skills, Benefits, Pay.
But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not mandatory to use exactly those; we can use those headings if content matches.
We have:
- About the role: we have initial description about role and mission. Could be "About the role".
- Responsibilities: we have bullet points under Business Finance Support, Controllership, Communication.
- Requirements: maybe we could use "Requirements" for basic qualifications? But they also have "Qualifications". The examples include both Requirements and Qualifications. We could treat BASIC QUALIFICATIONS as "Requirements" and PREFERRED QUALIFICATIONS as "Qualifications". Or we could have one "Qualifications" section with both basic and preferred. But we need to avoid thin sections. Perhaps combine into one "Qualifications" with subheadings? But we cannot add extra headings beyond h3? We could use for Qualifications and then inside have
for basic and
for preferred. That's okay. - Skills: we could extract from preferred qualifications: knowledge of Tableau, SQL, etc. Could be a Skills section. - Benefits: we have benefits description. - Pay: we have salary ranges. - Schedule: not present, so omit. We also have "About The Team" content. Could be part of About the role or separate "About the team". Since we have "About the role" already, we could add a separate "About the team" heading if we want. But instruction says prefer few substantive sections over many thin ones. So maybe merge team info into About the role. Thus sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Now we need to ensure we preserve all substantive information. Let's extract unique content for each. About the role: - Amazon’s North American Customer Fulfillment (NACF) Finance is looking for a Senior Finance Analyst to be the trusted finance partner supporting finance reporting and analytics. - Amazon operates the most complex retail networks in the world, delivering billions of packages to hundreds of millions of homes and businesses annually – and we have nearly doubled the size of our fulfillment network over the last two years! - Come be part of transforming how finance supports the business and join a dedicated team committed to building the skills, tools and processes enabling our finance teams to navigate the worlds most sophisticated supply chain! We could also include "A day in the life" details: fast-paced, high-energy environment; partner with various OPs, Finance and PE teams in NA to drive finance reporting with continuous improvements, deep dive into data to ensure accuracy, lead implementation, change management and adoption of new tools and processes; some travel may be required. And "About The Team": partner closely within finance teams in North America, Operations, PE finance teams, Planning teams of Under The Roof Operations Finance; plays a critical role in leading Financial reporting, data upholding, deep diving, developing scalable reporting structure (including dashboards, automated reports); lead process changes within finance to enable better reporting, insights to allow leaders to take strategic decisions. We can combine all that into About the role. Now Responsibilities: list bullet points. From the responsibilities section: Business Finance Support: - Leverage operations finance expertise to lead reporting and uphold financial data accuracy. - Partner with cross-functional teams on process/product requirements. - Provide analytical insights and recommendations to leadership. - Identify opportunities to optimize processes while raising the bar. Controllership: - Lead reporting, drive data accuracy, provide deeper insight, drive partnership with OPS, Field finance and PE Teams. - Resolve complex data integrity issues through collaboration. - Design and implement scalable, auditable data analysis processes. Communication: - Communicate financial data and reports effectively through active listening and audience-appropriate delivery. - Build strategic partnerships with Finance Leaders, Operations Stakeholders, and Program/Product Managers. We should ensure we don't duplicate. Now Qualifications: Basic: - 3+ years of tax, finance or a related analytical field experience - Bachelor's degree Preferred: - 4+ years of participating in continuous improvement projects in your team to scale and improve controllership with measurable results - MBA, or CPA - Knowledge of Tableau - Experience working with large-scale data mining and reporting tools (examples: SQL, MS Access, Essbase, Cognos) and other financial systems (examples: Oracle, SAP, Lawson, JD Edwards) We could also include "Experience working with large-scale data mining and reporting tools" as part of skills. Now Skills: maybe extract knowledge of Tableau, SQL, MS Access, Essbase, Cognos, Oracle, SAP, Lawson, JD Edwards. Also maybe "continuous improvement projects". But we could just put skills as a list. Better to have Skills section listing: Tableau, SQL, MS Access, Essbase, Cognos, Oracle, SAP, Lawson, JD Edwards, continuous improvement experience, MBA/CPA (though those are qualifications). But we can keep skills separate: knowledge of Tableau, experience with SQL, MS Access, Essbase, Cognos, Oracle, SAP, Lawson, JD Edwards. Now Benefits: - Sign-on payments and restricted stock units (RSUs) - Comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage) - 401(k) matching - Paid time off - Parental leave We should also mention "Learn