Describe the job the tool did
“I used React” says very little. “The dashboard had to update without reloading, so I used React for the interactive parts” shows you understood the problem. Start with the job, then name the tool.
Interviewers often follow up with “Why not X?” You don't need to know every alternative. Name one you considered and why you didn't pick it, even if the reason was “the team already knew this one.” That's a real reason.
Be honest about AI tools
If you used an AI assistant, say how: “I used it to draft test cases, then checked and fixed them myself.” That's a workflow, and it's more convincing than hiding it or claiming it wrote everything.
Be ready to explain any code you show. If there's a part you can't explain yet, say which part and how you'd learn it. Never present work as fully yours when it isn't.
Practise with Tool Talk Tuesday
Every Tuesday in the group, members post one tool and how they'd explain it. Use this template: “Tool: … / The job it did: … / Why this one: … / One limit I hit: …”
Reading other answers is practice too. Notice which explanations you understood right away, then borrow their structure.