Developer tools

Where to find customers who are data engineers

Data engineers are easiest to find when a warehouse bill, a failed DAG, or a dbt model is the villain — not when they are posting a medallion-architecture diagram. They compare Fivetran connectors, argue about Snowflake credit burn, and ask which orchestrator will not hide a silent schema break. If you sell ingestion, transformation, orchestration, observability for pipelines, a catalog, or anything that sits between a SaaS API and a dashboard, find them in r/dataengineering, the dbt Community Slack, Locally Optimistic, Discourse, and G2 threads on Snowflake, Fivetran, and Airflow. Ignore 'how do I become a data engineer' posts. Hunt comments that name a credit invoice, a connector that dropped a column, or a freshness SLA that finance already assumed was true. That is switching intent with a warehouse budget, not a bootcamp portfolio.

Where data engineers actually hang out

These are the rooms where data engineers ask for recommendations, compare tools, and name the competitor they want to leave. Start here before you buy ads.

Redditlarge
r/dataengineering
This is the default room for people who own warehouses and DAGs. Threads titled 'Snowflake credits doubled after we enabled search optimization' or 'Fivetran dropped a column and nobody noticed for a week' are buying notes. Commenters compare orchestrators, reverse ETL, and observability with enough credit numbers that you can tell whether your product is a fit. Search for named vendors plus 'credits,' 'schema drift,' and 'too expensive.'
Rules gotcha: Career-advice and bootcamp ads are a large fraction of the feed. Skip them. Disclose if you sell in the category. Do not paste a landing page into a 'how do I learn SQL' thread.
Slackvery large, analytics-engineering heavy
dbt Community Slack
The dbt Slack is where people debug incremental models at 6pm and then ask which warehouse still makes sense, which observability tool caught a silent null, and whether to replace an ingestion vendor. Channels for adapters, packages, and #advice-dbt-for-startups fill with 'we evaluated X and bounced because of Y' notes that never hit a G2 form. If your product sits next to dbt, this is where the comparison happens.
Rules gotcha: Vendor spam in help channels gets you a reputation fast. Answer the Jinja or the test first. Never scrape member lists. Threads are the culture; do not dump a pitch in the channel body.
Forumevergreen, searchable
dbt Community Forum
Discourse holds the long-form version of Slack: failed incremental strategies, package conflicts, and 'we outgrew our orchestrator' essays. People write complete sentences with model counts and warehouse editions. Search for your category plus 'credits,' 'timeout,' or 'migrating off.' Those posts are unusually good to reply to and unusually good training data for an AI draft if you already have a point of view.
Rules gotcha: Blatant product drops without a reproduction get ignored. The culture rewards specifics: model count, warehouse, and what you already tried.
Slackinvite-gated, analytics leaders
Locally Optimistic
Locally Optimistic is where analytics leads and data engineers compare org design and the stack that survived last year's credit shock. Conversations about hiring the first analytics engineer, killing a Looker instance, or leaving a managed Airflow happen with less Reddit theater. If your ACV is a few hundred a month and up, this room's problems match. The buying signal is a named vendor plus a team that already has dbt in production.
Rules gotcha: Invite is requested by email. Vendors who join only to hunt get remembered. Contribute a postmortem or a modeling note before a pitch.
LinkedInslower, higher ACV
Modern data stack threads on LinkedIn
Once a data team is selling dashboards to finance, they spend more time on LinkedIn than Reddit. Posts about Snowflake credit governance, Fivetran MAR, or 'we moved orchestration off Airflow' collect comments from heads of data who will forward a useful reply. A comment that names credit tags, a connector SLA, or a failed Monte Carlo rollout can become an internal thread.
Rules gotcha: Skip engagement-bait 'data is the new oil' posts. Reply under operator posts that include a credit number or a named vendor. Do not pitch in a hiring post.
Reviewsdecision-stage
G2 reviews of Snowflake, Fivetran, and Airflow
When a data engineer or analytics lead reviews Snowflake, Fivetran, dbt Cloud, Prefect, or a warehouse catalog, they are usually mid-switch. Filter 2–3 star reviews and company size 11–500. Cons paragraphs name credit surprises, connector lag, DAG UI that hides failures, and seats that finance will not fund. The substitutes widget maps the comparison you should be monitoring on Reddit and Slack.
Rules gotcha: Do not astroturf. Vendor replies on G2 are fine when you are named. Do not email reviewers because they mentioned credits.
YouTubelong-tail comments
Warehouse and dbt war-story videos
Creators who walk through a modern data stack collect comments from people copying the DAG and people who already hate a connector in the video. 'Fivetran MAR after we added HubSpot' and 'Airflow hiding failed sensors' are specs. Search for Snowflake, BigQuery, dbt, and Airflow plus 'too expensive' and read the comments, not the architecture diagram.
Rules gotcha: Product links under someone else's stack tour get hidden. Answer the commenter's warehouse, model count, and constraint in text.

How data engineers talk about their problems

Search and replies land when you use their words, not your category name. These phrases show up in threads when they are close to buying or switching.

