Senior AI Solutions Engineer
About Crunchyroll Founded by fans, Crunchyroll delivers the art and culture of anime to a passionate community. We super-serve over 100 million anime and manga fans across 200+ countries and territories, and help them connect with the stories and characters they crave. Whether that experience is online or in-person, streaming video, theatrical, games, merchandise, events and more, it’s powered by the anime content we all love. Join our team, and help us shape the future of anime!As a Senior AI Solutions Engineer in Crunchyroll's AI Enablement "Build & Partner" layer, you are the dedicated AI partner for business functions like Content, Marketing, or Product. You embed within these teams to deliver tailored solutions based on their specific operational context. This hands-on role combines engineering with consulting, focusing on building production-grade agentic systems. You design and implement systems that plan, use tools, and maintain state - utilizing RAG pipelines and workflow automation, rather than just building simple chat interfaces. Your time in this role is split between stakeholder scoping and technical implementation. You own the full lifecycle, from task decomposition and model selection to orchestration, evaluations, and production deployment. You build on the central AI Enablement team's shared technical standards, approved tooling list, and architectural playbook, and feed your own patterns, reusable components, and lessons learned back into them so the whole organization benefits from what you ship. In this role, you will Embed deeply with your assigned business function - attend their meetings, map their workflows end-to-end, and learn their pain points firsthand before proposing changes Ask the most important question first: "Should we use AI here at all?" - be willing to say no, and when the answer is yes, choose the right kind of AI (agentic system, generative AI, classical ML, RAG, or simple automation) rather than defaulting to the most sophisticated option Spot which parts of a workflow are genuinely agent-shaped - multi-step, tool-using, decisioning tasks where autonomy adds value, versus where a deterministic automation or a single LLM call is the more honest answer Translate business problems into clear technical designs - architecture diagrams, data flow maps, integration points, tool selection, and explicit build vs. buy vs. integrate decisions you can defend to both technical and non-technical audiences Design agentic systems deliberately: decompose the task, define the agent's goals, tools, and action space, choose between single-agent and multi-agent orchestration, and specify how it plans, reasons, retains memory/state, escalates to a human, and stays within its guardrails Engineer agents for reliability rather than demos: handle failure modes, retries, tool errors, hallucination recovery, cost and latency budgets, human-in-the-loop checkpoints, and graceful degradation when a step fails Build evaluation an...