Technical ability isn't going to help nearly enough if they don't understand software engineering principles. What SDLC methodologies have they used? What do they like and don't like? What source code tools do they like? What is Brooks' Law? How do they work with QA? Have they supported software they have released or has it gone to another team?
And understand their answers. Say they don't like the daily Scrum in their AGILE environment. Why? Is it because it's pointless in that environment - no real problems are addressed, brought up, no code is reviewed, no items gone over? Or do they just find it boring?
Technology is important. It's also important to have engineers and not programmers. 10 times out of 10 I'd hire and engineer with proven SDLC experience without the specific experience in the specific technology at hand*. My experience is that having an engineer that uses and respects the processes in place is infinitely more valuable than getting someone with mastery of the technology.
*Within reason. I'm not hiring a LAMP expert for an embedded C job, but hiring a LAMP expert for a web-based Java job? Yeah, I'd consider that.