Amazon BIE Intern SQL and Interview Questions: 17 Experiences

Shared by janebeingjane ·
Company
Amazon
Reports
17 interview reports
Level
Internship
Stages
OA → Phone screen → Onsite

Amazon BIE intern loops from 2023 to 2026 are two interviews: SQL with joins and window functions, then Leadership Principles, with a few chart questions.

At a glance

  • Process: usually a written test (01, 03, 04, 05), then two interviews, often back to back: one SQL-heavy, one behavioral or a visualization case (01, 02, 03, 05, 06, 07). Offers came four days (03) to about two and a half weeks (01) after the last round.
  • Asked recently: SQL in all 7 current reports, mostly joins and window functions (01, 03, 06, 07); Leadership Principles in 5; chart and dashboard questions in 3 (01, 03, 07). Candidate 01 also had a six-query, 15-minute SQL sprint and data-modeling questions.
  • Difficulty: candidate 02 called the SQL easy and still got an offer after a weak Python answer; 03 had one easy and two medium window-function questions. Six of the seven current candidates reported offers.
  • Practise first: First Order per Merchant per Date, Highest-Paid Employees by Salary Rank, Order Totals for Every Customer and dove deep to find a root cause.

Coverage: Amazon Business Intelligence Engineer (BIE) Intern, plus two "Business Intelligence internship" reports from Luxembourg. Online assessments, a take-home, a recorded video round, phone screens, and two-interview loops. Bangalore (campus), Germany, the U.S. (remote, New York, Seattle, San Francisco), Europe, and Luxembourg. Interviews from spring 2018 to mid-2026. Reports 01–07 (Nov 2023 to Jul 2026) are current; 08–17 (2018–2023) are under History, outside the current counts.

What came up

These counts cover the seven current reports (01–07).

Topic Reports Last seen
SQL query writing 7 of 7 Jul 2026 (report date)
Leadership Principles / behavioral 5 of 7 Jul 2026 (report date)
Joins and explaining the join choice 3 of 7 Jul 2026 (report date)
Window functions and ranking 3 of 7 Jul 2026 (report date)
Charts, dashboards, and visualization 3 of 7 Jul 2026 (report date)
Python 2 of 7 Jul 2026 (report date)
Data modeling and database concepts 1 of 7 Jul 2026 (report date)
Project deep dive 1 of 7 Jul 2026 (report date)
Fixing a broken SQL query 1 of 7 Jan–Mar 2025

Rows: SQL 01–07; behavioral 01, 02, 03, 05, 07; joins 01, 06, 07; window functions 01, 03, 07; charts 01, 03, 07; Python 01, 02.

Questions we found

SQL and data

Question Reports Last seen
Explain why you used a window function instead of a self-join 1: 01 Jul 2026 (report date)
Six SQL questions in 15 minutes (3 easy, 3 medium-to-hard) 1: 01 Jul 2026 (report date)
For each merchant, return the first order on each date (First Order per Merchant per Date) 1: 03 Mar 2025
Which ORDER BY expression is not the same as the others (OA multiple choice) 1: 04 Jan–Mar 2025
Which DENSE_RANK() expression causes a MySQL error (OA multiple choice) 1: 04 Jan–Mar 2025
Which GROUP BY … HAVING expressions have valid syntax (OA multiple choice) 1: 04 Jan–Mar 2025
Join two tables (simple join) 1: 06 May 2024 (report date)
Rank employees by salary and find the highest-paid (Highest-Paid Employees by Salary Rank) 1: 07 Nov 2023
Write a query and justify a LEFT join vs an INNER join (Order Totals for Every Customer) 1: 07 Nov 2023

Charts, dashboards, and visualization

Question Reports Last seen
The dashboard lifecycle and calculated columns 1: 01 Jul 2026 (report date)
How would you get to know a dataset you have never seen? 1: 03 Mar 2025
Critique two charts: title, chart type, and whether the right metrics are shown 1: 07 Nov 2023

Data modeling, database, and statistics concepts

Question Reports Last seen
Fact tables vs dimension tables 1: 01 Jul 2026 (report date)
Star schema vs snowflake schema 1: 01 Jul 2026 (report date)
Model a business scenario end to end 1: 01 Jul 2026 (report date)
Keys, constraints, and indexing 1: 01 Jul 2026 (report date)
Normal forms, and when you would denormalize on purpose 1: 01 Jul 2026 (report date)
ACID properties 1: 01 Jul 2026 (report date)

Behavioral (BQ)

