Company Culture

The shared values, behaviors, norms, and unwritten rules that define how work gets done and how people treat each other at an organization — often the gap between what's stated and what's real.

Company culture is the set of values, beliefs, behaviors, and norms — written and unwritten — that characterize how an organization operates and how people within it interact. It determines how decisions get made, how conflict gets handled, what gets rewarded and what gets punished, and what it actually feels like to work somewhere day-to-day. Culture is often described as 'how we do things here' — the collection of habits and defaults that persist even when no one is watching and no policy document is consulted. Every company has a culture; not every company has the culture it thinks it has or claims to have.

The gap between stated culture and real culture is one of the most common sources of employee disillusionment. A company may prominently advertise values like 'transparency,' 'work-life balance,' and 'psychological safety' while operating with information hoarding, expectation of 24/7 availability, and a leadership style that punishes dissent. The real culture — what behavior is actually reinforced and what is actually penalized — is always more informative than the stated values on the website. Candidates and employees assess real culture through observation: who gets promoted, what leadership does under pressure, how mistakes are handled, and what happens to people who raise concerns.

Research on culture and performance shows strong correlations between culture characteristics and organizational outcomes. Companies with high psychological safety, clear values consistently modeled by leadership, and genuine investment in employee development outperform on innovation, retention, and long-term financial results. Culture is also notably sticky: it changes slowly, it reflects the people who built it (especially founders), and it tends to reassert itself after attempted changes unless leadership behavior changes durably. This is why company culture assessments and 'culture fit' hiring are taken seriously — they're not just preference matching, but predictions about whether someone will thrive, stay, and contribute.

How to Actually Assess Culture Before Joining

  • Ask specific behavioral questions in interviews: 'Can you give me an example of how the company handled a major mistake by an employee?' or 'What's something the company has changed based on employee feedback?'
  • Talk to current or former employees outside the formal interview process — LinkedIn or mutual connections. Ask what surprised them when they joined.
  • Read Glassdoor and Blind reviews looking for patterns across multiple reviews, not outliers. Themes in the 'cons' section are signal.
  • Observe interview behavior itself: how interviewers treat support staff, whether they're present or distracted, how they talk about their team.
  • Ask 'how are decisions made here' and 'how does leadership communicate during times of uncertainty' — these reveal decision-making culture and transparency in practice.
  • Trust your gut on what you observe, not what you're told.

Culture Fit vs. Culture Add

The traditional framing — 'culture fit' — asks whether a candidate will blend in with the existing culture. The critique is that it can become a proxy for hiring people who are similar to the existing team (same backgrounds, same personalities, same communication styles), which limits diversity and stagnates the culture. 'Culture add' reframes the question: does this person share the company's core values while bringing something the team currently lacks? This distinction matters most in growing organizations, where the culture of the current team shouldn't necessarily be the template for the future team — especially if that team lacks diversity of thought, background, or approach.

Example

Two candidates at the same company describe very different cultures. The first, who joined sales, describes a high-performance, competitive, results-first environment where individual achievement is celebrated and collaboration is optional. The second, who joined engineering, describes a collaborative, process-oriented team where psychological safety is high and failure is discussed openly. Both are describing the same company — subcultures within the same organization can differ more than cultures across different companies.