Turn this role into an interview — a resume and cover letter built around what this employer wants.
Starfish Storage manages petabytes of unstructured data for national labs, research institutions, fintech, and pharma, and is building an AI-native layer with MCP servers, agentic workflows, and local LLM deployments. Researchers and engineers will interact with storage infrastructure through tools that enable autonomous data actions and governance.
In this role you will develop MCP servers, deploy and tune local LLMs, create production-grade agents for real customers, and run in constrained
Your home office or our Waltham, MA HQ or hybrid
Starfish Storage is an established company that maintains a startup culture mindset. We cater to a diverse client base, serving industries such as life sciences, artificial intelligence, and research computing. Our technology is critical to modern organizations, helping customers organize, manage, and move the tens of billions of files central to their operations.
Most AI work right now is happening in the cloud, with managed APIs, and relatively clean data. Some of our customers can't do that: they're operating in classified or regulated environments with filesystem metadata spanning billions of files. The AI problems here are genuinely hard, the deployments are genuinely constrained, and the work actually matters to science and research.
If you want AI work that's genuinely constrained, genuinely consequential, and can't phone home to OpenAI — this is it.
Starfish manages petabytes of unstructured data for national labs, research institutions, fintech, and pharma, the kind of data that doesn't fit neatly into databases or cloud buckets. We're building an AI-native layer on top of that: MCP servers, agentic workflows, local LLM deployments, and tools that let researchers and engineers actually talk to their storage infrastructure. We're tackling hard questions too: should an agent be permitted to move 2PB of data autonomously? How do you govern that?
In this role, you'll build and ship MCP servers, deploy and tune local LLMs, write custom agents for real customers with real petabyte-scale problems, and get them running in environments where "just use the API" isn't an option. You'll also support customers when things don't work: which means you need to actually understand what you've built.