Anecdata: am doing interviews with prospective new people right now.
Things I care about in my software engineer hires (for whom this is not their first job):
* that you're able to talk about stuff you've done in the past, involving diving into technical detail at will, and showing some understanding of what was happening one level of abstraction below/above whatever bit you were working on. (I don't actually care what you did. Don't tell me proprietary stuff. I want to know that you understood what you were doing, why you were doing it, what it depended on and what depended on it, and that you are able to communicate this to me.)
* that you're familiar with the languages/tools/environments you said in your CV you are, and are able to communicate this to me
* that you have some general data structures+algorithms awareness, and ability to apply this knowledge to at least trivial problems rather than merely recite the textbook contents on demand
Anecdata: am doing interviews with prospective new people right now.
Things I care about in my software engineer hires (for whom this is not their first job):
* that you're able to talk about stuff you've done in the past, involving diving into technical detail at will, and showing some understanding of what was happening one level of abstraction below/above whatever bit you were working on. (I don't actually care what you did. Don't tell me proprietary stuff. I want to know that you understood what you were doing, why you were doing it, what it depended on and what depended on it, and that you are able to communicate this to me.)
* that you're familiar with the languages/tools/environments you said in your CV you are, and are able to communicate this to me
* that you have some general data structures+algorithms awareness, and ability to apply this knowledge to at least trivial problems rather than merely recite the textbook contents on demand