← Amazon Interview Insights

Amazon·Software Engineer·Technical Phone Screen·Senior

Senior
Jun 2026

Summary

Amazon Applied Scientist screen that skips the small talk entirely and goes straight into your resume projects. The technical depth they expect is no joke, down to units of information-theoretic quantities.

Questions Asked (3)

Q1

Walk me through a specific ML project from your resume in detail.

Technical Trade-offsAdaptability & Ambiguity
Author's notes

They didn't ask me to introduce myself or say why I wanted the role.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Select a project where you made significant technical decisions and can clearly articulate the problem, your approach, and the impact. Use the STAR method to structure your answer, emphasizing trade-offs and how you navigated ambiguity. Keep it concise but detailed enough to demonstrate depth.

Pro tip: Quantify the impact of your project (e.g., latency reduction, cost savings, accuracy improvement) and explicitly discuss what you would do differently with hindsight, showing self-awareness and growth.

1. Set the Context

Briefly describe the project's goal, your role, and the business or technical problem it addressed. Mention the scale and any constraints (e.g., data size, latency requirements).

2. Explain the Approach

Outline the ML pipeline: data collection, feature engineering, model selection, training, and evaluation. Highlight key decisions and why you made them.

3. Discuss Trade-offs

Detail the trade-offs you considered (e.g., model complexity vs. interpretability, latency vs. accuracy) and how you balanced them. Explain any alternatives you rejected and why.

4. Handle Ambiguity

Describe any ambiguous requirements or unexpected challenges and how you resolved them. Show adaptability and problem-solving.

5. Share Results and Learnings

Quantify the impact (e.g., metrics, business outcomes) and reflect on what you learned or would improve. Connect it to the role at Amazon.

Key Points to Mention

  • Specific ML techniques used (e.g., model type, feature engineering methods)
  • Trade-offs between different approaches (e.g., precision vs. recall, training time vs. inference speed)
  • How you handled data quality issues or missing data
  • Metrics used to evaluate the model and their business relevance
  • Collaboration with cross-functional teams (e.g., product, data engineering)
  • Scalability and deployment considerations (e.g., serving infrastructure, monitoring)

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q2

What is the unit of surprisal in information theory?

Technical Trade-offsAlgorithms & Data Structures
Author's notes

Blanked for a second.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by directly answering that the unit is the bit (or shannon), then explain that surprisal measures the information content of an event and is defined as -log2(P(event)). Connect it to practical applications like data compression and decision trees to show relevance to software engineering.

Pro tip: Mention that while 'bit' is the standard unit, the base of the logarithm determines the unit (e.g., nats for natural log), and that in practice, base 2 is used because digital systems operate on binary. This shows depth and avoids ambiguity.

1. Direct Answer

State clearly that the unit of surprisal is the bit (also called shannon), when using base-2 logarithm.

2. Define Surprisal

Explain that surprisal quantifies the amount of information gained from an event, defined as -log2(P(event)).

3. Explain the Unit

Describe why the unit is the bit: it represents the information content of a fair coin flip (probability 0.5), which yields 1 bit.

4. Connect to Software Engineering

Relate surprisal to practical concepts like entropy, data compression (e.g., Huffman coding), and decision tree splits (e.g., information gain).

5. Mention Alternative Units

Note that other bases yield different units: natural log gives nats, base-10 gives hartleys, but bits are standard in computing.

Key Points to Mention

  • Surprisal is also known as self-information.
  • The formula is -log2(P(event)).
  • The unit is the bit (or shannon).
  • A fair coin flip has a surprisal of 1 bit.
  • Surprisal is inversely related to probability: rare events have high surprisal.
  • It is foundational to entropy, which is the expected surprisal.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.

Q3

Defend the evaluation methodology you used for that project. Why those metrics?

Technical Trade-offsProduct Analytics & Metrics
Author's notes

They kept pushing back on every metric I named.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by restating the project's goal and constraints to ground your metric choices. Explain how each metric directly measures progress toward that goal, and acknowledge trade-offs or alternatives you considered. Emphasize that metrics were chosen to drive the right behaviors and align with business outcomes.

Pro tip: Tie your metrics to Amazon's leadership principles, such as Customer Obsession and Dive Deep, by showing how they reflect customer impact and long-term value rather than vanity numbers.

1. Restate Goal and Constraints

Briefly remind the interviewer of the project's objective, scope, and any constraints (e.g., time, resources, technical debt). This sets the context for why certain metrics were necessary.

2. Explain Metric Selection Rationale

For each key metric, describe what it measures and why it was the best proxy for success. Connect it to user behavior, system performance, or business impact.

3. Discuss Trade-offs and Alternatives

Acknowledge other metrics you considered and why you rejected them (e.g., too noisy, lagging, or misaligned with goals). Show you evaluated multiple options.

4. Highlight Validation and Iteration

Explain how you validated the metrics (e.g., A/B tests, correlation with outcomes) and whether you adjusted them over time based on data.

5. Connect to Outcomes and Learnings

Summarize how the chosen metrics drove decisions, improved the product, and what you learned about measurement for future projects.

Key Points to Mention

  • Alignment with business goals and customer impact (e.g., conversion rate, latency, error rate)
  • Leading vs. lagging indicators and why you chose one over the other
  • Trade-offs between precision, recall, or other competing metrics
  • How metrics influenced prioritization and resource allocation
  • Validation methods such as A/B testing, cohort analysis, or statistical significance
  • Lessons learned and how you would refine metrics in hindsight

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.