Engineering Leader via Mutual Connection

SUBJECT LINE OPTIONS:
1. Tom suggested we connect, Lisa
2. Quick coffee chat - Notion's infrastructure scaling
3. Tom mentioned you might be worth chatting with

EMAIL:

Hey Lisa,

Tom mentioned we should connect - he knows I'm always fascinated by how companies like Notion handle infrastructure at scale.

Saw Notion's engineering team hit 374 people this year and you're actively hiring for cloud infrastructure roles. That level of growth (plus the whole data doubling every 6 months thing) usually means some interesting DevOps challenges around deployment velocity and system reliability.

We've helped a few fast-scaling product companies untangle similar growth pains - most recently helped a team go from 2-hour deploys to 15 minutes while cutting incident response time in half.

Worth grabbing coffee sometime soon? Would love to hear what you're working on, and happy to share what we've seen work (and fail) with other engineering leaders dealing with hypergrowth infrastructure.

Let me know if Thursday or Friday next week works.

Cheers,
[Your Name]

P.S. - Seriously impressed by the Postgres sharding work your team pulled off to handle that data growth.

---

PERSONALIZATION ELEMENTS USED:
- Mutual connection: Tom via LinkedIn
- Team growth: Engineering team at ~374 people, 30% of company headcount ([Unify Notion headcount data](https://www.unifygtm.com/insights-headcount/notion))
- Infrastructure challenges: Data doubling every 6 months, cloud infrastructure hiring ([Medium - Notion Database](https://medium.com/@nidhey60/how-notion-prepared-their-database-for-millions-of-users-dc198079e74c), [Notion Cloud Infrastructure role](https://jobs.ashbyhq.com/notion/e050309a-6b81-4341-b1ca-9bdd17e62e13))
- Technical achievement: Postgres sharding from 32 to 96 instances to handle data growth ([Onehouse - Notion's Data Scale Journey](https://www.onehouse.ai/blog/notions-journey-through-different-stages-of-data-scale))