Poor names lead to confusion and errors. Frame the concept in practical terms so you can explain it during interview discussion.
If a method name doesn't reflect its purpose, it can mislead developers. Naming a method `doStuff()` instead of `calculateTotalPrice()` obscures its function.