I&#x27;ve been wondering about the tells&#x2F;cues a hacker should be on the look out for when interviewing with startups. Like, if Person X does Action Y, it could potentially beget Outcome Z where Z is something favorable or unfavorable. Not, of course, X and Y always imply Z, that would be taking things a step too far.<p>Excluding the obvious bad signs (&quot;the CEO roared and threw a dev against a wall iron man style&quot;) what kinds of small technical or cultural subtleties do you automatically notice when interviewing?
Tells when interviewing with a startup?