Amazon·Software Engineer·Technical Phone Screen·Intermediate

Intermediate

Jul 2026

Summary

Amazon SWE interview with a language choice question that sounds easy but actually has a lot of layers to it. Walked away feeling like I talked too much without saying enough.

Questions Asked (1)

If you could pick any language for a front-end coding interview, would you choose JavaScript? Walk through the trade-offs against TypeScript or Python in terms of expressiveness, runtime quirks like types and hoisting, closures, standard library, and how readable your code looks to the interviewer.

Technical Trade-offs

Author's notes

I said JavaScript without hesitating, which felt right, but then I kind of fumbled the justification.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Acknowledge that JavaScript is often the default for front-end interviews, but frame your choice as context-dependent: for a front-end role, JavaScript or TypeScript is usually the pragmatic pick because the interviewer can easily follow along. Then systematically compare the three languages across the given dimensions, emphasizing that the best choice depends on the problem, the interviewer's expectations, and the company's tech stack.

Pro tip: Mention that at Amazon, where many teams use TypeScript for front-end and Node.js for back-end, choosing TypeScript can signal alignment with their stack—but always confirm with the interviewer if they have a preference, as some may prefer plain JavaScript for speed.

1. Clarify the context and constraints

Start by noting that the 'best' language depends on the role, the interviewer's familiarity, and the problem domain. For a front-end interview, JavaScript or TypeScript is typically expected, but Python might be acceptable if the focus is on algorithms.

2. Compare expressiveness and readability

Discuss how JavaScript and TypeScript offer similar expressiveness with modern ES6+ features, while Python is often praised for its concise, readable syntax. However, for front-end, JavaScript/TypeScript code is more directly transferable and readable to an interviewer familiar with the DOM.

3. Analyze runtime quirks: types and hoisting

Explain that JavaScript's dynamic typing and hoisting can lead to subtle bugs, whereas TypeScript adds static types to catch errors early. Python also has dynamic typing but no hoisting, which can make it more predictable for some.

4. Discuss closures and standard library

Highlight that closures are a fundamental JavaScript concept and are often tested in front-end interviews. Python also supports closures but with different scoping rules. JavaScript's standard library is smaller and more fragmented, while Python's is 'batteries included' and TypeScript inherits JavaScript's library plus type definitions.

5. Conclude with a balanced recommendation

Summarize that for a front-end interview, JavaScript or TypeScript is usually the safest choice due to ecosystem alignment and interviewer familiarity. If the role is more full-stack or algorithmic, Python could be viable, but be prepared to justify your choice.

Key Points to Mention

JavaScript's dynamic typing and hoisting can cause runtime surprises, while TypeScript's static types improve code reliability and readability.
Closures are a core JavaScript concept and often appear in front-end interview questions; Python's closures work but with different scoping (e.g., late binding).
JavaScript's standard library is minimal compared to Python's extensive standard library, but TypeScript adds type definitions and modern tooling.
Expressiveness: JavaScript/TypeScript with ES6+ features (arrow functions, destructuring) is highly expressive; Python is also expressive but less idiomatic for front-end tasks.
Readability to the interviewer: using the language the interviewer expects (often JavaScript/TypeScript for front-end) reduces cognitive load and demonstrates empathy.
At Amazon, TypeScript is increasingly used in front-end and Node.js services, so choosing TypeScript can show alignment with their tech stack.

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