I sympathise. I think the best way is to ask lots of questions in your interview. Developers are in demand, so asking some probing questions about the process i

I sympathise. I think the best way is to ask lots of questions in your interview. Developers are in demand, so asking some probing questions about the process is not going to hurt your chances at all. If anything it'll improve your standing. Ask about the development process, what documentation gets produced, and what tools they use. Then listen carefully to the answer. Ignore the buzz words, and focus on actual tangible artifacts. Saying "we're agile" or drawing a flow chart on the white board doesn't mean anything. Can they show you the scope of the current sprint? A Kanban board? A burndown chart? Some wireframe drawings? If they can't show you anything tangible, that's a warning sign.