The "Just Say No" Engineer Is Dead, and Nobody Agrees on What Killed It

An HN post argued that the 'just say no' engineer, the senior IC who blocks initiatives on principle and gets away with it, was a ZIRP-era phenomenon that has no place in the current market. The framing generated real debate. Some commenters agreed: in a world where headcount is scrutinized and engineers need to show impact, sustained obstruction is a career risk. Others pushed back, arguing the 'no' engineer is often the only person preventing a team from shipping something that will cause problems six months later.

This thread connects to a broader hiring anxiety visible across both HN and Reddit. Founders on r/startups described the hiring process itself as so overwhelming they defer it indefinitely, describing ghosting, fake resumes, and hours spent on screening as a second full-time job. The UC system's IT workers forming the largest tech worker union in the US, combined with Uber and Lyft drivers forming the first US ride-share union in Massachusetts, suggests labor organizing is spreading into tech-adjacent roles in ways that will complicate hiring calculus.

The through-line: the relationship between employers and technical workers is being renegotiated from multiple directions simultaneously. Companies want more productivity with fewer people. Workers are organizing to protect what they have. And the tools that were supposed to resolve this tension (AI coding agents, automation) are generating their own management overhead.