Member of Technical Staff, Data Systems

📋 Description

• Build the data plane for scientific results at scale: content addressing, lineage captured at write
• Scale the catalogs and query paths that make a billion-object corpus usable. Metadata operations
• Own the databases behind the platform, not just the object store. Transactional stores, analytical
• Own ingestion of the shared datasets every team depends on: scientific corpora, public data feeds
• Own the replicate-versus-fetch economics across storage tiers and clouds. What lives where, what it
• Understand data for AI, because that is what most of this data is for: training sets, eval corpora

🎯 Requirements

• Five or more years building data infrastructure in production at companies known for engineering
• You think in data identity: immutable content, names as pointers to versions, provenance that
• You have watched a catalog, namespace, or metadata service break before the storage under it did.
• You can produce a replicate-versus-fetch break-even from memory, argue a tiering decision in

🎁 Benefits

• Location: This role is based in Boston. Remote candidates may be considered on a case-by-case basis.
• Compensation: competitive salary, benefits, and meaningful early-stage equity.
• Culture: high technical bar with ownership from spec to ship to on-call, AI-native development