I'm very much NOT interested in code quality from an engineer. I very much AM interested in how an engineer thinks and approaches solving a problem.
One way to start that conversation is to have a code portfolio that they can talk to. Why did you do this? What were thinking about when you did that? Did you start writing some code then refactor? Did you think about the problem for 3 days before you started writing? Do you diagram on paper? Did you model the data structures before you modeled the application itself?
These are the sorts of questions I'm interested in when I hire someone; They're also the sorts of questions I want someone who is hiring me to be interested in.
Using your words:
To me, writing code is an artistically creative process as well, which takes talent. I wouldn't hire an engineer if I don't perceive their thinking as beautiful
The process for creativity doesn't change just because the expression changes. Compare the process of writing code with that of painting and you'll find a lot more similarities than differences.
PG even wrote a book about it.