Corporate FP&A Senior Analyst

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "What We Are Looking For", "Required Qualifications", "Desirable Qualifications", "Working at Aurora", "Our commitment to safety", "Our commitment to inclusion". But we must only include sections when posting has real, specific content. Also we must use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The list includes specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must map content map to these headings. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when appropriate. Not repeat job title as heading. Not include Job ID etc. Remove boilerplate. We need to preserve all substantive information. So we need to extract relevant content and place under appropriate headings. We have: - About the role: Could be description of role: "As a Corporate FP&A Senior Analyst, a high-impact individual contributor role, you will directly support Aurora's company-wide financial planning and reporting processes — partnering with functional executive leaders across the organization to build budgets, manage capital allocation, and deliver key analytical deliverables for C-suite and Board-level decisions." Also list of responsibilities: bullet points after "In this role, you will". Those are responsibilities. Thus we can have:

About the role

As a Corporate FP&A Senior Analyst, a high-impact individual contributor role, you will directly support Aurora's company-wide financial planning and reporting processes — partnering with functional executive leaders across the organization to build budgets, manage capital allocation, and deliver key analytical deliverables for C-suite and Board-level decisions.

Then

Responsibilities

with

• list each bullet. Bullets: - Drive the consolidated company-wide annual budget, quarterly re-forecasts, and long-range financial planning (3-statement modeling) across corporate and operating functions; - Partner directly with department leaders to build, maintain, and optimize operational expenditure (Opex), Capital Expenditure (Capex), and Headcount drivers; - Prepare comprehensive variance analysis (Actuals vs. Plan), trend reports, and operational insight packages for executive leadership during monthly and quarterly close cycles; - Support the preparation of quarterly Board of Directors presentations, executive financial decks, and quarterly earnings support materials; - Establish, monitor, and refine company-wide corporate financial KPIs to identify efficiency opportunities and optimize operating leverage; - Present corporate financial performance, variance drivers, and capital allocation recommendations to Finance and operational leadership; - Review FP&A SOPs, financial governance workflows, and budgeting systems to implement scalable best practices across the organization; - Drive system automation, data integrity, and model integration across corporate FP&A planning platforms (e.g., Pigment) and accounting systems (e.g., NetSuite); - As a member of the Finance COE, flex across high-impact concurrent projects and strategic finance workstreams as corporate priorities evolve. We need to preserve punctuation; maybe remove trailing semicolons? Keep as is. Next

  Requirements

  maybe combine Required Qualifications and Desirable Qualifications? The instruction says we can have Requirements, Qualifications, Skills sections. We have Required Qualifications and Desirable Qualifications. Could map Required Qualifications to

  Requirements

  (or Qualifications). Desirable Qualifications could go under

  Skills

  or

  Qualifications

  but we should not duplicate. Perhaps we put Required Qualifications under

  Requirements

  and Desirable Qualifications under

  Skills

  . Or we could have

  Qualifications

  with both required and desirable? But instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Required and Desirable into one Qualifications section, but we need to differentiate? Could list required then desirable as sub-bullets? Might be okay. But we also have "Working at Aurora", "Our commitment to safety", "Our commitment to inclusion". Those could be under Benefits? Not exactly. Benefits section is for pay, benefits, schedule. We have Pay info: salary ranges for locations. Also mention annual bonus, equity compensation, benefits. Also schedule: "Aurorans are expected to work from the office at least 3 days per week, with some roles requiring more frequent in-office presence, up to 5 days per week, based on operational needs." So we can have Pay, Benefits, Schedule sections. Thus we need sections: About the role, Responsibilities, Requirements (or Qualifications), Pay, Benefits, Schedule. Possibly also Skills? But we can incorporate desirable qualifications into Skills. Let's decide: - About the role: description. - Responsibilities: list. - Requirements: Required Qualifications. - Skills: Desirable Qualifications (SQL, BI, CPA, CFA, MBA, industry experience, investor relations). - Pay: salary ranges. - Benefits: annual bonus, equity compensation, benefits (general). - Schedule: in-office expectation. We must not create sections with filler like "commensurate with experience". We have real content. We must not include boilerplate like "Who We Are", "What We Are Looking For", "Working at Aurora", "Our commitment to safety", "Our commitment to inclusion". Those are not in the allowed headings list, but we could incorporate their content into appropriate sections if relevant. For example, "Who We Are" is about Aurora mission; could be part of About the role? Not exactly role but company overview. Might be considered not needed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that info somewhere. If we don't have a heading for it, we could put it in a

  under About the role? But About the role is supposed to be about the role, not company. However we could add a

  about company under About the role? Might be okay but could be considered not strictly role. However we could create a section "About the company" but not allowed heading. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to use other headings if needed, but they gave examples. Safer to stick to those headings and embed other info within them. Thus we can include company mission in About the role paragraph: "Aurora’s mission is to deliver the benefits of self-driving technology safely, quickly, and broadly. The Aurora Driver will create a new era in mobility and logistics..." etc. That is substantive. Similarly, "Working at Aurora" etc could go under Benefits? Not exactly. Could be under Benefits? Or we could add a

  under Benefits about culture? But Benefits is for compensation/benefits. However we could add a separate section "Culture" but not allowed. Maybe we can put under Benefits as "Working at Aurora" describing work expectations, but schedule already covers in-office days. Culture and values could be under Benefits? Might be a stretch. Alternatively, we could create a section "About the company" using

  but not in list; risk of violating instruction. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, but it says use those for section headings. It might be interpreted as you should use those headings when applicable. It doesn't forbid other headings, but to be safe, we should try to fit all substantive info into those categories. Let's see if we can fit: - Who We Are (mission) -> About the role (maybe as introductory paragraph). - What We Are Looking For (description of COE and role) -> Already covered in About the role and Responsibilities. - Required Qualifications -> Requirements. - Desirable Qualifications -> Skills. - Working at Aurora (values, in-office expectation) -> Could go under Benefits? Not exactly. Could go under Schedule (in-office expectation) and maybe Benefits (culture). But we have separate schedule bullet. Values could be under Benefits? Not ideal but we could add a

  under Benefits about culture and values. The instruction: Benefits section only if posting actually states them. The posting does state benefits: "The successful candidate will also be eligible for an annual bonus, equity compensation, and benefits." Also mentions working at Aurora values. So we can include that in Benefits. - Our commitment to safety and inclusion -> Could also go under Benefits? Or maybe under a separate section but we don't have heading. Could incorporate into Benefits as part of company policies. Might be okay. Thus final sections:

  About the role

  ... include mission and role description.

  Responsibilities

  ...

  Requirements

  ...
  (Required Qualifications)

  Skills

  ...
  (Desirable Qualifications)

  Pay

  ... salary ranges.

  Benefits

  ...
  (annual bonus, equity compensation, benefits, working at Aurora values, safety commitment, inclusion commitment)

  Schedule

  ... in-office expectation.

  We need to ensure we don't repeat info. Let's extract exact text. From posting: Who We Are: "Aurora’s mission is to deliver the benefits of self-driving technology safely, quickly, and broadly. The Aurora Driver will create a new era in mobility and logistics, one that will bring a safer, more efficient, and more accessible future to everyone. At Aurora, you will tackle massively complex problems alongside other passionate, intelligent individuals, growing as an expert while expanding your knowledge. For the latest news from Aurora, visit aurora.tech or follow us on LinkedIn." What We Are Looking For: "Aurora's Finance Center of Excellence (COE) functions as an internal strategic advisory team. Rather than sitting permanently within a single siloed function, COE analysts build 360-degree business fluency across Aurora's business and are deployed where their analytical skills and business acumen add the most strategic value, gaining direct exposure to senior executive leadership while solving Aurora's highest-priority growth challenges. As a Corporate FP&A Senior Analyst, a high-impact individual contributor role, you will directly support Aurora's company-wide financial planning and reporting processes — partnering with functional executive leaders across the organization to build budgets, manage capital allocation, and deliver key analytical deliverables for C-suite and Board-level decisions. We're looking for a self-motivated analyst who excels at translating complex operational details into clear financial narratives for executive audiences." Then responsibilities list. Required Qualifications: "5+ years of relevant experience in Corporate FP&A, Strategic Finance, or Investment Banking/Corporate Finance at a public or high-growth company; public company experience with quarterly reporting cycles required;Degree in Finance or a related quantitative field such as Business, Economics, Math, or Statistics;Strong proficiency in corporate budgeting, 3-statement financial modeling, variance analysis, and accounting consolidation principles;Proven track record of partnering with cross-functional executive stakeholders to manage budgets and streamline planning workflows;Ability to pivot seamlessly between granular operational inputs and macro executive messaging;Hands-on experience with modern financial planning software (e.g., Pigment, Anaplan, Adaptive) and ERP systems (e.g., NetSuite);Exceptional written and verbal communication skills with demonstrated experience building executive presentation decks;Strong analytical capability and rigorous attention to detail;Comfort operating within a Center of Excellence model, leading multiple projects across cross-functional priorities." Desirable Qualifications: "Hands-on experience with SQL