Do you evaluate naming during technical interviews?

[Kirchhoff-]

Naming is one of the most important skills in software development.

Good names make code easier to read, understand, and maintain. Poor naming, on the other hand, can make even a simple implementation difficult to follow.

Despite that, many interview tasks focus almost entirely on algorithms, while naming often receives little or no attention.

Do you evaluate naming during technical interviews?

If yes:

• What do you look for?
• Do poor names affect your evaluation?
• Have you ever rejected a candidate because of consistently poor naming?

If not:

• Why not?
• Do you think naming is something that can be taught after hiring?

I'd be interested to hear how different teams approach this.