Question Reports Last seen
Project deep dive: why that tech stack, what went wrong, what trade-offs you made, and what you would change (practice) 1: 01 Jul 2026 (report date)
A time you dove deep to solve a problem 1: 02 ~Jan 2026
A time you disagreed with someone on your team 1: 02 ~Jan 2026
Tell me about a time you had to learn something new 1: 02 ~Jan 2026
Tell me about a time you had a deadline 1: 02 ~Jan 2026
Simplify and Invent 1: 03 Mar 2025
A time you had difficulty communicating with a customer 1: 03 Mar 2025
Innovative projects you have worked on 1: 03 Mar 2025
Describe a project where you had to prioritize your time 1: 07 Nov 2023

Online assessments and take-homes

Four candidates described a written test before any live interview, and no two looked alike. Each summary points to the candidate's full entry.

Campus test in 2026, CS multiple choice plus one coding problem (entry 01)

Report date: Jul 29, 2026 · Role: BIE Intern · Location: Bangalore (campus)

  1. Multiple-choice questions, mostly on computer science fundamentals. No SQL was mentioned.
  2. One standard data-structures coding problem.

SQL-only test in 2025, syntax multiple choice and two medium queries (entry 04)

Interview date: Jan–Mar 2025 · Role: BIE Intern · Result: Passed

  1. Short SQL syntax and debugging questions, several in multiple-choice form (the three the candidate shared are in report 04 below).
  2. Two medium SQL problems at the end. The candidate didn't describe them.

Mixed test in 2025, multiple choice, hands-on SQL and a short Leadership Principles section (entry 05)

Interview date: early 2025 · Role: BIE Intern · Location: United States

  1. Multiple-choice questions.
  2. Hands-on SQL from basic to advanced, matching a sample test the recruiter had sent.
  3. A 10-minute Leadership Principles section.

Take-home in 2020 (history), three SQL questions on a five-table database (entry 16)

Interview date: ~Sep 2020 · Role: Business Intelligence internship · Location: Luxembourg

  1. Three SQL questions against about five tables, each testing different SQL functions.

7 candidate timelines, Nov 2023 to Jul 2026

01: Campus offer after a 15-minute, six-query SQL sprint

Report date: Jul 29, 2026 · Role: BIE Intern · Location: Bangalore (on campus) · Result: Offer, about two and a half weeks after the last round

Online assessment

  1. Computer-science multiple choice and one data-structures coding problem (see Online assessments above).

Technical interview 1

  1. Several medium SQL questions covering joins, aggregations, GROUP BY with HAVING, window functions, and subqueries. When the candidate used a window function, the interviewer asked why they had not used a self-join instead.
  2. Data modeling: fact vs dimension tables, star vs snowflake schemas, then modeling a scenario from start to finish. The scenario was not shared.
  3. Database basics: keys, constraints, and indexing; normalization and when you would denormalize on purpose; ACID properties.
  4. Basic Python, then one fairly easy data-structures question the interviewer wanted written in Python.

Technical interview 2

  1. A timed sprint: six SQL questions in 15 minutes, three easy and three medium-to-hard.
  2. Dashboards: how a dashboard moves from idea to maintenance, and basics like calculated columns.
  3. Normal forms, and when and why to apply them.
  4. A long deep dive into one of the candidate's projects, told in STAR format: why that tech stack, what went wrong and how they got around it, which trade-offs they made, and what they would do differently. Closest Amazon practice question: a technically complex project you worked on.
  5. A few Leadership Principle questions.

02: Nine easy SQL questions and a Python slip, still an offer

Interview date: ~Jan 2026 · Role: Business Intelligence Engineer Intern · Location: Germany (onsite) · Result: Offer · Process: about 8 weeks

Technical interview

  1. Nine easy SQL questions and one Python question. The candidate said the Python went badly.
  2. Behavioral: "Tell me about a time you dove deep" and "Tell me about a time you disagreed with your team."

Final round

  1. Behavioral only: "Tell me about a time you had to learn something new" and "Tell me about a time you had a deadline."

03: Window-function SQL and a "what does this dataset look like" case

Interview date: Mar 7, 2025 · Role: BIE Intern · Result: Offer, four days later · Process: OA Feb 11, invite Feb 18, interviews Mar 7

Online assessment

  1. Passed. The candidate didn't describe it.

Interview 1: SQL and behavioral (1 hour)

  1. Three SQL questions: one easy and two medium, using window functions. One of them was to return each merchant's first order for each date. Practice version: First Order per Merchant per Date.
  2. Behavioral: Simplify and Invent, and a time you had difficulty communicating with a customer.

