Cloud Machine Learning Engineer, Hugging Face (ex-EA)
Juan Julián Cea Morán is a Cloud Machine Learning Engineer at Hugging Face (Madrid; joined Jul 2025) working on making open-source models accessible and fast in the cloud — after five years at Electronic Arts; Universidad de Salamanca. NVIDIA agreed to acquire Hugging Face for ~$12.9B on 2026-09-03 ($11.9B to shareholders + up to $1B equity retention for HF employees joining NVIDIA; HF to remain an open platform; expected close H1 2027 pending regulatory approvals; antitrust runway + GPU-neutrality of the Hub are the live radar questions). No public X handle asserted. Named on the HF All Hands roster for the 2026-09-03 announcement.
Only public nodes listed.
1 entities geo-pinned · toggle People / Institutions · 40.4168, -3.7038
🔭 WATCH: enterprise logos versus pilots · compute contracts signed · open-weight versus API split
🔍 Juan Julián Cea Morán is carried at MEDIUM confidence on 1 filed source. The horizon below is a hypothesis with a shelf life, not advice.
Paste the badge on a site, a README or an agent page. It serves live from the edge and links back with its own attribution code.
Machine form: GET /badge/juan-julian-cea-moran.json
Paste a Base wallet and this record joins your watchlist. Nothing is uploaded, nothing is stored off-chain beyond the list, and removing it is one click.
Paste the badge on a post, a deck or a partner page. The image links home with ?ref=badge-juan-julian-cea-moran, so every embed is attributed in the referral ledger and every reader lands on this record.
JSON twin: /badge/juan-julian-cea-moran.json returns the same snippet for a generator.
Paste the badge on a post, a deck or a partner page. The image links home with ?ref=badge-juan-julian-cea-moran, so every embed is attributed in the referral ledger and every reader lands on this record.
JSON twin: /badge/juan-julian-cea-moran.json returns the same snippet for a generator.
Paste the badge on your own page. The image is edge-cached SVG, the link carries the attribution code, and the counter moves in the referral ledger.
The record is what it is: Cloud Machine Learning Engineer, Hugging Face (ex-EA). Nothing below is filed — it is the shape the seat would take if the current trajectory holds, and it is re-scored every time a new public source lands.
🔭 enterprise logos versus pilotsExpect the mandate to widen before it deepens. Watch whether the current seat adds an adjacent function to the seat rather than a bigger title on the same one.
🔭 compute contracts signedA second mandate is the normal move here — a board seat, a fund-side advisory role, or an operating chair next to the current one. The tell is a first public co-signature, not an announcement.
🔭 open-weight versus API splitFirst capital event window. Either a priced round behind the current seat or a personal vehicle appears. Watch open-weight versus API split rather than the headline valuation.
🔭 talent retention after the first raiseJurisdictional switch is the highest-probability structural change from Madrid, Spain. A second residence, a second entity, or a second currency book (EUR to a settlement unit) is the observable.
🔭 model-to-revenue ratioInstitutional shell forms: a holding vehicle, a family-office wrapper or a named co-investment club. Shells are quiet — the disclosure arrives through registry filings, not posts.
🔭 enterprise logos versus pilotsDistribution becomes the constraint. At this horizon the question is who carries the current seat's output and this seat's name, and on what terms. Watch talent retention after the first raise.
🔭 compute contracts signedSuccession pressure. Either a named deputy appears under the seat or the seat is re-scoped away from day-to-day. Both read as the same signal from outside.
🔭 open-weight versus API splitSecond-order liquidity: secondary sales, a tender, or a strategic minority into the current seat. This is where an OSINT file usually goes stale for six months and then re-prices.
🔭 talent retention after the first raiseRecord consolidation. By here the file should be readable as a single arc rather than a list of events, and the Madrid, Spain base stops being the interesting part.
🔭 model-to-revenue ratioEnd-of-horizon check. Re-read 2026 against 2036: the useful output is which of the eleven rows actually printed, and which were noise carried by the market rather than the person.
🔭 enterprise logos versus pilots🔍 Deterministic horizon model: every row is derived from facts already on this record and re-scored when a new public source lands. No forecast value is asserted.
Buy without a browser: GET /oauth/protected-resource, then tools/call fetch_profile over MCP. Bulk and 402 retries are idempotent on the same slug.
Machine pack: /api/um-radar/agent-pack?slug=juan-julian-cea-moranBatch / dataset pricing on request
The dossier prose stays public. The space around it is for sale: locales, frames, video, links, the city slot, the verified badge. Holding $UM cuts the price at quote time - the balance is read from your wallet, nothing is self-declared.
Public OSINT radar only. Not investment advice. Not a prediction engine.
Creator-fee revenue is onchain and verifiable.