Wow... that's the exact opposite of what I like to see. I want to see a thought process -- not someone throwing together code to get something there. When I've seen people like that get hired dealing with their code long term is painful. You tend to get "mostly working" code with a bunch of band-aids.

For an entry level position, getting an answer is important, but for more experience developers knowing how to figure out what actually is important (in my experience) is a better indicator (and yes, they actually need to be able to code).

Experiences vary though :)