Skip to lesson
Exit
The Role & Your Charter1 / 2

1 min lesson

Knowing the pillar boundaries earns credibility

Use two rows in "Knowing the pillar boundaries earns credibility" to state the practical decision rules.

Step 1 of 2

Knowing the pillar boundaries earns credibility. Cursor runs a separate growth data-science posting. That seat lives in monetization and self-serve product growth: activation, conversion, expansion. Yours lives in stability and agent-harness performance. Naming that contrast unprompted shows you read the org, not just one JD.

Dimension
Unit of value
Performance & Reliability DS (this role)
Product stability and harness performance
Growth DS (separate role)
Acquisition, conversion, expansion
Dimension
Core metrics
Performance & Reliability DS (this role)
Latency, error rate, agent success, SLOs
Growth DS (separate role)
Activation, retention, revenue, funnels
Dimension
Typical question
Performance & Reliability DS (this role)
Did this deploy degrade reliability?
Growth DS (separate role)
Did this change lift conversion?
Dimension
Main partner
Performance & Reliability DS (this role)
Engineering and infra
Growth DS (separate role)
Product and marketing/growth

Same company, different charters - don't pitch a growth playbook for a reliability seat.

The gatekeeper anti-pattern

The fastest way to fail the collaboration round is to position yourself as the owner of the dashboards who others must come to. The JD prizes the opposite: making engineers self-sufficient. If your stories sound like 'I controlled access to the data,' reframe them as 'I made it so the team didn't need me to answer that anymore.'