[blasdel]

Absolutely focus on the problems you've solved, and also the problems you failed to solve after getting deeply involved in them.

They know that you'll have to learn their proprietary technology stacks, which are always both ahead and behind the public stacks they inspired. At some companies they won't ask anything about your resume keywords after the phone screens.

Most Big 5 companies use what's called "Behavioral Interviewing" or "S.T.A.R." to formally assess how you get stuff done, and the technical questions can be answered in almost any language you like. Hell I've given successful answers to Big 5 "tell me about a time when you had to…" questions based on experiences in bicycle manufacturing and nonprofit administration, but it really has to involve ownership if you're straying from the norms.

[lgregg]

I'm good at "S.T.A.R.", most of my effort in the past is using CAR and PAR but it's not a hard shift. I'm glad to hear they don't limit it to just technology problems.

>"the problems you failed to solve after getting deeply involved in them". I have done it before in interviews when asked about weaknesses or failures; I've never done it on a resume though. How would you go about representing that on a resume?

[blasdel]

You don't put the failures on the resume as failures :)