Senior Business Intelligence Engineer, Infra Supply Chain Automation

We need to output HTML fragment with sections: About the role (maybe description), Responsibilities, Requirements (or Qualifications), Skills maybe, Benefits, Pay, Schedule. Must only include sections that have real specific content. We have description about role, responsibilities list, qualifications list, benefits description, pay ranges, schedule not mentioned. So we include About the role (maybe from first paragraphs), Responsibilities (list), Requirements (maybe combine Basic Qualifications and Preferred Qualifications?), Benefits (list), Pay (range). No schedule. We must not repeat job title as heading. Use

for each section heading. Use

• for lists. Use

  for prose. We must preserve all substantive info, not invent. Remove boilerplate: EEO, accommodation link, etc. Also remove duplicated lines, navigation, cookie, legal, application instructions. Also remove "Company - Amazon Data Services, Inc. Job ID: A10558684" as minor metadata; we can fold into short

  or drop. Probably drop. We need to include pay: base salary range listed for two locations: USA, TX, Austin - 130,400.00 - 176,300.00 USD annually; USA, WA, Seattle - same. We can present as a

  with both. Benefits: list of health insurance etc. We'll extract: 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. Also mention learn more link but that's boilerplate; we can drop link. Responsibilities: list bullet points from "Key job responsibilities". We'll capture each. Requirements: Basic Qualifications list (many). Preferred Qualifications list (two). We'll combine maybe as Requirements section with sublists? But we need to use

  • for any list of duties/requirements/benefits. Could have one list combining all qualifications. Might be long but okay. We must not include filler like "commensurate with experience". Not present. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits present, Pay present. Schedule not present, so omit. Now produce HTML. Structure:

    About the role

    ... description paragraphs ...

    Responsibilities

    • Design, develop and maintain scaled, automated, user-friendly systems, reports, dashboards, etc. that will support the needs of the business.
    • Apply deep analytic and business intelligence skills to extract meaningful insights and learning from large and complicated data sets.
    • Be hands-on with ETL to build data pipeline to support automated reporting.
    • Serve as liaison between the business and technical teams to achieve the goal of providing actionable insights into current business performance, and ad hoc analyses to support future improvements or innovations. This will require data gathering and manipulation, problem solving, and communication of insights and recommendations.
    • Build various data visualizations to tell the story of business trends, patterns, and outliers through rich visualizations.
    • Recognize and adopt best practices in reporting and analysis: data integrity, test design, analysis, validation, and documentation.

    Requirements

    • Bachelor's degree or foreign equivalent in Computer Science, Engineering, Mathematics, Statistics, Economics, or a related field
    • Experience programming to extract, transform and clean large (multi-TB) data sets
    • 5+ years of SQL experience
    • 5+ years of as a Data Analyst, Data Engineer, Business Intelligence Analyst, or a related occupation experience
    • 1+ years of SQL, ETL or Oracle experience
    • 1+ years of processing large, multi-dimensional datasets from multiple sources experience
    • 1+ years of performing statistical analysis experience
    • 1+ years of developing automated reporting experience
    • Experience with theory and practice of design of experiments and statistical analysis of results
    • Experience in scripting for automation (e.g. Python) and advanced SQL skills.
    • Experience with theory and practice of information retrieval, data science, machine learning and data mining
    • Experience working directly with business stakeholders to translate between data and business needs
    • Experience managing, analyzing and communicating results to senior leadership

    Benefits

    • 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

    Pay

    USA, TX, Austin: $130,400.00 - $176,300.00 USD annually; USA, WA, Seattle: $130,400.00 - $176,300.00 USD annually

    We also need About the role prose: combine initial description paragraphs about AWS Infrastructure Services and the ADS team seeking Senior BI Engineer. Let's craft a concise paragraph preserving all substantive info. Original description: "AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we’re the people who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we’re looking for talented people who want to help. You’ll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You’ll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you’ll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion. Do you want to be an integral part of the world's transition to the cloud? The AWS Analytics and Data Solutions (ADS) team is seeking a Senior Business Intelligence Engineer (BIE) with a combination of superior analytical abilities, business acumen, business judgement, curiosity, technical skills, and written and verbal communication skills to join our team. Data-driven decision-making is at the core of Amazon’s culture and people who are exceptionally talented at analyzing large sets of data to build insights are critical. Your work will directly impact the decisions and strategy of the entire AWS Infrastructure Services org and our customers. You will be gathering customer needs and insights, mining large and diverse data sets from across AWS Infrastructure, building visualizations and tools for our business partners, generating insights to help senior leaders make critical business decisions. Hence, the successful BIE will not only possess the expertise and passion for analyzing data, designing metrics to measure the performance of the business, and building reporting capabilities and tools, but also will interact directly with business leaders and teams that rely on the metrics and analyses that they produce. The Senior business intelligence engineer must be a self-starter, comfortable with ambiguity, able to think big and be creative (while still paying careful attention to detail), and enjoy working in a fast-paced, dynamic environment. If you are excited about data, are results-oriented, and want to join a growing analytics team within Amazon - this role is for you!" We'll put that in

    . Now ensure no boilerplate like "Amazon is an equal opportunity employer..." removed. We also need to maybe include "About The Team" section? That includes subsections like Why Amazon, Diverse Experiences, Work/Life Balance, Inclusive Team Culture, Mentorship and Career Growth. Those are generic benefits/culture but could be considered as part of Benefits? However they are more about culture. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Those sections have specific content (Why Amazon, Diverse Experiences, etc.) but they are somewhat generic but still specific. However they might be considered boilerplate? They are part of the job posting describing team culture. Could be included as a section like "About the Team". But we already have About the role. Could add another section "About the Team" with subheadings? But we only allowed

    for section headings. Could we include multiple

    sections? Yes. But we need to decide if we should include them. The instruction: "Prefer a few substantive sections over many thin ones." The About the Team subsections are somewhat thin but each has content. Might be better to combine them into a single "About the Team" section with a paragraph summarizing. However we must preserve ALL substantive information; we cannot summarize away detail. So we need to keep the details. Could we make a list? The content includes headings like "Why Amazon?" then paragraphs. We could treat each as a

    but that would be many sections. The instruction says prefer few substantive sections over many thin ones. So maybe we should not create separate headings for each subpoint; instead we could include a single "About the Team" section with a

    capturing the bullet points? But the content is not a list; it's paragraphs with headings. We could convert each heading into a inside a

    but that might be altering structure. The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. It says use

    for section headings. So we can use

    for any section heading we want. But we should avoid many thin sections. The About the Team section has multiple subheadings; maybe we can treat the whole "About The Team" as a section and inside use

    for each paragraph, preserving the headings as plain text (maybe bold). But we cannot use markdown; we can use HTML inside

    . That's acceptable. Thus we could add

    About the Team

    then series of

    each containing Why Amazon? followed by paragraph, etc. But we need to check if that violates "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using h3 for those typical sections. Using h3 for About the Team is okay. We must also avoid repeating job title as heading. Not doing that. We must not put Job ID / requisition numbers as headings — we dropped. Now decide: include About the Team? It contains substantive info about Amazon values, diverse experiences, work-life balance, inclusive culture, mentorship. This is indeed substantive. Should we include? The instruction: "Prefer a few substantive sections over many thin ones." If we add About the Team, we increase sections but each is substantive. Could be okay. But we already have About the role which covers a lot of the role description. The About the Team is separate. Given the instruction to preserve ALL substantive information, we should include it. Thus final HTML will have sections: About the role, Responsibilities, Requirements, Benefits, Pay, About the Team. We could also include Skills? Not separate; we have skills within Requirements. Now craft About the Team content. From posting: "About The Team Why AWS? Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global