Turn Problem Statements Into Inputs and Outputs

In Algorithm Examples In Everyday Life, we saw that algorithms are ordered procedures for solving problems.

Now we move one level closer to interview code: before you can design the procedure, you need to know the starting materials and the required result.

That means translating a problem statement into:

Inputs  ->  Algorithm  ->  Output

Many interview mistakes happen before the algorithm begins. A learner reads too quickly, starts coding, and later realizes they returned the wrong thing, ignored a constraint, or solved a slightly different problem.

This lesson is about preventing that.