Senior Business Intelligence Engineer, North America Supply Chain Execution Strategy
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading.
We must not put Job ID etc.
We must preserve ALL substantive information; do not invent or summarize away detail.
We need to include Pay section only if posting actually states them. Yes, salary ranges given. So include Pay.
Benefits: they list comprehensive benefits; include Benefits section.
Schedule: no info, so omit.
Skills: we could extract from Basic Qualifications: programming to extract, transform and clean large data sets; AWS technologies; theory and practice of information retrieval, data science, machine learning and data mining; Cloud Storage and Computing technologies such as AWS Redshift, S3, Hadoop, etc.; scripting for automation (e.g. Python) and advanced SQL skills; experience in the data/BI space; experience creating AI-based tools to be used by non-technical stakeholders. That's skills. Could also include Preferred Qualifications as Qualifications.
We need to decide sections: About the role (description + team). Responsibilities (key job responsibilities). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills (maybe combine with Requirements? But we can separate). Benefits. Pay.
We must not create sections with filler like "commensurate with experience". Not present.
We need to ensure we don't duplicate content.
Let's craft.
First, About the role: combine description paragraph and About The Team paragraph.
Description: "We are looking for a Senior Business Intelligence Engineer (BIE) to drive the use of AI in analytics with high exposure to executive level business decision making support. In this role you will define and implement scalable processes, diving deep into the product and program metrics globally across multiple business units. You will apply both business and technical acumen in a fast-paced, ambiguous and innovative environment."
About The Team: "We are a collaborative group of technology and business experts dedicated to pushing the boundaries of AI performance optimization. Our team thrives on innovation, continuous learning, and creating transformative solutions that make a tangible impact across various business domains. We value diverse perspectives and empower team members to contribute unique insights that drive our collective success."
We'll combine into one
maybe two paragraphs.
Responsibilities: list bullet points from "Key job responsibilities". Let's extract each:
- Design and build AI tools that derive actionable insights from some of the world’s largest datasets
- Own the design and development of automated solutions for recurrent reporting and in-depth analyses including learning, publishing, and managing our operational business metrics decks
- Drive continuous improvement of our analytical processes by automating, scaling, and simplifying self-service support for our customers
- Invent new ways to explore our data and work with Product Managers to identify opportunities and transform business problems into defined data and reporting requirements
- Recognize and adopt best practices in reporting and analysis: data integrity, test design, analysis, validation, and documentation
Also "A day in the life" paragraph could be considered responsibilities? It's more descriptive of day. Could include as prose under Responsibilities or maybe as part of About the role. But we have to preserve all substantive info. Could add as a
under Responsibilities after list? Might be okay. But we need to follow rule: Use
- for any list of duties/requirements/benefits, and
for prose. So we can have a
for the day in the life.
Thus Responsibilities section:
Responsibilities
then - ... then a
A day in the life ...
.
Requirements: Basic Qualifications list.
- Experience programming to extract, transform and clean large (multi-TB) data sets
- Experience with AWS technologies
- Experience with theory and practice of information retrieval, data science, machine learning and data mining
- Experience using Cloud Storage and Computing technologies such as AWS Redshift, S3, Hadoop, etc.
- Experience in scripting for automation (e.g. Python) and advanced SQL skills.
- Experience in the data/BI space
- Experience creating AI-based tools to be used by non-technical stakeholders
We'll put as .
Qualifications: Preferred Qualifications list.
- Experience working directly with business stakeholders to translate between data and business needs
- Experience managing, analyzing and communicating results to senior leadership
- Experience working as a BIE in a technology company
- Master's degree in statistics, data science, or an equivalent quantitative field
Skills: Could be derived from Basic Qualifications but maybe we can combine with Requirements? However we need a Skills section if we have specific skills. Could list technical skills: programming, AWS, data science, machine learning, data mining, AWS Redshift, S3, Hadoop, Python, advanced SQL, scripting, data/BI, AI-based tools for non-technical stakeholders. That's essentially same as Requirements. Might be redundant. But we could still include Skills as a summary of technical proficiencies. However we must not invent or summarize away detail; we can list them as they appear. It's okay to repeat? Might be considered duplication but not prohibited. However we should aim to avoid thin sections. Maybe we can omit Skills and instead include skills within Requirements or Qualifications. But the instruction says we can include Skills section if we have real specific content. We have skills listed in Basic Qualifications; we could put them there. So maybe we don't need separate Skills. But we need to decide.
We have Benefits and Pay sections.
Benefits: list from paragraph: 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.
We'll put as .
Pay: list salary ranges per location. We need to preserve all substantive info. So we need to include each location line.
We can present as - USA, AZ, Tempe - $130,400.00 - $176,300.00 USD annually
etc.
We must not include "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." That's substantive? It mentions sign-on payments and RSUs. That's also part of compensation. Should we include that? Yes, it's substantive. So we should include that as prose in Pay section before the list.
Thus Pay section: 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 with each location.
Schedule: no info, omit.
Now we need to ensure we don't include boilerplate like EEO, accommodation, etc.
Now produce HTML fragment.
Let's craft.
We'll start with About the role
then two paragraphs.
Then
Responsibilities
then with li items, then A day in the life ...
.
Then Requirements
then with li items.
Then Qualifications
then with li items.
Then Benefits
then with li items (maybe combine benefits into one li? Better to split each benefit? The instruction: use - for any list of duties/requirements/benefits. So we can list each benefit as separate li. But the benefits paragraph includes many items within health insurance; we could keep as one li for health insurance with subitems? Might be okay to keep as one li describing health insurance. Then separate li for 401(k) matching, paid time off, parental leave.
We'll do:
- 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
Then Pay
then 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 with li for each location.
Now ensure we didn't miss any substantive info: The "About The Team" paragraph we included in About the role. The "A day in the life" paragraph we included under Responsibilities. The "Key job responsibilities" list we included. The "Basic Qualifications" list we included as Requirements. The "Preferred Qualifications" list we included as Qualifications. The benefits and pay we included. The location salary ranges we included. The company name and Job ID we omitted. The EEO etc omitted. The accommodation link omitted. The "Learn more about our benefits at https://amazon.jobs/en
for prose. We must not repeat job title as heading. We must not put Job ID etc. We must preserve ALL substantive information; do not invent or summarize away detail. We need to include Pay section only if posting actually states them. Yes, salary ranges given. So include Pay. Benefits: they list comprehensive benefits; include Benefits section. Schedule: no info, so omit. Skills: we could extract from Basic Qualifications: programming to extract, transform and clean large data sets; AWS technologies; theory and practice of information retrieval, data science, machine learning and data mining; Cloud Storage and Computing technologies such as AWS Redshift, S3, Hadoop, etc.; scripting for automation (e.g. Python) and advanced SQL skills; experience in the data/BI space; experience creating AI-based tools to be used by non-technical stakeholders. That's skills. Could also include Preferred Qualifications as Qualifications. We need to decide sections: About the role (description + team). Responsibilities (key job responsibilities). Requirements (Basic Qualifications). Qualifications (Preferred Qualifications). Skills (maybe combine with Requirements? But we can separate). Benefits. Pay. We must not create sections with filler like "commensurate with experience". Not present. We need to ensure we don't duplicate content. Let's craft. First, About the role: combine description paragraph and About The Team paragraph. Description: "We are looking for a Senior Business Intelligence Engineer (BIE) to drive the use of AI in analytics with high exposure to executive level business decision making support. In this role you will define and implement scalable processes, diving deep into the product and program metrics globally across multiple business units. You will apply both business and technical acumen in a fast-paced, ambiguous and innovative environment." About The Team: "We are a collaborative group of technology and business experts dedicated to pushing the boundaries of AI performance optimization. Our team thrives on innovation, continuous learning, and creating transformative solutions that make a tangible impact across various business domains. We value diverse perspectives and empower team members to contribute unique insights that drive our collective success." We'll combine into one
maybe two paragraphs. Responsibilities: list bullet points from "Key job responsibilities". Let's extract each: - Design and build AI tools that derive actionable insights from some of the world’s largest datasets - Own the design and development of automated solutions for recurrent reporting and in-depth analyses including learning, publishing, and managing our operational business metrics decks - Drive continuous improvement of our analytical processes by automating, scaling, and simplifying self-service support for our customers - Invent new ways to explore our data and work with Product Managers to identify opportunities and transform business problems into defined data and reporting requirements - Recognize and adopt best practices in reporting and analysis: data integrity, test design, analysis, validation, and documentation Also "A day in the life" paragraph could be considered responsibilities? It's more descriptive of day. Could include as prose under Responsibilities or maybe as part of About the role. But we have to preserve all substantive info. Could add as a
under Responsibilities after list? Might be okay. But we need to follow rule: Use
- for any list of duties/requirements/benefits, and
for prose. So we can have a
for the day in the life. Thus Responsibilities section:
Responsibilities
then- ... then a
A day in the life ...
. Requirements: Basic Qualifications list. - Experience programming to extract, transform and clean large (multi-TB) data sets - Experience with AWS technologies - Experience with theory and practice of information retrieval, data science, machine learning and data mining - Experience using Cloud Storage and Computing technologies such as AWS Redshift, S3, Hadoop, etc. - Experience in scripting for automation (e.g. Python) and advanced SQL skills. - Experience in the data/BI space - Experience creating AI-based tools to be used by non-technical stakeholders We'll put as- .
Qualifications: Preferred Qualifications list.
- Experience working directly with business stakeholders to translate between data and business needs
- Experience managing, analyzing and communicating results to senior leadership
- Experience working as a BIE in a technology company
- Master's degree in statistics, data science, or an equivalent quantitative field
Skills: Could be derived from Basic Qualifications but maybe we can combine with Requirements? However we need a Skills section if we have specific skills. Could list technical skills: programming, AWS, data science, machine learning, data mining, AWS Redshift, S3, Hadoop, Python, advanced SQL, scripting, data/BI, AI-based tools for non-technical stakeholders. That's essentially same as Requirements. Might be redundant. But we could still include Skills as a summary of technical proficiencies. However we must not invent or summarize away detail; we can list them as they appear. It's okay to repeat? Might be considered duplication but not prohibited. However we should aim to avoid thin sections. Maybe we can omit Skills and instead include skills within Requirements or Qualifications. But the instruction says we can include Skills section if we have real specific content. We have skills listed in Basic Qualifications; we could put them there. So maybe we don't need separate Skills. But we need to decide.
We have Benefits and Pay sections.
Benefits: list from paragraph: 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.
We'll put as
- USA, AZ, Tempe - $130,400.00 - $176,300.00 USD annually etc. We must not include "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." That's substantive? It mentions sign-on payments and RSUs. That's also part of compensation. Should we include that? Yes, it's substantive. So we should include that as prose in Pay section before the list. Thus Pay section:
- for any list of duties/requirements/benefits. So we can list each benefit as separate li. But the benefits paragraph includes many items within health insurance; we could keep as one li for health insurance with subitems? Might be okay to keep as one li describing health insurance. Then separate li for 401(k) matching, paid time off, parental leave. We'll do:
- 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 Then
- .
Pay: list salary ranges per location. We need to preserve all substantive info. So we need to include each location line.
We can present as
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- with each location.
Schedule: no info, omit.
Now we need to ensure we don't include boilerplate like EEO, accommodation, etc.
Now produce HTML fragment.
Let's craft.
We'll start with
About the role
then twoparagraphs. Then
Responsibilities
then- with li items, then
A day in the life ...
. ThenRequirements
then- with li items.
Then
Qualifications
then- with li items.
Then
Benefits
then- with li items (maybe combine benefits into one li? Better to split each benefit? The instruction: use
Pay
thenThe 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- with li for each location.
Now ensure we didn't miss any substantive info: The "About The Team" paragraph we included in About the role. The "A day in the life" paragraph we included under Responsibilities. The "Key job responsibilities" list we included. The "Basic Qualifications" list we included as Requirements. The "Preferred Qualifications" list we included as Qualifications. The benefits and pay we included. The location salary ranges we included. The company name and Job ID we omitted. The EEO etc omitted. The accommodation link omitted. The "Learn more about our benefits at https://amazon.jobs/en
- ... then a