Interview 2: visualization case and behavioral (1 hour)

  1. How would you get to know what a dataset looks like?
  2. Behavioral: innovative projects.

04: An SQL-only OA with three tricky multiple-choice questions

Interview date: Jan–Mar 2025 · Role: BIE Intern · Result: Passed the OA · Process: applied in September, heard from HR in October

Online assessment

  1. Short SQL debugging and syntax questions, then two medium SQL problems at the end. The candidate shared screenshots of three of the short ones:
    • Pick the expression that is not the same as the others:

      • SELECT * FROM categories ORDER BY id
      • SELECT * FROM categories ORDER BY id ASC
      • SELECT * FROM categories ORDER BY id DESC
      • None of the above, all expressions are the same.
    • Which expression causes a MySQL error?

      • SELECT DENSE_RANK() OVER ( ORDER BY SUBSTRING( customer_id, 1, 4 ) ) FROM transactions
      • SELECT DENSE_RANK() OVER ( ORDER BY ROW_NUMBER() OVER () ) FROM transactions
      • SELECT DENSE_RANK() OVER ( ORDER BY FOUND_ROWS() ) FROM transactions
      • None of the above, all expressions are correct.

      The candidate's screenshot shows the second option selected.

    • Select every expression with correct syntax (one or more):

      • SELECT customer_id, MAX( is_active ) FROM transactions GROUP BY customer_id HAVING MAX( is_active )
      • SELECT customer_id, is_active FROM transactions GROUP BY customer_id HAVING MAX( is_active )
      • SELECT customer_id, DISTINCT is_active FROM transactions GROUP BY customer_id HAVING MAX( is_active )
      • A fourth option starting SELECT customer_id, MAX( is_active ) AS is_active FROM transactions GROUP BY customer_id HAVING is_active, cut off in the screenshot.

      Readers of the post debated this one. One pointed out that MySQL treats HAVING MAX(is_active) as HAVING MAX(is_active) <> 0, which makes the first option valid.

  2. Two medium SQL problems. The candidate didn't describe them.

05: OA, then two back-to-back interviews in one two-hour block

Interview date: Feb 21, 2025 · Role: BIE Intern · Location: United States (remote, Amazon Chime) · Result: Offer, five days later

Online assessment

  1. Multiple choice, hands-on SQL from basic to advanced, and a 10-minute Leadership Principles section (see Online assessments above). The candidate finished it in six days.

Interview 1: technical, with a Business Intelligence Engineer

  1. A live technical round. The candidate did not share the questions.

Interview 2: behavioral, with the hiring manager

  1. Every question tied back to a Leadership Principle. The candidate did not list them.

06: Two relaxed technical interviews in New York

Report date: May 8, 2024 · Role: BIE Intern · Location: New York · Result: Offer, accepted

Two technical interviews

  1. A simple SQL question about joining two tables. That was the only question the candidate described.

07: Window-function ranking, a join debate, and a chart critique

Interview date: Nov 2023 · Role: Business Intelligence Engineer Intern · Location: United States (remote) · Result: Offer · Process: about 3 months; no recruiter screen and no OA

Interview 1: live SQL

  1. Rank employees by salary and find the highest-paid one. The candidate used a window function over an employee table. Practice version: Highest-Paid Employees by Salary Rank.
  2. Write a query and justify choosing a LEFT join or an INNER join. The candidate wrote it with CTEs and explained when each join fits, and the interviewer cared more about that reasoning than the syntax. Practice version, where the join choice changes the answer: Order Totals for Every Customer.

Interview 2: data visualization and Leadership Principles

  1. Critique two charts and suggest improvements, covering the title, the chart type, and whether the right metrics were shown.
  2. "Describe a project where you had to prioritize your time." The candidate didn't remember the other LP questions.

History (2018–2023)

These ten reports are more than three years old, so they are left out of the counts above. They tell the same story: SQL in 8 of the 10 and Leadership Principles in 6.

Topic Reports Last seen
SQL query writing 8 of 10 Oct 2022 (report date)
Leadership Principles / behavioral 6 of 10 Oct 2022 (report date)
Fixing a broken SQL query 4 of 10 Oct 2022 (report date)
Joins, UNION, and explaining the join choice 4 of 10 Oct 2022 (report date)
Charts, dashboards, and visualization 4 of 10 Oct 2022 (report date)
Data modeling and database concepts 3 of 10 Oct 2022 (report date)
Business and analytics cases 3 of 10 Oct 2022 (report date)
Window functions and ranking 2 of 10 Oct 2022 (report date)
Statistics and A/B testing 2 of 10 Oct 2022 (report date)
Python 1 of 10 2023

