Finance Manager, Advertising Product Finance
Amazon · New York, United States · 1 mo ago
AccountingFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, accommodation, etc. Must preserve substantive info.
Let's parse the description.
First paragraph: "Amazon Advertising seeks a Finance Manager to directly support the product team in charge of the Video Advertising business, and collaborate with several internal stakeholders across sales, supply, and device teams. This is a fast growth business that is continuously expanding and launching new products and services on a frequent basis. This role will play a key role in evaluating ambiguous and complex monetization opportunities, designing new or enhance reporting and models that make our data more actionable, developing and communicating business insights through data analytics, and owns reporting functions during the various business review, planning, and forecasting phases in finance."
That's about the role. Could be "About the role" heading.
Next: "Key job responsibilities The successful candidate will be highly motivated and have the ability to tackle multiple projects and efficiently execute deliverables; move and adapt quickly to new information or change in strategic direction; can dive deep into data to understand and identify business trends; is detail oriented and has the ability to work well with cross-functional business and finance stakeholders; has strong oral and written communication skills and solid business acumen capable of driving results and improving processes; can think clearly, analyze quantitatively, problem-solve and prioritize."
That's responsibilities.
Next: "About The Team The DAV advertising product finance team directly supports Amazon Device, Audio, and Video advertising demand-side platform (DSP) product teams. We also act as internal partners to support and drive our ad sales and supply teams. Our focus is to accelerate top-line revenue and improve profitability by evaluating overall ad supply monetization and utilization, product feature or sales package adoption, campaign performance, and other various product drivers of growth. DAV product finance manages our business priorities through modeling new opportunities and initiatives, developing key operational metric reports with actionable insights, and building input-based forecasts."
That could be "About the team" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About The Team" could be considered part of "About the role" or maybe we can treat as "About the role" includes team description. We'll include it under About the role.
Next: "Basic Qualifications 5+ years of tax, finance or a related analytical field experience Bachelor's degree"
That's Requirements (basic qualifications). Next: "Preferred Qualifications 6+ years of identifying incomplete or inaccurate data, identifying the root cause and creating/implementing an escalation plan experience 6+ years of solving complex business challenges by delivering accurate and timely financial models, analysis, and recommendations that have a proven impact on business (e.g., financial savings, operational improvements, or customer benefits) experience MBA, or CPA Knowledge of SQL/ETL 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) Experience delivering forecasting, budgeting, and variance analysis, and data interpretation of results"
That's Qualifications (preferred). Also includes skills like SQL, etc. Could be Skills section.
We need to decide: we have Requirements (basic qualifications) and Qualifications (preferred). Also Skills could be extracted from preferred qualifications: Knowledge of SQL/ETL, experience with large-scale data mining and reporting tools, etc. But we can also put those under Qualifications. The instruction: Use sections only when posting has real specific content. We can have Requirements and Qualifications sections. Skills maybe not needed if covered.
Benefits: The posting mentions: "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."
That's benefits content. Also Pay: "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." Then they list salary ranges: "USA, NY, New York - 104,900.00 - 179,500.00 USD annually USA, WA, SEATTLE - 95,400.00 - 163,200.00 USD annually". That's pay info. So we need Pay section with those ranges.
Schedule: Not mentioned. So we should not include Schedule section.
We must not include boilerplate like EEO, accommodation, etc. Also remove duplicated lines.
We need to output only HTML fragment, no /. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide what to put as lists.
Responsibilities: The bullet points are semicolon-separated list. We can convert to
- each item.
Requirements: Basic Qualifications: "5+ years of tax, finance or a related analytical field experience" and "Bachelor's degree". Could be list.
Qualifications: Preferred Qualifications: many items. Could be list.
Skills: maybe we could extract skills from preferred qualifications: Knowledge of SQL/ETL, Experience working with large-scale data mining and reporting tools (SQL, MS Access, Essbase, Cognos), Experience with other financial systems (Oracle, SAP, Lawson, JD Edwards), Experience delivering forecasting, budgeting, variance analysis, data interpretation. But we could also just put them under Qualifications. However we have both Requirements and Qualifications sections; Skills could be separate if we want. But we need to avoid thin sections. The preferred qualifications already cover skills; we could put them under Qualifications and not have a separate Skills section. That would be fine.
Benefits: list items.
Pay: we need to present salary ranges. Could be
with the ranges.
We must not include headings with filler text. Ensure we only include sections with real content.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if any content for "About the role" includes the initial paragraphs plus About The Team. We'll combine.
Now craft HTML.
We'll start with
About the role
then containing prose: combine the initial description and About The Team.
But we need to avoid too long paragraph? It's fine.
Let's write:
About the role
Amazon Advertising seeks a Finance Manager to directly support the product team in charge of the Video Advertising business, and collaborate with several internal stakeholders across sales, supply, and device teams. This is a fast growth business that is continuously expanding and launching new products and services on a frequent basis. This role will play a key role in evaluating ambiguous and complex monetization opportunities, designing new or enhanced reporting and models that make our data more actionable, developing and communicating business insights through data analytics, and owning reporting functions during the various business review, planning, and forecasting phases in finance. The DAV advertising product finance team directly supports Amazon Device, Audio, and Video advertising demand-side platform (DSP) product teams. We also act as internal partners to support and drive our ad sales and supply teams. Our focus is to accelerate top-line revenue and improve profitability by evaluating overall ad supply monetization and utilization, product feature or sales package adoption, campaign performance, and other various product drivers of growth. DAV product finance manages our business priorities through modeling new opportunities and initiatives, developing key operational metric reports with actionable insights, and building input-based forecasts.
Now Responsibilities:
Responsibilities
- Highly motivated and able to tackle multiple projects and efficiently execute deliverables
- Move and adapt quickly to new information or change in strategic direction
- Dive deep into data to understand and identify business trends
- Detail oriented and able to work well with cross-functional business and finance stakeholders
- Strong oral and written communication skills and solid business acumen capable of driving results and improving processes
- Think clearly, analyze quantitatively, problem-solve and prioritize
Requirements:
Requirements
- 5+ years of tax, finance or a related analytical field experience
- Bachelor's degree
Qualifications:
Qualifications
- 6+ years of identifying incomplete or inaccurate data, identifying the root cause and creating/implementing an escalation plan
- 6+ years of solving complex business challenges by delivering accurate and timely financial models, analysis, and recommendations that have a proven impact on business (e.g., financial savings, operational improvements, or customer benefits)
- MBA or CPA
- Knowledge of SQL/ETL
- Experience working with large-scale data mining and reporting tools (examples: SQL, MS Access, Essbase, Cognos)
- Experience with other financial systems (examples: Oracle, SAP, Lawson, JD Edwards)
- Experience delivering forecasting, budgeting, and variance analysis, and data interpretation of results
Benefits:
Benefits
- Sign-on payments and restricted stock units (RSUs)
- Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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
Pay:
Pay
Base salary ranges: USA, NY, New York – $104,900.00 – $179,500.00 USD annually; USA, WA, Seattle – $95,400.00 – $163,200.00 USD annually. Final compensation based on experience, qualifications, and location, and includes sign-on payments and RSUs.
We should not include Schedule.
Check for any duplicated content: We included sign-on payments and RSUs both in Benefits and Pay. That's okay; they appear in both places but it's not duplicated exactly; but we might want to avoid duplication. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It's okay to mention in both sections if it's in original. But we could keep sign-on payments and RSUs only in Benefits, and Pay section just base salary ranges. However the original says "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." So sign-on payments and RSUs are part of compensation package, not strictly base salary. Could be in Benefits. We'll keep them in Benefits only, and Pay section just base salary ranges. Let's adjust.
Thus Benefits list includes sign-on payments and RSUs.
Pay section only base salary ranges.
Now ensure no boilerplate: removed EEO, accommodation, etc.
Check for any leftover like "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; we should remove as it's application instruction? It's not a core benefit but a link; we
for prose. We need to decide what to put as lists. Responsibilities: The bullet points are semicolon-separated list. We can convert to
- each item.
Requirements: Basic Qualifications: "5+ years of tax, finance or a related analytical field experience" and "Bachelor's degree". Could be list.
Qualifications: Preferred Qualifications: many items. Could be list.
Skills: maybe we could extract skills from preferred qualifications: Knowledge of SQL/ETL, Experience working with large-scale data mining and reporting tools (SQL, MS Access, Essbase, Cognos), Experience with other financial systems (Oracle, SAP, Lawson, JD Edwards), Experience delivering forecasting, budgeting, variance analysis, data interpretation. But we could also just put them under Qualifications. However we have both Requirements and Qualifications sections; Skills could be separate if we want. But we need to avoid thin sections. The preferred qualifications already cover skills; we could put them under Qualifications and not have a separate Skills section. That would be fine.
Benefits: list items.
Pay: we need to present salary ranges. Could be
with the ranges. We must not include headings with filler text. Ensure we only include sections with real content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any content for "About the role" includes the initial paragraphs plus About The Team. We'll combine. Now craft HTML. We'll start with
About the role
thencontaining prose: combine the initial description and About The Team. But we need to avoid too long paragraph? It's fine. Let's write:
About the role
Amazon Advertising seeks a Finance Manager to directly support the product team in charge of the Video Advertising business, and collaborate with several internal stakeholders across sales, supply, and device teams. This is a fast growth business that is continuously expanding and launching new products and services on a frequent basis. This role will play a key role in evaluating ambiguous and complex monetization opportunities, designing new or enhanced reporting and models that make our data more actionable, developing and communicating business insights through data analytics, and owning reporting functions during the various business review, planning, and forecasting phases in finance. The DAV advertising product finance team directly supports Amazon Device, Audio, and Video advertising demand-side platform (DSP) product teams. We also act as internal partners to support and drive our ad sales and supply teams. Our focus is to accelerate top-line revenue and improve profitability by evaluating overall ad supply monetization and utilization, product feature or sales package adoption, campaign performance, and other various product drivers of growth. DAV product finance manages our business priorities through modeling new opportunities and initiatives, developing key operational metric reports with actionable insights, and building input-based forecasts.
Now Responsibilities:Responsibilities
- Highly motivated and able to tackle multiple projects and efficiently execute deliverables
- Move and adapt quickly to new information or change in strategic direction
- Dive deep into data to understand and identify business trends
- Detail oriented and able to work well with cross-functional business and finance stakeholders
- Strong oral and written communication skills and solid business acumen capable of driving results and improving processes
- Think clearly, analyze quantitatively, problem-solve and prioritize
Requirements
- 5+ years of tax, finance or a related analytical field experience
- Bachelor's degree
Qualifications
- 6+ years of identifying incomplete or inaccurate data, identifying the root cause and creating/implementing an escalation plan
- 6+ years of solving complex business challenges by delivering accurate and timely financial models, analysis, and recommendations that have a proven impact on business (e.g., financial savings, operational improvements, or customer benefits)
- MBA or CPA
- Knowledge of SQL/ETL
- Experience working with large-scale data mining and reporting tools (examples: SQL, MS Access, Essbase, Cognos)
- Experience with other financial systems (examples: Oracle, SAP, Lawson, JD Edwards)
- Experience delivering forecasting, budgeting, and variance analysis, and data interpretation of results
Benefits
- Sign-on payments and restricted stock units (RSUs)
- Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, 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
Pay
Base salary ranges: USA, NY, New York – $104,900.00 – $179,500.00 USD annually; USA, WA, Seattle – $95,400.00 – $163,200.00 USD annually. Final compensation based on experience, qualifications, and location, and includes sign-on payments and RSUs.
We should not include Schedule. Check for any duplicated content: We included sign-on payments and RSUs both in Benefits and Pay. That's okay; they appear in both places but it's not duplicated exactly; but we might want to avoid duplication. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It's okay to mention in both sections if it's in original. But we could keep sign-on payments and RSUs only in Benefits, and Pay section just base salary ranges. However the original says "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." So sign-on payments and RSUs are part of compensation package, not strictly base salary. Could be in Benefits. We'll keep them in Benefits only, and Pay section just base salary ranges. Let's adjust. Thus Benefits list includes sign-on payments and RSUs. Pay section only base salary ranges. Now ensure no boilerplate: removed EEO, accommodation, etc. Check for any leftover like "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link; we should remove as it's application instruction? It's not a core benefit but a link; we