Software Engineer, Ontology

How We Operate

• Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role.
• Insane urgency. We drive everything forward as fast as possible.
• Reason from first principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins.
• Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward.
• Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world.

Examples of key problems the team is working on

• Reduce the latency from something happening to Fluidstack knowing about it. Index operational systems, documents, conversations, and telemetry as they change, so a delayed shipment or a rack coming online becomes usable context while there is still time to act.
• Give every entity in Fluidstack's domain a shared identity. Connect a machine’s design, order, delivery, deployment, and incidents even when each system describes it differently.
• Turn what Fluidstack knows into business signals. Compare plans with observations across sites, supply chains, and compute operations, and surface the gaps that matter as the company builds at gigawatt scale.
• Build a secure platform where agents can be first-class citizens. Give agents access within each user’s permissions, with every answer traceable to its sources, freshness, and gaps in the evidence.

Role Scope

• Build the index and graph engine that connect Fluidstack’s operational data, documents, and conversations as new information arrives.
• Define the entities, relationships, and identity rules that let teams contribute knowledge about sites, equipment, orders, and incidents.
• Detect meaningful changes and publish evidence-backed signals when observed state diverges from plan.
• Give engineers and agents fast, authorized ways to query the business, with clear provenance and freshness on every answer.
• Measure change-to-knowledge latency, answer quality, and signal quality against real operational questions and events.

What We're Looking for

The below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would.

• You’ve built and operated a foundational data system that multiple teams relied on to make decisions or run critical workflows.
• You’ve made heterogeneous data sources work as one coherent model that people and software can rely on.
• You’ve built data platforms with extensible models that let other teams bring new domains and questions into the system.
• You’ve built systems that turn a continuous stream of changes into timely, reliable signals for operations.
• You’ve worked directly with domain experts to define what their data means and which changes matter.
• You’ve made hard calls between correctness, freshness, query speed, and access control, then revised those choices using production evidence.
• Bonus: Temporal data models (Datomic, EAVT). Search and retrieval over unstructured data. Database or indexing internals. Formal ontology and semantic web standards (RDF, OWL, SHACL, SPARQL). Physical infrastructure or inventory systems.

We are committed to pay equity and transparency.

You will receive a confirmation email once your application has successfully been accepted. If there is an error with your submission and you did not receive a confirmation email, please email with your resume/CV, the role you've applied for, and the date you submitted your application-- someone from our recruiting team will be in touch.