Questions in the older reports

SQL and data

Question Reports Last seen
Fix a broken query that filters on MONTH(timestamp) > 2010 (Fix the Broken Year Filter Query) 2 Oct 2022
Winner and Loser tables: combine all names into one output, and explain UNION vs UNION ALL (Combine Winner and Loser Names) 2 Oct 2022
Count distinct values 1 ~Jan 2021
Book sales: the highest value, the Nth highest, then the Nth highest without LIMIT or nested queries (Nth-Highest Book Sales Volume) 1 Apr–Jun 2018

Charts, dashboards, and visualization

Question Reports Last seen
Pie charts: what they are and when to use or avoid them 2 Oct 2022
Which charts to use for exploratory analysis, and how to show the relationship between two variables 1 Oct 2022
How to design a dashboard, and common dashboard mistakes 1 Jan 2022
Given a line chart and a pie chart, should either become a different chart type, and why 1 ~Jan 2021
Tableau questions, including the names of chart types 1 ~Jan 2021

Data modeling, database, and statistics concepts

Question Reports Last seen
What is a primary key, and which join types do you know? 2 Oct 2022
Basic data modeling questions 1 Feb 2021
Hypothesis testing and a simple A/B testing question 1 Feb 2021

Business and analytics cases

Question Reports Last seen
How would you email customers to introduce a new Prime Video show? Approach, model, and first step 1 Oct 2022
A search ranking algorithm changed: how would you test it, and with several candidates, how do you pick the best? 1 Oct 2022
AWS is building a new data center: which metrics should it track, and why? 1 Jan 2022
Business-sense questions, plus "what forecasting models are there?" 1 ~Jan 2021

Behavioral (BQ)

Question Reports Last seen
A time you dove deep to solve a problem 2 Oct 2022
A time you disagreed with someone on your team 2 ~Jan 2021
A teammate was struggling: what did you do? 2 Oct 2022
A tight deadline where you could not consider every option before deciding 1 Oct 2022
A decision you made on your own without asking a supervisor or professor 1 Oct 2022
A time you went outside your comfort zone and tried something new 1 Oct 2022
Making a decision in a short time 1 ~Jan 2021
How you overcame a difficulty 1 ~Jan 2021
Ownership 1 ~Jan 2021
A time you solved a problem creatively 1 ~Nov 2020
Why this internship, and how do you picture it going? 1 ~Sep 2020
Would you rather work in a technical team or with less technical people? 1 ~Sep 2020
A time you took a risk, made a mistake, or failed 1 ~Sep 2020
A time you helped a coworker, for example by catching a mistake 1 ~Sep 2020
The biggest subject you had to analyze: how you went about it and what came out of it 1 ~Sep 2020
Your role in a team project, how the work was split and planned, and what you learned 1 ~Sep 2020
The biggest dataset you have worked with, and whether its size worried you 1 ~Sep 2020
How comfortable you are with SQL and Python, and which language you know best 1 ~Sep 2020

10 older candidate timelines

08: One Python question in a European technical round

Interview date: ~2023 (year only) · Role: BIE Intern · Location: Europe

Technical interview

  1. A single Python question, which the candidate called extremely easy. They didn't say what it was.

09: The Winner/Loser UNION question, a pie chart, and two analytics cases

Report date: Oct 13, 2022 · Role: BIE Intern (summer 2023) · Result: Got the internship · Process: applied online Sep 17, scheduling email two weeks later; two back-to-back 45-minute interviews

Interview 1: SQL, visualization, then behavioral

  1. Concepts: what is a primary key, and which kinds of join do you know?
  2. Find and fix the errors in this query:
    select name MONTH(timestamp)
    FROM table
    WHEREMONTH(timestamp)>2010
    In a reply, the candidate confirmed that part of the fix is filtering on the year instead of the month. Practice version: Fix the Broken Year Filter Query.
  3. Given a Winner table (ID, Name) and a Loser table (ID, Name), write a query that combines all of the names into one output, using UNION and UNION ALL and explaining the difference. Practice version: Combine Winner and Loser Names.
  4. Visualization: what a pie chart is, when to use one and when not to, which charts suit exploratory analysis, and how to show the relationship between two variables in a chart.
  5. Two behavioral questions, each with many follow-ups: a teammate who was struggling and what you did, and a time you dove deep to solve a new problem.

