Data Engineer, Analytics

Use-case intelligence is the part of se Revel that tells an SE leader which use cases predict a win, which combinations lift win rates, and which ones have quietly degraded. That data does not exist in any CRM, because it comes from what actually happened in the POC, captured as it happens, not typed in from memory a week later. You will own the pipelines, the Postgres models, and the metrics that turn POC activity, Salesforce data, Gong transcripts, and Jira and Confluence content into numbers an SE leader will bet a quarter on.

• Build and run the ingestion pipelines that pull POC activity, Salesforce data, Gong transcripts, and Jira and Confluence content into one analytical store, and keep them running when a vendor changes its API.
• Design the Postgres models that turn raw, organically captured events into clean facts about POCs, use cases, customers, and outcomes.
• Define and ship the metrics behind use-case intelligence: which use cases predict success, which combinations lift win rates, which ones are dragging, and how long a POC should really run.
• Structure transcript and ticket data so the AI worker can use it for insights and coaching, not just dashboards.
• Build the analytics SE leaders open every week, and stand behind the numbers when someone who has run a hundred POCs challenges them.
• Own data quality end to end: freshness, completeness, dedup across connectors, and what happens when a source changes.
• Document the models so a small team can build on them without asking you.

• Experience building and running data pipelines and warehouse models in production, where they have to keep working after you ship them.
• Strong SQL and solid Postgres experience: schema design, indexing, and query performance on large tables.
• Comfortable writing pipeline and transformation code in Type Script on Node. A Python background is fine if you are willing to switch.
• Hands-on with third-party APIs (CRMs, call recorders, ticketing tools): rate limits, pagination, backfills, and schema drift.
• Can take a vague question from a sales leader and turn it into a metric that is defined, measurable, and honest.
• Clear writer who works well async on a remote team.

• Experience with unstructured text at volume: call transcripts, tickets, meeting notes, and preparing it for LLM pipelines.
• Time spent in or near a Sales Engineering, Rev Ops, or sales analytics team.
• Predictive or scoring models built on sales data, and a clear view of where they go wrong.