Data Engineer
Braintrust
| Company | Braintrust |
| Category | Engineering |
| Location | San Francisco |
| Remote | On-site (inferred) |
| Employment | Not stated |
| Level | Not stated |
| Salary | Not stated by the employer |
| Posted | 13 Jul 2026 |
| Last verified | 30 Jul 2026 |
| Source | Employer career page (ashby) |
Description
ABOUT THE COMPANY
Braintrust is the agent observability platform. By actively applying intelligence to agent traces and automatically surfacing the most critical patterns, Braintrust gives teams the visibility to understand how agents behave in production and the tools to improve them.
Teams at Notion, Stripe, Box, OpenAI, and Cloudflare use Braintrust to trace their agents, find the issues in their observability data, and run evals that tell them how to improve.
ABOUT THE ROLE
Braintrust is growing quickly across enterprise and self-serve customers, and our internal systems need to scale with us. You will build and own the data infrastructure that will power how our business operations and systems function. This is a hands-on, solo role for now. You won't be joining a team with mature processes already in place. You'll be building the queues, workers, and data models, on top of a warehouse that already has solid foundations (health scoring, ARR movement, engagement facts) but no activation layer.
The right person has strong technical depth, understands how GTM teams work, and is excited to build with AI. You should have strong opinions about where agents can automate operational workflows, and the judgment to build the data systems, context, and feedback loops that make those workflows work.
You'll partner with Product and Engineering on usage data and event schemas, and work directly with Sales, RevOps, Marketing, and Finance to turn one-off requests into reusable platform primitives (routing rules, scoring models, activation contracts) instead of one-off scripts.
WHAT YOU WILL DO
- Build and own the customer data platform: a company/event/signal spine that resolves identity across Salesforce, product, and marketing sources into one queryable universe.
- Design the queues, workers, and models that power enrichment, account routing/assignment, and activation
- Build the account scoring and routing engine that determines account ownership (AE-owned vs. house/hedge pools), with every decision explainable and reversible.
- Integrate external data sources across CRM, sales engagement, ads, and enrichment/intent vendors, and handle vendor APIs, web hooks, and rate limits.
- Push signal outward, not just model it. Reverse-ETL into Salesforce, Slack digests that surface risk and opportunity before someone has to go looking, eventually activation into ad platforms.
- Partner with Engineering and Product on usage data and event schemas as the product surface grows.
- Design row- and column-level governance (who can see which accounts, which fields) as a first-class part of the data model, not an afterthought bolted onto Snowflake permissions later.
- Debug production issues across the full path: Snowflake, dbt, orchestration, vendor APIs, web hooks, and the downstream systems (Salesforce, Slack) that depend on the output being right.
- Use AI to accelerate your own build, and design the data layer (clean context, structured inputs, feedback loops) that future GTM agents (account research, pre-call prep, follow-up) will run on top of.
ABOUT YOU
- You’ve built data platforms, backend systems, workflow engines, or data/ML infrastructure. This is a platform-engineering role, not a dashboards-and-reporting role.
- Deep experience with analytical data systems: Snowflake, dbt, and an orchestrator (Dagster, Airflow, or similar).
- Comfortable writing production backend code, not just SQL. This role involves queues, workers, and stateful jobs (e.g., on AWS Batch/Lambda), not only transformation models.
- Clear judgment about data modeling, schema evolution, contracts, and lineage, with an instinct for what happens to a model six months after you ship it.
- You care whether a workflow actually works end to end: whether the rep trusts the Slack ping, whether the routed account was routed for a reason someone can state in one sentence.
- Strong debugging instincts across a multi-system path: a broken pi
991,236 openings. Erioun finds yours.Scored against your own profile, every hour.Try the radar →