Software Engineer, Frontend

About this role

Fluidstack is seeking a Frontend Engineer to own their public marketing website and internal operational dashboards as a key technical leader. You'll make architectural decisions, establish component systems, and ship high-impact interfaces that serve both external customers and internal teams scaling AI infrastructure.

What you'll do

• Lead technical architecture and performance optimization for the public marketing homepage
• Design and build React-based internal dashboards for data center management, procurement, and operational workflows
• Establish and maintain a shared React component library with Mantine/Tailwind, documented in Storybook
• Prototype and implement interactive experiences using Framer and modern animation techniques
• Manage CMS integrations (Webflow or equivalent) and decide when to use no-code versus custom solutions
• Collaborate with product designers, infrastructure engineers, and GTM teams to translate ambiguous requirements into implementations

What they're looking for

• React with TypeScript (3+ years production experience)
• Mantine, Tailwind CSS, or similar styling frameworks
• Storybook component documentation and library architecture
• Modern React patterns (hooks, context, server components, state management)
• Framer for motion and interactive prototyping
• Git workflows, CI/CD pipelines, and code review best practices
• AI-assisted development tools (Claude Code, Cursor, Codex)
• Webflow or similar CMS platforms

Benefits

• Work on civilization-scale AI infrastructure with direct impact on human freedom
• Collaborate directly with design, product, and engineering leadership
• Ownership of high-visibility public and internal products
• Opportunity to establish technical standards and component systems
• Fast-paced environment at one of the fastest-scaling AI infrastructure companies

Likely interview questions

• Tell us about a marketing website or public-facing product you shipped—how did you balance design fidelity with performance, and what metrics mattered most?
• Describe your experience building and maintaining a component library. How did you ensure adoption across teams and maintain accessibility standards?