Skip to content
Crunchyroll, LLC

Senior Software Engineer

Los Angeles, California, United States; Los AngelesUnited States
Senior · Engineering: Emerging Technology
POSTED 14 OCTVERIFIED 57M AGO
Apply Ask
Role
28 days opentrue age
Closes in ~21d at the median (49d)
Posted 14 Oct · n=15
Payats field
$183k–229kposted
▲ +25% vs market median $165k
$155k$229k
Market p25–p75
$155k–$185k
Crunchyroll, LLC p25–p75
$188k–$206kn=3
Los Angeles · n=555 · 365d to 12 Nov
CompanyCrunchyroll, LLC →
100open roles
Opened · 30d
+12
Closed · 30d
−12
9d of snapshots · 30d window
Market
17,125open · Senior Software engineering
Opened · 7d
+1,3048% of open
All software engineering
75,472open
All tracked boards · live 12 Nov · n=17,125
Visa
✓licensed sponsor
UK licensed sponsor
✓Worker (A rating)
Checked 9 Nov
TypeScriptPython

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!

About the role

In the role of Senior Software Engineer for Concepts Lab, you will report to the VP of the Concepts Lab.

We are considering applicants for the location of Los Angeles, CA (onsite).

As a Senior Software Engineer in Concepts Lab, you will take the lab’s validated experiments into production and embed directly with the teams who will run them long-term. For a defined period on each engagement, you will work inside a delivery team’s codebase and processes, building out the experiment to production quality, then hand off ownership, runbooks, and documentation so the team can carry it forward without you. The lab moves in short cycles, so you will decide when to prototype quickly and when to build something meant to last, and each engagement ends with a real handoff, not a demo.

The team is small, which makes your work visible: the systems you build become the foundation the receiving team adopts, and the standards you set for testing, documentation, and release safety become the standard they inherit. You will also share in the operational ownership of what the lab runs, on a rotation across the team, until handoff is complete. Success in your first year looks like experiments that graduated into long-term teams because the engineering under them held up, and because the handoff itself was clean.

Core Areas of Responsibility

  • Build and help deliver experiences to our internal experimental environment. Own its reliability, deployment path, and the ability to stand a new experiment up quickly.
  • Design, build, and ship the software behind the lab’s experiments directly inside production environments, turning unclear asks into a crisp plan and a milestone path.
  • Embed with delivery teams for the duration of each engagement, working within their systems and conventions to implement and build out the lab’s experiments.
  • Own production health during the engagement, including security patching, dependency upgrades, bug reduction, scaling work, runbooks, and documentation, shared on a rotation across the team.
  • Set the technical bar for the lab’s software work, including design reviews, code quality, test coverage, observability, cost management, and security practices.
  • Lead the handoff of validated experiments to the long-term owning team, so what graduates out of the lab arrives documented, supportable, and fully owned by the receiving team.
  • Mentor the engineers and contractors who collaborate with us, contribute to hiring, and help shape how Crunchyroll Engineering builds software.

About You

We get excited about candidates, like you, because...

  • You have 8+ years of professional software engineering experience building and operating production systems.
  • You have designed systems with multiple components interacting across API or service boundaries, and you anticipate the failure modes before they reach customers.
  • You write production-grade Python and/or TypeScript and have built software that other engineers chose to adopt because it made their work easier.
  • You have built and maintained CI/CD pipelines and integrated automated testing into them.
  • You use AI, including agentic coding tools and workflows, to accelerate complex delivery, refactors, and migrations while ensuring correctness and production safety.
  • You have carried operational ownership for services you built: runbooks, diagnostics, and incident follow-through.
  • You have experience working in early-stage, ambiguous environments where you define the problem as much as you solve it, and you know when to prototype quickly versus when to build for the long term.
Source · Crunchyroll, LLCFirst seen 4 NovOriginal ↗