Recevez plus de réponses des employeurs
Envoyez un CV adapté au poste en quelques minutes.
Carbonfact, a Paris‑based Environmental Intelligence platform for fashion, seeks an Analytics Engineer to own the metrics layer and governance.
You will transform SQL into a trusted, audit‑ready source of truth, work with Engineering, Data Science and Product, and ensure data quality never reaches customers.
Ownership of the semantic layer, contracts, tests, and CI gates, plus collaboration on product bets and AI tooling, define the role.
The fashion industry is responsible for 5–10% of global greenhouse gas (GHG) emissions. As climate pressure grows, fashion companies need carbon tools built for their reality, not generic platforms.
Carbonfact is the Environmental Intelligence Platform for textile and fashion. We turn messy business data into environmental intelligence so brands can measure, model, reduce, and report on their impact with confidence.
We’ve raised $17M from top-tier investors including Alven, Headline, and Y Combinator, and we’re trusted by brands like Carhartt, GANNI, On, Burton, Armedangels, Jack Wolfskin, and many more.
Our platform is organized around four pillars: Collect customer data through custom connectors, Measure impact from a single process to an entire brand, Reduce footprint through simulation tools and Report with audit‑ready, regulation‑compliant outputs.
As our first Analytics Engineer, you will own the layer that makes our numbers trustworthy. The footprint a customer sees, the KPIs our team steers on, and the data our AI agents query all flow through one metrics system. Your mission is to make sure data quality issues never reach customers.
We are scaling our teams, AI is accelerating our pace of innovation, and our data stack has grown faster than its ownership:
Our warehouse transformations run on lea, an open‑source framework born at Carbonfact, whose creator has since moved on.
Engineering has been maintaining a metrics layer that belongs with Data.
You will join the Data team as an individual contributor, reporting to Félix, our Head of Data. You will own the metrics system and work daily with Engineering, Data Science, and Product to keep every number consistent, tested, and documented.
Real items from our wishlist - the kind of work waiting for you:
One factory, three data sources. Factories share data through our suppliers platform, brands through the platform, and our parsing layer extracts factory information from customer files. You design the model that reconciles all three, so cross‑brand factory analysis becomes one clean query.
Converge the sources of truth. The same metric can currently be computed in up to five places! You fold them into one governed semantic layer for the platform, the team, and our AI agents.
Guard the per‑account view. A methodology change might look immaterial as a whole while capable of moving one customer’s footprint by double digits. You turn per‑customer checks into a pre‑merge gate, with a cost and runtime budget you define.
Documentation as a build artifact. Our warehouse has 276 SQL models and no column dictionary. Our parsing layer already generates docs from code; you bring the same discipline to the metrics layer, for humans and AI agents.
Own the SQL transformation layer that materializes our metrics in BigQuery: guidelines, contracts, tests, monitoring, and CI gates.
Build and govern the semantic layer that becomes the single source of truth for the platform, internal KPIs, and AI tools.
Implement and test the data contracts behind company KPIs, and challenge definitions that would not survive an audit.
Partner on product bets: define success metrics that survive scrutiny and implement their tracking on governed models.
Treat agent‑facing tooling as part of the data layer: Claude skills, MCP tools, and generated dictionaries.
Detect bad data early and route failures to the right owner, before a customer ever sees them.
Three traits matter more to us than any tool on your CV:
You thrive on complexity, yet manage to break things down to make them clear. The fashion industry and carbon accounting in general are more complex than it seems. We’re aiming to give clear environmental insights to customer with various degrees of data proficiency.
You have owned something, not just contributed to it, and were accountable when it broke.
You treat documentation as a build artifact: generated from source, tested and versioned.
And concretely:
Bonus points:
Semantic layer work: MetricFlow, Cube, LookML, or the Open Semantic Interchange direction
If you match most of this but not every line, apply anyway. We hire people, not skills.
If there is mutual interest to move forward, we’ll extend you an offer to join our team