FluidStack
Software Engineer, Applied AI
About this role
Join Fluidstack's software engineering team to build core infrastructure systems powering AI-driven data center design and operations. You'll own end-to-end domain modeling, authorization, and orchestration systems while enabling AI agents to safely operate critical infrastructure.
What you'll do
- Design and implement core system primitives including entity ownership, authorization, audit trails, and orchestration
- Develop and maintain domain models representing power systems, data centers, and hardware as composable entities
- Build interfaces to ingest and process vendor data in formats like KMZ, BIM, and Revit
- Create tools and guardrails for AI agents to safely operate infrastructure systems
- Automate site design generation from unstructured vendor documentation
- Build dynamic project delivery scheduling systems that update as conditions change
What they're looking for
- Domain modeling and abstraction design
- Authorization and policy engines (OPA, Zanzibar, RBAC/ABAC)
- Workflow orchestration (Temporal, Cadence, Airflow)
- AI tooling and agentic frameworks (Claude, Cursor, LLM APIs)
- Unstructured data processing and extraction
- Geospatial and BIM format handling
- Go, TypeScript, or Python
- Event sourcing and audit systems
Benefits
- Competitive salary and equity package
- Health, dental, and vision coverage
- Retirement or pension plan aligned with local norms
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
FluidStack
FluidStack builds AI infrastructure at scale, developing data centers and warehouse operations designed to handle gigawatt-capacity compute deployment. The company is hiring for warehouse engineers, data center operations specialists, product engineers, and people leaders to support rapid infrastructure expansion across multiple sites.
- Website
- fluidstack.io
Likely interview questions
- Tell us about a time you had to model a complex, messy domain into something usable. What went wrong initially, and how did you fix it?
- You'll be building core primitives like authorization, audit, and orchestration that other teams depend on. Walk us through how you'd approach designing one of these systems for long-term correctness.