Startup Culture & The Human Element

Summary

This piece argues that real engineering culture is revealed under pressure, not in perks or value statements. It challenges common startup myths around culture, equity, hiring, ownership, and pace, and offers a blunt, experience-based framework for building durable engineering teams.

Key Ideas

1. Culture Is What Happens When Nobody's Watching

• Perks (like ping pong tables) often signal a lack of serious thought about culture.
• Real culture shows up in:
• Slack threads after incidents
• How teams talk about missed deadlines
• Whether leadership prioritizes customers or investors when things go wrong
• The gap between stated values (e.g., psychological safety, blameless postmortems) and actual behavior under pressure is the true culture.
• A litmus test: what a junior engineer does at 11pm when something breaks and nobody senior is online.

2. The Equity Trap

• A realistic comparison: FAANG comp vs. early-stage startup comp.
• Example: $200K at FAANG vs. $140K + 0.25% equity at a Series A.
• Forgone salary over 4 years: ~$240K, with high risk the equity is worth $0.
• Equity isn’t a scam, but it is a risky bet.
• The real problem is when founders use equity to discount salary without being transparent about:
• Failure rates
• Dilution
• Liquidation preferences
• Engineers eventually do the math and leave if they feel misled.
• Prescription:
• Pay as close to market as possible.
• Be explicit and numerical about equity, risk, and upside scenarios.

3. Hiring Hungry, Not Desperate

• Two types of candidates:
• Hungry: believe in the mission, want ownership, energized by ambiguity.
• Desperate: just need a job and took the first offer.
• Both sound good in interviews; the difference shows up in month three.
• Practical filter: ask what they’d change about your technical approach if they joined tomorrow.
• Hungry candidates have opinions, push back, and show homework.
• Desperate candidates mirror your own talking points back to you.
• A bad culture fit is multiplicatively harmful:
• Drags down team morale and productivity.
• Drives away the best people who have options.
• Effective replacement cost for a senior engineer ≈ 6–9 months of salary.
• Guideline: hire slower than feels comfortable; fire faster than feels kind.

4. Ownership Isn’t a Buzzword

• “Flat org” is often empty signaling, like a ping pong table.
• Real ownership looks like:
• Engineers can deploy to production without begging for permission.
• The builder of a feature talks to at least one real customer affected by it.
• The person closest to the problem makes the architectural call and defends it with reasoning.
• Anti-pattern: no deployment authority below senior level.
• Leads to shipping bottlenecks and a mindset of “I finished my tickets” vs. “we shipped X.”
• Ownership requires both:
• Accountability for decisions and outcomes.
• Genuine psychological safety so people can admit mistakes without fear.
• Without both:
• Accountability without safety → fear.
• Safety without accountability → theater.

5. The Burnout Math

• Analogy: farm equipment during harvest.
• You can push hard for a short window, but you must maintain the system or you lose the crop.
• In engineering:
• 60-hour weeks can work for 6–8 weeks of crunch.
• Beyond that, defect rates rise, architecture quality drops, and top performers start leaving.
• Crunch culture often hits a wall around month 18 with a spike in attrition.
• Replacement flywheel:
• Losing a senior → 2–3 months recruiting + 2–3 months onboarding.
• Remaining team absorbs extra load → accelerates their burnout.
• Sustainable pace is framed as a business decision with ROI, not a soft perk.

6. What to Tell Startup CEOs

1. Pay people honestly.

• You don’t need to match FAANG, but you should be within ~20–30% and transparent about why.
• People will trade some cash for mission and respect, but not for deception.

1. Give decisions to the people closest to the problem.

• Trust engineers earlier than feels comfortable.
• Start with smaller domains: deployment pipeline, testing strategy, tooling.
• Use these as stepping stones to larger architectural ownership.

1. Protect time like you protect budget.

• Every meeting is an attention withdrawal.
• Run calendar audits; if a senior engineer is in 15+ hours of meetings weekly, they’re not doing senior engineering work.

1. Say the hard things early.

• Performance issues, equity resets, layoffs — communicate sooner than feels natural.
• People can handle bad news; they can’t handle being blindsided.
• Early honesty builds the trust that keeps people when they get higher offers elsewhere.

Closing Thought

Strong engineering cultures don’t come from perks, slogans, or prestige. They come from leaders who treat compensation honesty, decision ownership, time protection, and direct communication as core business levers. If any part of this exposed a gap between what you say and what actually happens on your team at 11pm, that gap is where the work is.

If you want to pressure-test your own situation with someone who’s seen these patterns repeatedly, you offer discovery calls at: https://cal.com/mdostal/meet