Sr. Business Intelligence Engineer, AWS Analytics Engineering

We need to output HTML fragment with headings

for 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 as heading. Must not include Job ID etc. Remove boilerplate like EEO, accommodation, etc. Also remove application instructions. Must preserve all substantive info. We need to parse the description. Key parts: Description: AWS is looking for a Sr. Business Intelligence Engineer to join the AWS Analytics Engineering (AAE) team supporting Amazon Quick. ... (long paragraph). This is your opportunity... etc. Then "Key job responsibilities" list bullet points. Then "About The Team" paragraph. Then "Basic Qualifications" list. Then "Preferred Qualifications" list. Then EEO etc (remove). 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. 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." Then location: "USA, WA, Seattle - 130,400.00 - 176,300.00 USD annually" Then "Company - Amazon Development Center U.S., Inc. Job ID: A10538977" We need sections: About the role (maybe the description paragraph?), Responsibilities (Key job responsibilities), Requirements (maybe Basic Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills (maybe combine?), Benefits (benefits description), Pay (salary range), Schedule (maybe not present). There's no explicit schedule info, so we should not create Schedule section. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We must not create sections with filler like "not specified". So we include only those with content. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus: - About the role: prose from description (first paragraph(s) up to maybe before "Key job responsibilities"). - Responsibilities: list under "Key job responsibilities". Use

  • . - Requirements: maybe "Basic Qualifications". Use
    • . - Qualifications: maybe "Preferred Qualifications". Use
      • . - Skills: maybe combine some skill mentions? Could be redundant. The posting includes "Experience programming to extract, transform and clean large (multi-TB) data sets", "Experience with data modeling, warehousing and building ETL pipelines", "Experience with AWS technologies", "Experience in scripting for automation (e.g. Python) and advanced SQL skills." Those are part of Basic Qualifications. Might be better to keep them under Requirements. The Skills section could be omitted if not distinct. But we could create a Skills section for things like SQL, Python, AWS, etc. However we must not create thin sections. Better to keep Requirements (Basic Qualifications) and Qualifications (Preferred Qualifications). Skills maybe not needed. - Benefits: list of benefits from paragraph. - Pay: salary range. We need to preserve all substantive info, not invent or summarize away detail. So we need to include the description paragraphs exactly (or close). We must not omit any substantive info. Must not add extra info. We need to be careful to not include boilerplate like EEO, accommodation, etc. Also remove "Amazon is an equal opportunity employer..." lines. Also remove "Learn more about our benefits at ..."? That is a link; but it's part of benefits description. Might be considered boilerplate? It's a link to learn more; but it's still part of benefits info. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn more about our benefits at ..." is not exactly boilerplate but could be considered navigation? It's a link to benefits page. Might be okay to keep? It's not essential substantive info about benefits; it's a reference. Might be considered navigation. Safer to remove it? The instruction says remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits is navigation; we could drop it. However we need to preserve ALL substantive information; the link is not substantive info about benefits; it's just a pointer. So we can drop it. Similarly, the line "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." is substantive about compensation; keep. We need to include location and salary range: "USA, WA, Seattle - 130,400.00 - 176,300.00 USD annually". That's pay. We also have "Company - Amazon Development Center U.S., Inc. Job ID: A10538977" - we should drop Job ID and maybe company? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. So we could include company name in a short p maybe. But it's minor metadata; we could drop it entirely. Probably safe to drop. Now we need to format. Let's extract prose for About the role: "AWS is looking for a Sr. Business Intelligence Engineer to join the AWS Analytics Engineering (AAE) team supporting Amazon Quick. Formerly Amazon QuickSight, Quick has evolved from a standalone BI service into a comprehensive, generative-AI-powered business intelligence platform that combines traditional analytics with modern AI assistance. It brings together two complementary experiences. Amazon Quick Sight is the cloud-native dashboarding and visualization engine that powers governed datasets, interactive dashboards, and ML-driven insights such as forecasting and anomaly detection. Alongside it, an agentic AI layer lets users chat with their data, conduct deep research, and automate multi-step workflows across connected enterprise sources through natural language. Available in the browser, as a desktop companion, and through extensions for Slack and Microsoft Office, Quick is used to turn data into decisions and actions, without requiring machine learning expertise. This is your opportunity to shape the analytical foundation of one of AWS's fastest-evolving products. As a Sr. BIE on this team, you will own the end-to-end analytical roadmap for Amazon Quick. You will generate insights that directly drive adoption, engagement, and growth, and that influence product and feature decisions at the leadership level. You will work with datasets in one of the world's largest data warehousing environments, developing and supporting your hypotheses with data-driven analysis. You will partner closely with product, business, finance, and engineering leaders to tackle non-standard, ambiguous business problems and translate them into actionable output. You will be part of a business intelligence team that goes beyond reporting and drills into the drivers behind key business metrics, redefining best practices with a cloud-based approach to scalability and automation. Beyond building analytics for Amazon Quick, this team is reimagining how analytical work itself gets done. We are developing agentic capabilities that automate and accelerate the daily workstream of a business intelligence engineer, from building reports to answering analytical questions on demand. As a Sr. BIE, you will help shape and adopt these capabilities, both applying them to scale your own impact and informing how they evolve. This is a rare opportunity to practice business intelligence on a platform you are helping to build, and to redefine analytical best practices for an AI-native era." That's the description. Now Responsibilities list: - Develop a deep understanding of the business drivers, customer behavior, and data landscape for Amazon Quick. - Own and deliver a comprehensive reporting and analytical roadmap that surfaces the key metrics for adoption, engagement, and growth. - Deliver in-depth, data-driven analysis papers with actionable insights for business and product leaders. - Design and build scalable data pipelines and models to derive key business metrics from large, complex datasets. - Collaborate with cross-functional teams to identify and onboard new data sources that expand analytical coverage. - Communicate findings clearly to business, finance, product, and technical audiences to influence decision-making and product enhancements. - Build and adopt agentic capabilities that automate and accelerate analytical work, from report generation to answering analytical questions on demand. - Mentor junior engineers and help establish new analytical standards and best practices for the team. Now About The Team paragraph: "Our team is dedicated to supporting new members. We have a broad mix of experience levels and tenures, and we're building an environment that celebrates knowledge sharing and mentorship. Our senior members enjoy one-on-one mentoring and thorough, but kind, code reviews. We care about your career growth and strive to assign projects based on what will help each team member develop into a better-rounded engineer and enable them to take on more complex tasks in the future." This could be part of About the role or maybe a separate section? The instruction only lists specific headings; we could incorporate this into About the role prose, or maybe create a separate section like "About the Team" but not in allowed headings. Since only allowed headings are those listed, we should not add extra headings. So we can fold this into About the role prose (maybe after the description). That would preserve all substantive info. Now Basic Qualifications list: - 5+ years of SQL experience - Experience programming to extract, transform and clean large (multi-TB) data sets - Experience with data modeling, warehousing and building ETL pipelines - Experience with AWS technologies - Experience in scripting for automation (e.g. Python) and advanced SQL skills. Now 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 with data visualization using QuickSight, Tableau, or similar tools Now Benefits paragraph: "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." We could also include "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." That's compensation, not benefits. Could be part of Pay section? Pay section includes salary range and maybe sign-on payments and RSUs. The instruction: include Pay section only if posting actually states them. It does state base salary range and mentions sign-on payments and RSUs. So we can include Pay section with that info. Thus Pay section: "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. USA, WA, Seattle - 130,400.00 - 176,300.00 USD annually" We need to preserve all substantive info; we should not drop the sentence about final compensation determination. So include that. Now Benefits section: as above. Now we need to decide about Skills section. Could we create a Skills section summarizing technical skills? But we already have Requirements (Basic Qualifications) which includes skills. Might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So we can skip Skills. Thus sections: About the role (prose), Responsibilities (ul), Requirements (ul), Qualifications (ul), Benefits (ul? Actually benefits is a list but we can keep as

        • for each benefit item). Pay (p). No Schedule. Now we need to output only HTML fragment, no /, no markdown. We'll produce something like:

          About the role