Our Take
Linguistic markers of status are not new; what matters is whether 'vibe' judgments are replacing evidence-based evaluation in teams building AI systems.
Why it matters
In fast-moving AI shops, informal language often encodes real decisions about resource allocation and hiring. If 'vibes' override metrics, you've got a culture problem that will eventually show up in your product decisions.
Do this week
Engineering leads: audit your last three project-kill or hire decisions for explicit criteria versus vibe language in the reasoning, and document the gap before your next planning cycle.
Vibe Checks Have Become Standard Practice
The New York Times reports that workplace vocabulary now includes "high-signal" and "anti-signal" as shorthand for assessing ideas, people, and fit. The terms originated in technical contexts (signal-to-noise ratio in data) but have migrated into general performance and culture evaluation. Teams use "vibe" language to describe whether a candidate, proposal, or collaboration "feels" aligned with team values or output quality.
The trend cuts across industries but appears most prevalent in fast-moving sectors where hiring and decision-making happen quickly. The language serves as a cultural compression mechanism: rather than enumerate specific competencies or measurable outcomes, teams collapse judgments into affective categories.
Informal Language Masks Real Power Dynamics
Vibe-based evaluation is not inherently flawed. Teams do benefit from assessing cultural fit and communication style. The problem surfaces when "high-signal" becomes a post-hoc rationalization for decisions already made on other grounds, or when it displaces explicit criteria that can be audited and improved.
In AI-focused organizations, this gap is particularly acute. ML teams especially are vulnerable to unexamined biases baked into hiring and project prioritization because the work itself involves probabilistic judgment. When that judgment language spills into team dynamics without friction, you lose the ability to distinguish between signal and noise in your own decision-making.
The cost is real: hiring decisions that rely on vibe over pattern, project cancellations that can't be explained to stakeholders, and institutional memory that evaporates when the person who "knew the vibe" leaves.
Demand Explicit Criteria Before Vibe Talk
Make it a discipline in your org: any hire, project kill, or resource decision gets documented with both qualitative reasoning (culture fit, communication style) and quantitative criteria (velocity, error rate, specific skill gaps). Separate them visibly. Name the vibe assessment after the fact check, not before.
In practice: "This candidate scored 7/10 on system design and 6/10 on communication clarity, and they felt like a good fit for the team because they asked strong questions in the interview." Not: "Great vibe, let's bring them in."
This is not anti-intuition. It is anti-mystification. The best teams trust their judgment and verify it.