Snowflake credit burn
schema drift
Fivetran MAR surprise
dbt incremental strategy
silent null in prod
Airflow hiding failures
freshness SLA
medallion architecture
reverse ETL broke Salesforce
warehouse edition lock-in
connector dropped a column

What data engineers complain about — and what that means

PainHuntr classifies conversations by intent: actively asking, comparing, frustrated, discussing, or a passing mention. The quotes below are the shape of demand, not a promise that a specific post is live today.

Frustrated
“Snowflake credits doubled after someone enabled search optimization on a table finance refreshes hourly. I do not need another catalog. I need tags and a kill switch before the invoice lands.”
r/dataengineering cost threads, G2 cons on Snowflake, and LinkedIn posts after a monthly warehouse invoice.
Comparing
“Fivetran vs Airbyte vs 'we will write the connector.' HubSpot plus Stripe plus a database we do not own. MAR is now a line item that outruns the dashboard it feeds.”
dbt Slack advice channels, r/dataengineering ingestion threads, and YouTube comments under stack-tour videos.
Actively asking
“Need pipeline observability that catches a silent type change before the CFO Slack channel does. Monte Carlo is a budget conversation. Open source is fine if I am not the on-call for the collector.”
dbt Discourse, Locally Optimistic Slack, and HN comments on data-observability launches.
Discussing
“We put dbt everywhere and now nobody owns freshness. The analytics engineers want tests. The warehouse team wants fewer models. Leadership wants a number on a slide.”
LinkedIn modern-data-stack posts and slower Twitter/X threads after a dbt Coalesce talk.

Search queries that surface data engineers in buying mode

Paste these into Google, Reddit, or X search. They are the manual version of what PainHuntr runs when you paste a product URL.

site:reddit.com/r/dataengineering (Snowflake OR Fivetran OR Airflow OR dbt) (credits OR expensive OR switching)

site:discourse.getdbt.com (migrating OR expensive OR "we switched" OR timeout)

site:news.ycombinator.com (Snowflake OR Fivetran OR Airflow) (credits OR alternative OR expensive)

("data engineer" OR "analytics engineer") ("credit burn" OR "we moved off" OR "schema drift")

site:g2.com ("data engineer" OR analytics) (cons) (Snowflake OR Fivetran OR "credits")

site:youtube.com (Snowflake credits OR Fivetran MAR OR Airflow) (expensive OR alternative)

How to reach data engineers without getting ignored

Lead with the warehouse constraint they already named — credits, MAR, a dropped column, a hidden DAG failure — and answer that before your product appears. Data engineers reward people who have been paged by a silent null, not a brand that says 'trusted data.' A credit-tagging example, a dbt test, or a connector SLA beats a deck. Never ask them to book a demo from a dbt help thread. Offer a public cost model at their warehouse edition, a migration note, or a project with a broken incremental. If you sell usage-based ingestion, show MAR at their connector mix. Follow up in the same thread. Do not scrape Slack handles into a sequence. The fastest way to get banned from dbt Slack is a weekly drip to people who asked about Jinja.

Frequently asked questions

Are data engineers the same buyer as machine learning engineers?

They share warehouses and still buy different tools. Data engineers own ingestion, dbt, and the credit invoice. ML engineers own GPUs, training jobs, and inference latency. Pitching a feature store into a Fivetran MAR thread will miss. Pitching Snowflake cost tags into a CUDA OOM thread will miss. Use both pages and keep the vocabulary honest.

Where do data engineers complain about Snowflake and Fivetran?

r/dataengineering, dbt Slack and Discourse, G2 cons, and LinkedIn when finance sees the invoice. YouTube comments under stack tours. Watch for credits, MAR, and schema drift as buying criteria, not jokes.

Is the dbt Slack worth joining if I sell adjacent tools?

Yes if you will answer modeling questions for months. No if you want a lead list. Help channels are for Jinja and tests. Public Reddit, Discourse, G2, and HN are easier to monitor at scale. Use Slack only after you have a genuine adapter or a useful cost note.

How do I tell a career-switcher from a buyer?

Look for a named warehouse, a credit number, a connector, or a freshness SLA that another team already believes. 'How do I become a data engineer' is not a buyer. 'Search optimization doubled credits on a finance table' is a buyer. PainHuntr's frustrated and comparing labels exist for that cut.

What should I paste into PainHuntr if I sell to data engineers?

Your product URL plus the incumbent they already run — Snowflake, Fivetran, Airflow, dbt Cloud, a catalog. The engine looks for people asking for a replacement, comparing ingestion and orchestration, and venting about credits or silent failures. Pair that with the queries on this page if you still want to hunt by hand.

Related audiences

Reading 1,000 threads a month doesn't scale. PainHuntr does.

Paste your product URL. PainHuntr finds the conversations where data engineers ask, compare, and complain on Reddit, X, Hacker News, YouTube, and review sites — then helps you reply, track what worked, and do it again.

Join the waitlist to get early access and help shape the product.