Explain what you built, and your part in it

🏠The everyday picture

A contractor who built a house with a big team can still walk you through it: why the stairs are here, why this beam is steel, what went wrong with the plumbing and how it was fixed. Nobody expects the contractor to have laid every brick, but everyone expects them to understand every room. With AI as your fast team, you're the contractor.

📘What it really is

Interviewers for builder roles often ask you to explain a project and then change something in it. They're checking four things:

Do you understand the parts? Frontend, backend, database, where it runs (System design, Lesson 1).
Can you explain your decisions? "I chose X over Y because..."
Did you check the work? What you tested, and how you knew it was right.
Can you handle a problem? One bug or setback, how you found it, and what you did.

A simple shape for telling any project story is situation, task, action, result, and what I learned:

Situation: the shop kept running out of atta.
Task: I needed a way to warn them before it happened.
Action: I planned the app, chose a Google Sheet as the store, had AI write the first version, and tested it with made-up data.
Result: in a week of use, the shop didn't run out of anything on the list.
Learned: test the exact edge, such as "exactly 5 left", because that's where my bug was.

📝A worked example

Interviewer: "Did you write this code yourself?"

Weak answer: "Yes, all of it." (If they ask about one line and you can't explain it, trust is lost.)

Also weak: "No, the AI did it all." (This hides the real work you did.)

Strong answer: "AI wrote most of the first draft from my one-page plan. I chose the tools, reviewed each change before accepting it, tested it, and fixed the reorder bug myself. I can walk you through any part. For example, here's how the reorder check works..."

🖱️Try it

Pick your project from Lesson 1 and practise out loud:

Explain it in one minute using situation, task, action, result, and what you learned.
Ask an AI: "Act as an interviewer. Ask me five questions about this project, one at a time, including one where you ask me to change something." Answer each without looking anything up.
Note the question you found hardest, and go and understand that part properly.

✅Quick check

You're asked about a part of your code you don't understand. What's the best response?

Show the answer

Be honest: say which part AI wrote and that you haven't studied it closely yet, then explain how you would find out (read it, test it, ask). Then go and learn it after the interview.

What's the "result" in a project story?