Business Intelligence Engineer II, SCOT - Long Term Planning and Forecasting
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 as heading. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the description.
Key parts:
- Intro description about SCOT LTPF team, what they do.
- "SCOT LTPF is looking for a Business Intelligence Engineer to support the team."
- Description of role: LTPF BI Engineers build and maintain analytical tools supporting Topline, Inventory, and Capacity planning, engage with stakeholders.
- Ideal candidate experience: leading analytics projects including forecasting, business monitoring, BI, data visualization; mapping analytical solutions to business problems in ambiguous environments; track record making data easy to consume; extensive stakeholder and project management.
- Key job responsibilities (list bullet points). We'll need to put them under a Responsibilities section using - .
- "A day in the life" paragraph.
- Benefits paragraph: Amazon offers a full range of benefits... list benefits.
- "If you are not sure that every qualification on the list above describes you exactly, we'd still love to hear from you!" etc. That's more of encouragement; maybe part of About the team? Might be considered boilerplate? It's not boilerplate but it's generic encouragement; but we can include under About the role? Probably we can include under "About the role" or "About the team". However we need to avoid filler. It's substantive? It's encouraging applicants; maybe we can keep as a short paragraph under "About the role". But we need to decide.
- "About The Team" section: description of LTPF.
- Basic Qualifications list.
- Preferred Qualifications list.
- Amazon is an equal opportunity employer... that's EEO boilerplate; must remove.
- If you have a disability... accommodation; also boilerplate; remove.
- If the country/region you’re applying in isn’t listed... remove.
- The base salary range for this position is listed below... then salary range: USA, WA, Bellevue - 99,500.00 - 160,000.00 USD annually. Also mention sign-on payments and RSUs, final compensation determined based on factors, comprehensive benefits etc. This is Pay and Benefits info. We need to include Pay section if posting actually states them. Yes they give salary range. So we need a Pay section with that info. Benefits section already present; we can include Benefits with the list.
- Company - Amazon.com Services LLC Job ID: A10552186 - we should drop Job ID and maybe company name? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short paragraph with company name maybe? But they said we can drop it. Probably we can drop it entirely as minor metadata. The company name is not essential; but we could keep as a short p if we want. However they said "fold minor metadata into a short
or drop it." So we could include a short p with "Company: Amazon.com Services LLC". But maybe better to drop it to keep minimal. I'd drop it.
- Also note: "Amazon offers a full range of benefits that support you and eligible family members, including domestic partners and their children. Benefits can vary by location, the number of regularly scheduled hours you work, length of employment, and job status such as seasonal or temporary employment. The benefits that generally apply to regular, full-time employees include: Medical, Dental, and Vision Coverage Maternity and Parental Leave Options Paid Time Off (PTO) 401(k) Plan". That's benefits.
- Later they also mention comprehensive benefits including health insurance etc. That's duplicate; we should not duplicate. We'll keep the first benefits list; maybe combine but avoid duplication. We'll keep the first list.
- Pay: base salary range, sign-on payments and RSUs, final compensation determined based on experience, qualifications, location. Also mention comprehensive benefits (but we already have benefits). We'll include Pay section with salary range and note about sign-on payments and RSUs.
- Schedule: not mentioned; no schedule info. So we should not create Schedule section.
- Skills: not explicitly a section; but we could incorporate under Requirements or Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include based on content.
We have:
- About the role: could be the introductory paragraphs describing the team and role.
- Responsibilities: the list of key job responsibilities.
- Requirements: maybe Basic Qualifications.
- Qualifications: maybe Preferred Qualifications? Or we could combine Basic and Preferred under Requirements and Qualifications respectively.
- Skills: maybe not separate; we could omit if no specific skills section beyond qualifications.
- Benefits: we have.
- Pay: we have.
- Schedule: none.
- About the Team: we have a separate "About The Team" section; could be part of About the role or separate. Could treat as About the role (since it's about the team). But we have both an intro and an "About The Team". Might combine into About the role section.
We need to avoid filler like "commensurate with experience", "not specified", etc. Not present.
We must not repeat job title as heading.
We must output only HTML fragment, no /, no markdown.
Let's craft:
About the role
... intro about SCOT LTPF team and the Business Intelligence Engineer role ...
Maybe also include "About The Team" content inside same section or separate? Could add another About the team
but that might be redundant. The instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid having both About the role and About the team. But we could treat "About The Team" as part of About the role. However we have distinct content: "About The Team Long-Term Planning & Forecasting (LTPF) enables coordinated long-term planning..." That's substantive. Could be its own section About the team
. But the instruction list includes About the role, not About the team. However we can still use About the team
as a heading; it's not prohibited. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests examples, not exclusive list. So we can add About the team.
Thus we could have:
About the team
Long-Term Planning & Forecasting (LTPF) enables coordinated long-term planning ...
Then About the role
maybe not needed if we already described role in intro. But we need to avoid duplication. Perhaps we can combine intro and role description under About the role. Then About the team separate.
Let's decide:
Section About the role: includes description of what SCOT LTPF does and what the BI Engineer will do (the paragraph after "SCOT LTPF is looking for a Business Intelligence Engineer to support the team." and the following sentences about building tools, engaging stakeholders, ideal candidate experience, stakeholder management). That seems appropriate.
Section About the team: includes the "About The Team" paragraph.
Responsibilities: list of key job responsibilities.
Requirements: Basic Qualifications.
Qualifications: Preferred Qualifications.
Benefits: list.
Pay: salary range and sign-on/RSU note.
We should not include Skills unless we have specific skills; we could omit.
Now we need to ensure we preserve all substantive information. Let's extract.
Intro paragraph:
"Description Where will Amazon's growth come from next year? In five years? Which product lines are staged to quintuple in size, and which ones are mature? Are we investing enough in our infrastructure, or too much? How will our customers react to changes in prices, or selection, or delivery speed? The SCOT Long-Term Planning and Forecasting (LTPF) team works to answer these key questions. The Supply Chain Optimization Technology (SCOT) team owns Amazon's global inventory planning systems: SCOT decides what, when, where, and how much inventory to buy in order to meet customer needs as well as Amazon's business goals. We do this for millions of items, for hundreds of product lines worth billions of dollars of inventory world-wide. Our systems are built entirely in-house, and represent the forefront of automated large scale supply chain planning and optimization systems.. SCOT LTPF is responsible for long-term forecasting and planning across Topline, Inventory, and Capacity — helping Amazon plan key metrics including ordered units and GMS, inventory units and cost, and FC building capacity and topology (size and location). SCOT LTPF is looking for a Business Intelligence Engineer to support the team. LTPF BI Engineers build and maintain analytical tools supporting Topline, Inventory, and Capacity planning, and engage with internal stakeholders and external consumers of LTPF forecasts to ensure they have timely data in the right context to answer key business questions. The ideal candidate will have experience in leading analytics projects including but not limited to: forecasting, business monitoring, business intelligence and data visualization. The candidate should also have experience mapping analytical solutions to business problems in the most ambiguous environments with a track record of making data easy to consume for end users. This position will require extensive stakeholder and project management."
That's a lot; we need to preserve all substantive info. We'll put that in About the role paragraph(s). Might be long but okay.
Then "A day in the life LTPF BI Engineers focus on how our customers use our forecasts and plans, and ensuring it's as easy as possible to access and understand them. We serve on the front lines of forecast and plan validation as a proxy for our customers, making sure changes across Topline, Inventory, and Capacity are well understood and clearly communicated. We develop reports and data access points that answer key questions about forecast performance, inventory positioning, and capacity planning — and work with science and engineering teams to resolve forecast and planning questions."
We could include that as part of About the role or maybe a separate section "A day in the life". But not in heading list; we could incorporate into About the role as a paragraph.
Then Benefits paragraph: "Amazon offers a full range of benefits that support you and eligible family members, including domestic partners and their children. Benefits can vary by location, the number of regularly scheduled hours you work, length of employment, and job status such as seasonal or temporary employment. The benefits that generally apply to regular, full-time employees include: Medical, Dental, and Vision Coverage Maternity and Parental Leave Options Paid Time Off (PTO) 401(k) Plan"
We need to format as - for list. So we need to extract list items: Medical, Dental, and Vision Coverage; Maternity and Parental Leave Options; Paid Time Off (PTO); 401(k) Plan.
We'll put those in
.
Then later they mention comprehensive benefits again; we can ignore duplicate.
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. 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. USA, WA, Bellevue - 99,500.00 - 160
or drop it. So we could include a short paragraph with company name maybe? But they said we can drop it. Probably we can drop it entirely as minor metadata. The company name is not essential; but we could keep as a short p if we want. However they said "fold minor metadata into a short
or drop it." So we could include a short p with "Company: Amazon.com Services LLC". But maybe better to drop it to keep minimal. I'd drop it. - Also note: "Amazon offers a full range of benefits that support you and eligible family members, including domestic partners and their children. Benefits can vary by location, the number of regularly scheduled hours you work, length of employment, and job status such as seasonal or temporary employment. The benefits that generally apply to regular, full-time employees include: Medical, Dental, and Vision Coverage Maternity and Parental Leave Options Paid Time Off (PTO) 401(k) Plan". That's benefits. - Later they also mention comprehensive benefits including health insurance etc. That's duplicate; we should not duplicate. We'll keep the first benefits list; maybe combine but avoid duplication. We'll keep the first list. - Pay: base salary range, sign-on payments and RSUs, final compensation determined based on experience, qualifications, location. Also mention comprehensive benefits (but we already have benefits). We'll include Pay section with salary range and note about sign-on payments and RSUs. - Schedule: not mentioned; no schedule info. So we should not create Schedule section. - Skills: not explicitly a section; but we could incorporate under Requirements or Qualifications. The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include based on content. We have: - About the role: could be the introductory paragraphs describing the team and role. - Responsibilities: the list of key job responsibilities. - Requirements: maybe Basic Qualifications. - Qualifications: maybe Preferred Qualifications? Or we could combine Basic and Preferred under Requirements and Qualifications respectively. - Skills: maybe not separate; we could omit if no specific skills section beyond qualifications. - Benefits: we have. - Pay: we have. - Schedule: none. - About the Team: we have a separate "About The Team" section; could be part of About the role or separate. Could treat as About the role (since it's about the team). But we have both an intro and an "About The Team". Might combine into About the role section. We need to avoid filler like "commensurate with experience", "not specified", etc. Not present. We must not repeat job title as heading. We must output only HTML fragment, no /, no markdown. Let's craft:
About the role
... intro about SCOT LTPF team and the Business Intelligence Engineer role ...
Maybe also include "About The Team" content inside same section or separate? Could add anotherAbout the team
but that might be redundant. The instruction says use headings for sections like About the role, Responsibilities, etc. It doesn't forbid having both About the role and About the team. But we could treat "About The Team" as part of About the role. However we have distinct content: "About The Team Long-Term Planning & Forecasting (LTPF) enables coordinated long-term planning..." That's substantive. Could be its own sectionAbout the team
. But the instruction list includes About the role, not About the team. However we can still useAbout the team
as a heading; it's not prohibited. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests examples, not exclusive list. So we can add About the team.
Thus we could have:
About the team
Long-Term Planning & Forecasting (LTPF) enables coordinated long-term planning ...
ThenAbout the role
maybe not needed if we already described role in intro. But we need to avoid duplication. Perhaps we can combine intro and role description under About the role. Then About the team separate. Let's decide: Section About the role: includes description of what SCOT LTPF does and what the BI Engineer will do (the paragraph after "SCOT LTPF is looking for a Business Intelligence Engineer to support the team." and the following sentences about building tools, engaging stakeholders, ideal candidate experience, stakeholder management). That seems appropriate. Section About the team: includes the "About The Team" paragraph. Responsibilities: list of key job responsibilities. Requirements: Basic Qualifications. Qualifications: Preferred Qualifications. Benefits: list. Pay: salary range and sign-on/RSU note. We should not include Skills unless we have specific skills; we could omit. Now we need to ensure we preserve all substantive information. Let's extract. Intro paragraph: "Description Where will Amazon's growth come from next year? In five years? Which product lines are staged to quintuple in size, and which ones are mature? Are we investing enough in our infrastructure, or too much? How will our customers react to changes in prices, or selection, or delivery speed? The SCOT Long-Term Planning and Forecasting (LTPF) team works to answer these key questions. The Supply Chain Optimization Technology (SCOT) team owns Amazon's global inventory planning systems: SCOT decides what, when, where, and how much inventory to buy in order to meet customer needs as well as Amazon's business goals. We do this for millions of items, for hundreds of product lines worth billions of dollars of inventory world-wide. Our systems are built entirely in-house, and represent the forefront of automated large scale supply chain planning and optimization systems.. SCOT LTPF is responsible for long-term forecasting and planning across Topline, Inventory, and Capacity — helping Amazon plan key metrics including ordered units and GMS, inventory units and cost, and FC building capacity and topology (size and location). SCOT LTPF is looking for a Business Intelligence Engineer to support the team. LTPF BI Engineers build and maintain analytical tools supporting Topline, Inventory, and Capacity planning, and engage with internal stakeholders and external consumers of LTPF forecasts to ensure they have timely data in the right context to answer key business questions. The ideal candidate will have experience in leading analytics projects including but not limited to: forecasting, business monitoring, business intelligence and data visualization. The candidate should also have experience mapping analytical solutions to business problems in the most ambiguous environments with a track record of making data easy to consume for end users. This position will require extensive stakeholder and project management." That's a lot; we need to preserve all substantive info. We'll put that in About the role paragraph(s). Might be long but okay. Then "A day in the life LTPF BI Engineers focus on how our customers use our forecasts and plans, and ensuring it's as easy as possible to access and understand them. We serve on the front lines of forecast and plan validation as a proxy for our customers, making sure changes across Topline, Inventory, and Capacity are well understood and clearly communicated. We develop reports and data access points that answer key questions about forecast performance, inventory positioning, and capacity planning — and work with science and engineering teams to resolve forecast and planning questions." We could include that as part of About the role or maybe a separate section "A day in the life". But not in heading list; we could incorporate into About the role as a paragraph. Then Benefits paragraph: "Amazon offers a full range of benefits that support you and eligible family members, including domestic partners and their children. Benefits can vary by location, the number of regularly scheduled hours you work, length of employment, and job status such as seasonal or temporary employment. The benefits that generally apply to regular, full-time employees include: Medical, Dental, and Vision Coverage Maternity and Parental Leave Options Paid Time Off (PTO) 401(k) Plan" We need to format as- for list. So we need to extract list items: Medical, Dental, and Vision Coverage; Maternity and Parental Leave Options; Paid Time Off (PTO); 401(k) Plan.
We'll put those in
- .
Then later they mention comprehensive benefits again; we can ignore duplicate.
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. 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. USA, WA, Bellevue - 99,500.00 - 160