Brainforge Knowledge

README

2 min read

Data Service — Operations Hub

Service Line: Data
Subservices: Data Platform, Data Modeling, Reverse ETL (proposal — see README.md Decision 6)
Practice Linear Initiative: Establish Data Service

Last updated: 2026-04-08

ResourceLink
Parent hubREADME.md
GTM offersdata
Practice boardLinear: Delivery — Practice → Establish Data Service
SL expectationsexpectations-by-cadence.md
Success metricssuccess-metrics.md

Current Direction

  • Current status: subservices and offer list are proposed by Head of Delivery
  • Next owner: Data Service Leads validate naming, merge overlaps, retire weak offers, and complete artifacts
  • Non-core retained motions: audits remain cross-cutting offer variants rather than a standalone subservice
  • Naming transition: Data Platform and Data Modeling are the preferred display names; older implementation references may still use Data Infrastructure and Analytics & BI
  • Reverse ETL: Subservice for outbound warehouse syncs / retainer-style reverse ETL work; Linear label reverse-etl — proposal pending HoD (knowledge/sales/services/README.md Decision 6)

Line-Specific Playbooks

PlaybookStatusLink
REST API → BigQuery (curl, schema, MERGE upsert)Draftapi-to-bigquery-ingest.md
dbt project setup🔴 Draft / TBD—
Snowflake migration patterns🔴 Draft / TBD—
Data quality frameworks🔴 Draft / TBD—
Data modeling standards🔴 Draft / TBD—
Semantic layer implementation patterns🔴 Draft / TBD—

Service Line Review Notes

Monthly summaries stored by date:

DateKey ThemesAction Items
2026-04-XX——

(Link to vault transcripts or notes as appropriate)

IC Growth & Standards

Hiring profile: (TBD — what makes a strong Data line IC?)
Leveling criteria: (TBD — junior → mid → senior in Data service)
Certification path: (TBD — dbt, Snowflake, or internal certs)

Cross-Client Patterns

Repeated technical debt, stack risks, or reusable assets observed across Data clients:

PatternClients AffectedStatus
———

Graph View