Interview 2: behavioral and technical cases, no SQL

  1. Behavioral: a tight deadline where there was no time to weigh every option before deciding, a decision made without consulting a supervisor or professor, and a time you went outside your comfort zone.
  2. How would you email customers to introduce a new Prime Video show: how would you start, what model would you use, and what is the first step?
  3. If a ranking function changed, how would you test it? Follow-up: with many ranking functions, how do you know which is best? The candidate later explained that "ranking function" meant a ranking algorithm, such as the one that orders Amazon search results, and that the question was about testing a new recommendation algorithm with an A/B test.

The candidate prepared more than ten stories across the Leadership Principles and used four or five of them across both rounds.


10: The same UNION question in Seattle, plus an AWS data-center case

Interview date: early Jan 2022 · Role: BIE Intern · Location: Greater Seattle · Result: Offer after a waitlist · Process: applied in late September with a referral; invite in early November; waitlisted a week after interviewing; portal changed to "moved to another job" in early February, offer the next day

Interview 1: SQL and data visualization

  1. Find the syntax errors in a SQL query.
  2. Given a Winner table (ID, Name) and a Loser table (ID, Name), write a query that combines all of the names into one output. Practice version: Combine Winner and Loser Names.
  3. Data visualization: how to design a dashboard and common mistakes.

Interview 2: business case

  1. If AWS were building a new data center, which metrics should it watch? The candidate had to justify each one, and there were follow-up questions.

The candidate said interns seemed to get only one interview session that cycle: two interviewers back to back, 90 minutes in total.


11: Data modeling in one interview, A/B testing in the other

Report date: Feb 23, 2021 · Role: BIE Intern · Location: United States · Result: Offer · Process: invite in early February; two interviewers, 45 minutes each

Interview 1

  1. Basic data modeling and basic SQL for about 15 minutes, then behavioral questions for the rest.

Interview 2

  1. Hypothesis testing and a simple A/B testing question for about 15 minutes, then behavioral questions for the rest.

The week after, the portal showed "moved to another job"; the offer came two days later.


12: A UNION question, a pie chart, and a forecasting question

Report date: Jan 27, 2021 · Role: BIE Intern (summer 2021) · Result: Offer, about a week later · Process: two rounds, booked for 45 minutes each but closer to an hour

Round 1

  1. 20 minutes of SQL: two easy questions, one fixing errors in given code and one using UNION.
  2. 15 minutes of data visualization, where they only asked about pie charts.
  3. 15 minutes of behavioral questions, then 10 minutes for the candidate's questions.

Round 2

  1. No SQL. Some business-sense questions and "what forecasting models are there?" The candidate guessed time series and regression but said they couldn't really answer, and the interviewer moved on.
  2. Many behavioral questions.

The candidate told the author of report 14 that their questions had been almost identical.


13: A confusing schedule, then an offer

Interview date: ~Jan 26, 2021 · Role: BIE Intern · Location: United States (San Francisco office) · Result: Offer

  1. Applied online in November. The interview slots were fixed within a single day, and HR first described one round of two back-to-back interviews, then a 45-minute round plus two more. The candidate didn't share the questions.
  2. About a week after interviewing, the portal changed to "moved to another job"; the offer followed a few days later.

14: The MONTH/YEAR debugging query, count distinct, and a chart makeover

Report date: Jan 22, 2021 (written right after the interviews) · Role: BIE Intern (2021) · Process: two interviews

Interview 1

  1. Concepts: primary key, join, and union.
  2. Fix this query (the candidate said a very similar one had been posted before):
    select name MONTH(timestamp)
    FROM table
    WHEREMONTH(timestamp)>2010
    Practice version: Fix the Broken Year Filter Query.
  3. A question similar to a LeetCode easy SQL problem.
  4. How do you count distinct values?
  5. Behavioral: making a decision in a short time and how you overcame a difficulty, plus questions about projects on the resume.

Interview 2

  1. Behavioral: someone on the team disagreed, and ownership.
  2. Some Tableau questions. The candidate suggested knowing the names of common chart types.
  3. Given a line chart and a pie chart, how would you improve them? In a reply, the candidate explained this meant deciding whether each chart should become a different type, and why.

The candidate said none of the questions were hard, but every one had follow-ups.


15: A recorded video round in Luxembourg, then a behavioral final

Interview date: ~Nov 2020 · Role: BI Intern · Location: Luxembourg · Result: Offer, the day after the final

