&quot;How do you deliver software your users&#x2F;clients want?&quot; is really the only technical question you should need to ask the 10+ crowd.<p>The highly-experienced type of dev who could easily walk out of the interview and become your next competitor is the one you want to hire.<p>So, would you ask a competitor questions about one pattern, inner vs. outer joins, and naming conventions? Or would you use that time to actually learn&#x2F;discover info about your (potential) competitor?