How do we build engineering resilience at Carta
summary
Three concrete practices drive resilience: prioritize one-on-ones to surface patterns (career goals, personal crises, tool complaints), publish plain-language weekly updates in Slack and monthly all‑hands, and reorganize ownership around teams not people (tripod: PM, EM, designer). Metrics track team throughput, not individual velocity, and career conversations are company‑agnostic career plans. Removing layers for a fundraise team gave them direct exec access and accelerated delivery. Core engineering headcount grows from 53 to about 75 while the central team stays intact.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:51Constant reorganizations at Carta
- 3:39Traditional resilience limits
- 5:47Listening to individuals
- 8:36One-on-ones reveal needs
- 11:51Turning insights into action
- 14:44Treat humans as humans
- 15:45Open communication builds trust
- 17:31Career development discussions
- 20:03Plain language updates
- 21:07Trust the group
- 22:53Mindset for change
- 24:19Tripod framework for teams
- 26:05Three-step resilience framework
- 26:48Q&A
related talks
33mAn Engineering Team Where Everyone is a Leader
40mThe Joys of Managing Engineering Teams
09m"The Joys of Managing Engineering Teams"
28mBuilding Resilient Tech Organisations to Survive and Thrive
31mFrom Engineer to Engineering Manager
34mAn Engineering Team Where Everyone is a Leader
46mHow to scale a unicorn-building engineering team (and stay sane)
43mThe Joys of Managing Engineering Teams