Python Programming Foundations

Expected answer
input() returns text, so age is a string and cannot be added directly to an integer. Convert and validate the value at the input boundary, for example with int(age), while handling invalid user input explicitly.

Why this answer works
The interview signal is whether you trace types through execution instead of guessing at the error. External input begins as untrusted text. Converting close to the boundary makes the program’s internal assumptions clearer, but conversion can fail, so robust code decides what to do with blank, malformed, or out-of-range values rather than scattering casts throughout later calculations.

Review the relevant lesson →

Expected answer
Assignment binds another name to the same mutable list object; it does not clone the list. Create a separate shallow copy with list(existing) or existing.copy() when independent top-level mutation is required.

Why this answer works
This tests the difference between names and objects. The useful trace is to ask whether the operation creates a new object or mutates an existing one. A shallow copy is enough for a flat list, but nested mutable objects can still be shared, so a strong answer distinguishes shallow copying from the rarer need for a deliberate deep copy.

Review the relevant lesson →

Expected answer
Use a set when the requirement is unique membership rather than positional order. Set membership is typically constant expected time, while scanning a list grows linearly with the number of stored IDs.

Why this answer works
The important skill is matching the data structure to the operation. Lists are valuable when order, duplicates, or indexing matter; sets express uniqueness and fast membership directly. A strong answer also notes that changing structures can change ordering semantics and that performance claims should be understood as expected behavior rather than a universal guarantee.

Review the relevant lesson →

Expected answer
Python evaluates the chain from top to bottom and stops at the first true branch. The broad >= 60 condition captures 95 before the more specific >= 90 condition is reached, so the conditions should be ordered or rewritten to reflect the intended ranges.

Why this answer works
This is an execution-tracing question. Do not read every branch as if it were independently evaluated. For mutually exclusive ranges, trace the first condition that becomes true and ask whether earlier conditions accidentally contain later cases. Reordering from most specific/highest threshold downward is one clear fix when that matches the domain rules.

Review the relevant lesson →

Expected answer
Extract the business rule into a function with explicit inputs and a returned result, then have each caller supply its values. Keep input/output or unrelated state outside the function unless those effects are part of its responsibility.

Why this answer works
Interviewers are looking for more than “use a function.” A good boundary names one responsibility, makes dependencies visible as parameters, returns a useful value, and can be tested independently. Copy-pasted formulas drift over time; centralizing the rule reduces inconsistent fixes while avoiding a giant function that mixes calculation, user interaction, and unrelated side effects.

Review the relevant lesson →