Round 1: one-way recorded video

  1. One SQL question with four parts, and general questions otherwise. The candidate answered two parts, then accidentally skipped ahead with shift+enter. HR later said overall performance mattered, and they still reached the final. They remembered only that the parts they answered were not hard.

Final round: two interviewers, one hour

  1. No technical questions; all situational: a disagreement and how you resolved it, a time you went deep to solve a problem, a time you solved a problem creatively, and a coworker who was struggling and what you did. The interviewers were from a finance team.

16: A 2020 take-home and two short, mostly behavioral interviews

Interview date: ~Sep 2020 · Role: Business Intelligence internship (the candidate also called it a Business Analyst internship) · Location: Luxembourg · Result: Offer, the day after the interviews

Recruiter call

  1. A 10-minute call to confirm interest and explain the steps.

Take-home

  1. Three SQL questions on a database of about five tables (see Online assessments above).

Two 30-minute interviews

  1. Billed as "technical," but mostly about the candidate and their experience:
    • why this internship, and how they pictured it going;
    • whether they'd rather work in a technical team or with less technical people;
    • a time they took a risk, made a mistake, or failed, and what they learned;
    • a time they helped a coworker, for example by catching a mistake;
    • the biggest subject they had analyzed, how they went about it, and the result;
    • their role in a team project, how the work was split and planned, and what they learned;
    • the biggest dataset they had handled and whether its size worried them;
    • how comfortable they were with SQL and Python, and which language they knew best.

17: Highest, Nth highest, then Nth highest without LIMIT

Interview date: Apr–Jun 2018 · Role: Business Intelligence Engineer Intern (summer 2018) · Result: Rejected after this round, within three business days

Technical interview: online SQL coding

  1. Every question used the same book-sales scenario. The first was like "find the highest value," and the second like "find the Nth highest value."
  2. The third built on the second: the candidate had used LIMIT, so the interviewer asked for a version without it. They nested two queries; the interviewer then asked for no nesting either, using a function instead. The candidate suspected a window function but couldn't write one, and believes this is where they failed. Practice version: Nth-Highest Book Sales Volume.
  3. The candidate could choose the SQL dialect; the interviewer asked which one they were using.

Patterns across all 17 reports

  1. Two interviews, usually back to back. Reports 01, 02, 03, 05, 06, 07, 09, 10, 11, 12, 14, 15 and 16 describe two interviews after any written test. In most, one leaned on SQL and the other on behavioral questions or a case, though reports 02, 03, 09, 11 and 12 mixed behavioral questions into both.

  2. The same SQL exercises came back. The broken MONTH(timestamp) > 2010 query appears in reports 09 and 14, and the Winner/Loser names question in reports 09 and 10. The candidate in report 12 told the author of report 14 that their questions were almost identical.

  3. Interviewers pushed on the why. Report 01 was asked why a window function rather than a self-join, report 07 why a LEFT or an INNER join, report 09 how UNION differs from UNION ALL, and report 17 to redo a query without LIMIT and then without nesting.

  4. Charts came up as discussion, not as building. Reports 07, 09, 12 and 14 talked about specific charts (pie charts in 09 and 12, a line chart and a pie chart in 14, two charts to critique in 07). Reports 01 and 10 talked about dashboards. None built one live.

  5. Python stayed small. Reports 01, 02 and 08 each describe one basic or easy Python question. The candidate in 02 struggled with it and still got an offer.

  6. The written test varied. Report 01 had computer-science multiple choice and a coding problem, 04 SQL syntax questions plus two medium SQL problems, 05 SQL plus a short Leadership Principles section, and 16 a SQL take-home. Report 15 had a recorded video round instead, and report 07 no test at all.

  7. "Moved to another job" was not a rejection. In reports 10, 11 and 13, the candidate's application portal switched to "moved to another job" shortly before the offer arrived.

Common questions

What SQL does the Amazon BIE intern interview ask?

Mostly joins, aggregation and window functions: each merchant's first order per date (03), ranking employees by salary (07), a LEFT vs INNER join you must justify (07), and why a window function instead of a self-join (01).

Does the Amazon BIE intern loop have an online assessment?

Four of the seven current candidates took one, and no two looked alike: CS multiple choice plus a coding problem (01), SQL syntax questions plus two medium SQL problems (04), and SQL plus a short Leadership Principles section (05).

How many interviews are in the Amazon BIE intern loop?

Two in most reports, often back to back in one block (05: two hours on Amazon Chime): one SQL-heavy and one behavioral or visualization case.

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.