Pipeline, warehouse, modern-data-stack, ML-engineering practitioners · 12 rooms · ranked by yield
dbt, MLOps, r/dataengineering, Modern Data Stack — where production-data orgs first leak hiring + roadmap.
Data-eng and ML-eng practitioner rooms. The audience overlaps with /infra-and-platform-eng-circles but indexes harder on data-platform and modern-data-stack adoption. Crossover with /ai-builder-rooms is intentional — same people, different lens.
Yield story
Primary surfaces are dbt Community Slack, MLOps Community Slack, r/dataengineering, r/MachineLearning, DataTalks.Club Slack, and Modern Data Stack forum — six rooms where data-platform repos most often first telegraph commercial plans.
Cadence
Weekly read on the six primary surfaces.
Caveat
Data-eng rooms reward operational precision. No marketing-shaped posts.
Yield breakdown · 12 rooms
6
Primary
Direct deal-flow surface. Multiple repos we surface first showed up here.
5
Secondary
Adjacent. Signals overlap, but rarely the first-mention surface.
1
Ambient
Culture / reading list. Useful for framing, not for sourcing.
Engagement status
0
Engage
8
Watch
0
Hold
4
Read
0
Blocked
The ranked roster
Primary first, then secondary, then ambient. Hand-authored order within each tier — top of tier = highest attention density.
dbt-practitioner Slack. Modern-data-stack adoption signal.
Production-ML practitioners. Crossover with AI-builder rooms.
Data-platform stack threads. High GitHub-org overlap.
Where ML papers and infrastructure orgs first surface.
Data-eng practitioner Slack. Cohort-of-engineers signal.
MDS vendor + buyer crossover surface.
Analytics-practitioner Slack. Niche but high-signal-density.
Hex-customer notebook community.
Data-science practitioner audience.
Experiment-tracking customers. Research-to-product flips.
HF discussion forum. Long-tail of model-product transitions.
Snowflake-power-user community. Adjacent buyer pool.
Frequently asked
Where the deal-flow signal actually lives
Reading data and ml engineering collectivesdoesn’t produce a deal. It sharpens the question we ask the GitHub-side telemetry. The actual deal-flow signal lives at /predicted, /firstlook, and the rest of the signal stack below.
Data and ML engineering collectives roster regenerated quarterly. Status flags update weekly. Companion platform map at /voices. Master mixed list at /target-list.