jobctl

Senior Software Engineer - Kubernetes & Service Mesh

Roku - Bengaluru, India - original posting ->
Status
Open
Remote policy
Not stated
Employment type
Not stated
Salary
Not stated
Categories
220 - Cloud Tech
Tech
awsazuregcpdockergrafanakubernetesprometheusterraformgopythondevopssenior
Source
roku
First observed
2026-08-25 15:03 UTC
Last seen
2026-09-11 17:29 UTC
Source claims posted
2026-08-13 18:02 UTC
Consecutive misses
0 of 3

What the posting says

Teamwork makes the stream work.

Roku is changing how the world watches TV

Roku is the #1 TV streaming platform in the U.S., Canada, and Mexico, and we've set our sights on powering every television in the world. Roku pioneered streaming to the TV. Our mission is to be the TV streaming platform that connects the entire TV ecosystem. We connect consumers to the content they love, enable content publishers to build and monetize large audiences, and provide advertisers unique capabilities to engage consumers.

From your first day at Roku, you'll make a valuable - and valued - contribution. We're a fast-growing public company where no one is a bystander. We offer you the opportunity to delight millions of TV streamers around the world while gaining meaningful experience across a variety of disciplines.

What does the team work on?

Our Cloud Platform team builds the internal platform that Roku's engineers use to ship and operate software. We run Kubernetes and Istio service mesh at scale across multiple regions and clouds, and we obsess over making that platform easy to use so every engineering team at Roku can move faster and scale reliably.

What is the role?

As a member of the Cloud Platform team, you'll architect, build, and operate Roku's next-generation, multi-cloud platform powered by Kubernetes and service mesh at scale across multiple regions. This is a hands-on engineering role: you'll write code (Go and Python) and use Docker, Kubernetes, Istio/Envoy, Terraform, and scripting to solve hard compute, scale, and reliability problems, and to evolve the technology stack and deployments over time.

You'll research and introduce new technologies to improve scalability, reliability, and developer experience, and bake security best practices into infrastructure design and automation. You'll partner with engineering teams across Roku to migrate their workloads onto Kubernetes and Istio, and work with the Observability team to scale telemetry for a holistic view of the platform. Applying SRE principles, you'll keep the platform highly available, streamline onboarding, and build tooling that surfaces inefficiencies and optimizes cost across shared-tenancy clusters. You'll also mentor engineers and help define the best practices other teams build on.

How will I use AI at Roku?

At Roku, we don't just use AI, we work with it. AI agents and smart tools help power drafts, analysis, and repetitive workflows, while our people bring direction, judgment, and accountability. We're looking for curious, adaptable builders who can show how they've used AI or automation to move faster, raise the bar, and scale their impact.

We value your AI skills if you have built fluency across the agentic engineering toolchain, coding harnesses like Claude Code or Cursor, MCP servers, custom skills, or agent frameworks. And you can describe projects where you shipped real work with these tools. You know how to drive an agent, verify its output, and ramp on an unfamiliar codebase with an agent helping you.

What are the responsibilities of the role?

Architect, design, and operate Roku's multi-cloud, multi-region Kubernetes and service mesh platform

Solve compute and scale challenges by writing code (Go, Python) and using Docker, Kubernetes, Istio/Envoy, Terraform, and scripting

Proactively drive the research and implementation of new technologies to enhance scalability, reliability, and developer experience

Build security best practices into infrastructure design and automation

Build tooling to visualize inefficiencies and optimize costs across shared-tenancy clusters, including network traffic insights, cross-cluster communication efficiency, and cost attribution

Partner with product teams to migrate their workloads onto Kubernetes and Istio

Work closely with the Observability team to scale telemetry for a holistic view of the platform

Apply SRE principles to maintain high availability and streamline onboarding workflows

Design and build agentic systems and AI-powered tooling — e.g. agents, MCP servers, and automation — that improve platform reliability, developer experience, and operational efficiency

Mentor team members and help define best practices for infrastructure and automation

What experience would help someone be successful in this role at Roku?

8+ years of relevant experience or equivalent

Strong hands-on experience with cloud technologies (AWS preferred; GCP or Azure is a plus), specifically in architecting and managing performant, large-scale systems handling significant traffic and data

Deep knowledge of Kubernetes (EKS, GKE, AKS, or similar) and service mesh technologies

Proficiency in Go or another systems programming language, and Python or another scripting language

Experience designing infrastructure and building automation tools, while collaborating with internal team members and external stakeholders

Experience building CI/CD pipelines and following modern deployment practices

Familiarity with observability tools (Prometheus, Thanos, Loki, Grafana, or similar)

Ability to work independently and communicate effectively with technical and non-technical stakeholders

Passion for learning and solving complex infrastructure challenges

Hands-on experience building agentic systems (agents, MCP servers, custom skills, or agent frameworks), and integrating AI tools to improve processes and reduce operational toil

#LI-DN1

What's Roku's approach to hybrid working?

Roku fosters an inclusive and collaborative environment where teams generally work in the office Monday through Thursday. Fridays are generally flexible for remote work, except for employees whose specific roles or assigned office location require five days' a week attendance.

What are some of the benefits?

Roku is committed to offering a diverse range of benefits as part of our compensation package to support our employees and their families. Our comprehensive benefits include global access to mental health and financial wellness support and resources. Local benefits include statutory and voluntary benefits which may include healthcare (medical, dental, and vision), life, accident, disability, commuter, and retirement options (401(k)/pension). Employees are supported in taking time off, in accordance with local leave policies and other personal needs to support their evolving work and life needs. It's important to note that not every benefit is available in all locations or for every role. For details specific to your location, please consult with your recruiter.

Accommodations

Roku welcomes applicants of all backgrounds and provides reasonable accommodations and adjustments in accordance with applicable law. If you require reasonable accommodation at any point in the hiring process, please direct your inquiries to [email protected].

What should I know about Roku's culture?

Roku is a great place for people who want to work in a fast-paced environment where everyone is focused on the company's success rather than their own. We try to surround ourselves with people who are great at their jobs, who are easy to work with, and who keep their egos in check. We appreciate a sense of humor. We believe a fewer number of very talented folks can do more for less cost than a larger number of less talented teams. We're independent thinkers with big ideas who act boldly, move fast and accomplish extraordinary things through collaboration and trust. In short, at Roku you'll be part of a company that's changing how the world watches TV.

We have a unique culture that we are proud of. We think of ourselves primarily as problem-solvers, which itself is a two-part idea. We come up with the solution, but the solution isn't real until it is built and delivered to the customer. That penchant for action gives us a pragmatic approach to innovation, one that has served us well since 2002.

To learn more about Roku, our global footprint, and how we've grown, visit https://www.weareroku.com/factsheet.

By providing your information, you acknowledge that you want Roku to contact you about job roles, that you have read Roku's Applicant Privacy Notice, and understand that Roku will use your information as described in that notice. If you do not wish to receive any communications from Roku regarding this role or similar roles in the future, you may unsubscribe at any time by emailing [email protected].

Quality

Completeness: 45%
Honesty: 100%

Based on 79 observation(s).

Timeline

  1. *
    #361774 2026-08-25 15:03 UTC
    Published
  2. ~
    #371368 2026-08-25 23:23 UTC
    Modified
    • source_updated_at
      2026-08-25T10:58:45-04:00->2026-08-25T16:04:42-04:00
  3. ~
    #374652 2026-08-26 03:25 UTC
    Modified
    • source_updated_at
      2026-08-25T16:04:42-04:00->2026-08-25T20:04:25-04:00
  4. ~
    #378220 2026-08-26 07:28 UTC
    Modified
    • source_updated_at
      2026-08-25T20:04:25-04:00->2026-08-26T00:04:36-04:00
  5. ~
    #380131 2026-08-26 10:27 UTC
    Modified
    • source_updated_at
      2026-08-26T00:04:36-04:00->2026-08-26T04:04:56-04:00
  6. ~
    #382226 2026-08-26 12:59 UTC
    Modified
    • source_updated_at
      2026-08-26T04:04:56-04:00->2026-08-26T08:04:24-04:00
  7. ~
    #388901 2026-08-26 22:38 UTC
    Modified
    • source_updated_at
      2026-08-26T08:04:24-04:00->2026-08-26T16:04:39-04:00
  8. ~
    #392106 2026-08-27 02:40 UTC
    Modified
    • source_updated_at
      2026-08-26T16:04:39-04:00->2026-08-26T20:04:23-04:00
  9. ~
    #397316 2026-08-27 10:46 UTC
    Modified
    • source_updated_at
      2026-08-26T20:04:23-04:00->2026-08-27T04:04:39-04:00
  10. ~
    #400061 2026-08-27 14:46 UTC
    Modified
    • source_updated_at
      2026-08-27T04:04:39-04:00->2026-08-27T08:04:18-04:00
  11. ~
    #403781 2026-08-27 18:46 UTC
    Modified
    • source_updated_at
      2026-08-27T08:04:18-04:00->2026-08-27T12:06:26-04:00
  12. ~
    #413454 2026-08-28 06:47 UTC
    Modified
    • source_updated_at
      2026-08-27T12:06:26-04:00->2026-08-28T00:04:21-04:00
  13. ~
    #416995 2026-08-28 10:48 UTC
    Modified
    • source_updated_at
      2026-08-28T00:04:21-04:00->2026-08-28T04:04:43-04:00
  14. ~
    #421209 2026-08-28 14:48 UTC
    Modified
    • source_updated_at
      2026-08-28T04:04:43-04:00->2026-08-28T08:04:14-04:00
  15. ~
    #425154 2026-08-28 18:49 UTC
    Modified
    • source_updated_at
      2026-08-28T08:04:14-04:00->2026-08-28T12:04:44-04:00
  16. ~
    #431780 2026-08-29 02:50 UTC
    Modified
    • source_updated_at
      2026-08-28T12:04:44-04:00->2026-08-28T20:04:17-04:00
  17. ~
    #434033 2026-08-29 06:51 UTC
    Modified
    • source_updated_at
      2026-08-28T20:04:17-04:00->2026-08-29T00:04:41-04:00
  18. ~
    #438027 2026-08-29 13:13 UTC
    Modified
    • source_updated_at
      2026-08-29T00:04:41-04:00->2026-08-29T08:03:57-04:00
  19. ~
    #445543 2026-08-29 20:13 UTC
    Modified
    • source_updated_at
      2026-08-29T08:03:57-04:00->2026-08-29T16:04:23-04:00
  20. ~
    #454455 2026-08-30 03:52 UTC
    Modified
    • source_updated_at
      2026-08-29T16:04:23-04:00->2026-08-29T20:04:08-04:00
  21. ~
    #456702 2026-08-30 07:52 UTC
    Modified
    • source_updated_at
      2026-08-29T20:04:08-04:00->2026-08-30T00:03:53-04:00
  22. ~
    #462865 2026-08-30 12:02 UTC
    Modified
    • source_updated_at
      2026-08-30T00:03:53-04:00->2026-08-30T04:04:04-04:00
  23. ~
    #464560 2026-08-30 13:33 UTC
    Modified
    • source_updated_at
      2026-08-30T04:04:04-04:00->2026-08-30T08:04:00-04:00
  24. ~
    #467170 2026-08-30 17:42 UTC
    Modified
    • source_updated_at
      2026-08-30T08:04:00-04:00->2026-08-30T12:04:24-04:00
  25. ~
    #469477 2026-08-30 21:43 UTC
    Modified
    • source_updated_at
      2026-08-30T12:04:24-04:00->2026-08-30T16:03:51-04:00
  26. ~
    #472134 2026-08-31 01:43 UTC
    Modified
    • source_updated_at
      2026-08-30T16:03:51-04:00->2026-08-30T20:03:58-04:00
  27. ~
    #473925 2026-08-31 05:44 UTC
    Modified
    • source_updated_at
      2026-08-30T20:03:58-04:00->2026-08-31T00:03:59-04:00
  28. ~
    #481630 2026-08-31 13:25 UTC
    Modified
    • source_updated_at
      2026-08-31T00:03:59-04:00->2026-08-31T08:04:09-04:00
  29. ~
    #485353 2026-08-31 17:31 UTC
    Modified
    • source_updated_at
      2026-08-31T08:04:09-04:00->2026-08-31T12:06:34-04:00
  30. ~
    #500520 2026-09-01 13:35 UTC
    Modified
    • source_updated_at
      2026-08-31T12:06:34-04:00->2026-09-01T08:04:09-04:00
  31. ~
    #505562 2026-09-01 17:35 UTC
    Modified
    • source_updated_at
      2026-09-01T08:04:09-04:00->2026-09-01T12:05:55-04:00
  32. ~
    #509659 2026-09-01 21:36 UTC
    Modified
    • source_updated_at
      2026-09-01T12:05:55-04:00->2026-09-01T16:04:24-04:00
  33. ~
    #514156 2026-09-02 01:36 UTC
    Modified
    • source_updated_at
      2026-09-01T16:04:24-04:00->2026-09-01T20:04:23-04:00
  34. ~
    #519721 2026-09-02 05:36 UTC
    Modified
    • source_updated_at
      2026-09-01T20:04:23-04:00->2026-09-02T00:04:19-04:00
  35. ~
    #528358 2026-09-02 13:38 UTC
    Modified
    • source_updated_at
      2026-09-02T00:04:19-04:00->2026-09-02T08:04:02-04:00
  36. ~
    #536222 2026-09-02 21:40 UTC
    Modified
    • source_updated_at
      2026-09-02T08:04:02-04:00->2026-09-02T16:04:24-04:00
  37. ~
    #541372 2026-09-03 01:41 UTC
    Modified
    • source_updated_at
      2026-09-02T16:04:24-04:00->2026-09-02T20:04:00-04:00
  38. ~
    #543660 2026-09-03 05:41 UTC
    Modified
    • source_updated_at
      2026-09-02T20:04:00-04:00->2026-09-03T00:04:08-04:00
  39. ~
    #547426 2026-09-03 09:42 UTC
    Modified
    • source_updated_at
      2026-09-03T00:04:08-04:00->2026-09-03T04:04:16-04:00
  40. ~
    #550034 2026-09-03 13:43 UTC
    Modified
    • source_updated_at
      2026-09-03T04:04:16-04:00->2026-09-03T08:04:03-04:00
  41. ~
    #553829 2026-09-03 17:44 UTC
    Modified
    • source_updated_at
      2026-09-03T08:04:03-04:00->2026-09-03T12:05:29-04:00
  42. ~
    #558617 2026-09-03 21:46 UTC
    Modified
    • source_updated_at
      2026-09-03T12:05:29-04:00->2026-09-03T16:04:40-04:00
  43. ~
    #561993 2026-09-04 01:46 UTC
    Modified
    • source_updated_at
      2026-09-03T16:04:40-04:00->2026-09-03T20:04:03-04:00
  44. ~
    #564732 2026-09-04 05:46 UTC
    Modified
    • source_updated_at
      2026-09-03T20:04:03-04:00->2026-09-04T00:04:21-04:00
  45. ~
    #568354 2026-09-04 09:47 UTC
    Modified
    • source_updated_at
      2026-09-04T00:04:21-04:00->2026-09-04T04:05:07-04:00
  46. ~
    #571009 2026-09-04 13:48 UTC
    Modified
    • Description
      Teamwork makes the stream work. Roku is changing how the world watches TV Roku is the #1 TV streaming platform in the U.S., Canada, and...->Teamwork makes the stream work. Roku is changing how the world watches TV Roku is the #1 TV streaming platform in the U.S., Canada, and...
    • source_updated_at
      2026-09-04T04:05:07-04:00->2026-09-04T08:04:03-04:00
  47. ~
    #575530 2026-09-04 17:49 UTC
    Modified
    • source_updated_at
      2026-09-04T08:04:03-04:00->2026-09-04T12:06:12-04:00
  48. ~
    #580022 2026-09-04 21:50 UTC
    Modified
    • source_updated_at
      2026-09-04T12:06:12-04:00->2026-09-04T16:04:05-04:00
  49. ~
    #584962 2026-09-05 05:52 UTC
    Modified
    • source_updated_at
      2026-09-04T16:04:05-04:00->2026-09-05T00:03:49-04:00
  50. ~
    #587353 2026-09-05 09:53 UTC
    Modified
    • source_updated_at
      2026-09-05T00:03:49-04:00->2026-09-05T04:05:23-04:00
  51. ~
    #589582 2026-09-05 13:57 UTC
    Modified
    • source_updated_at
      2026-09-05T04:05:23-04:00->2026-09-05T08:04:04-04:00
  52. ~
    #591122 2026-09-05 17:57 UTC
    Modified
    • source_updated_at
      2026-09-05T08:04:04-04:00->2026-09-05T12:05:33-04:00
  53. ~
    #594847 2026-09-05 23:47 UTC
    Modified
    • source_updated_at
      2026-09-05T12:05:33-04:00->2026-09-05T16:04:03-04:00
  54. ~
    #596831 2026-09-06 03:48 UTC
    Modified
    • source_updated_at
      2026-09-05T16:04:03-04:00->2026-09-05T20:04:03-04:00
  55. ~
    #599389 2026-09-06 07:48 UTC
    Modified
    • source_updated_at
      2026-09-05T20:04:03-04:00->2026-09-06T00:03:49-04:00
  56. ~
    #602295 2026-09-06 11:49 UTC
    Modified
    • source_updated_at
      2026-09-06T00:03:49-04:00->2026-09-06T04:04:35-04:00
  57. ~
    #604655 2026-09-06 15:49 UTC
    Modified
    • source_updated_at
      2026-09-06T04:04:35-04:00->2026-09-06T08:03:54-04:00
  58. ~
    #609012 2026-09-06 23:49 UTC
    Modified
    • source_updated_at
      2026-09-06T08:03:54-04:00->2026-09-06T16:03:49-04:00
  59. ~
    #613275 2026-09-07 07:50 UTC
    Modified
    • source_updated_at
      2026-09-06T16:03:49-04:00->2026-09-07T00:03:55-04:00
  60. ~
    #619577 2026-09-07 15:53 UTC
    Modified
    • source_updated_at
      2026-09-07T00:03:55-04:00->2026-09-07T08:04:05-04:00
  61. ~
    #623234 2026-09-07 19:53 UTC
    Modified
    • source_updated_at
      2026-09-07T08:04:05-04:00->2026-09-07T12:05:24-04:00
  62. ~
    #626147 2026-09-07 23:53 UTC
    Modified
    • source_updated_at
      2026-09-07T12:05:24-04:00->2026-09-07T16:03:46-04:00
  63. ~
    #628505 2026-09-08 03:53 UTC
    Modified
    • source_updated_at
      2026-09-07T16:03:46-04:00->2026-09-07T20:03:47-04:00
  64. ~
    #635213 2026-09-08 11:56 UTC
    Modified
    • source_updated_at
      2026-09-07T20:03:47-04:00->2026-09-08T04:04:28-04:00
  65. ~
    #638463 2026-09-08 15:56 UTC
    Modified
    • source_updated_at
      2026-09-08T04:04:28-04:00->2026-09-08T08:04:15-04:00
  66. ~
    #642652 2026-09-08 19:58 UTC
    Modified
    • source_updated_at
      2026-09-08T08:04:15-04:00->2026-09-08T12:05:53-04:00
  67. ~
    #646720 2026-09-08 23:59 UTC
    Modified
    • source_updated_at
      2026-09-08T12:05:53-04:00->2026-09-08T16:04:04-04:00
  68. ~
    #651720 2026-09-09 08:00 UTC
    Modified
    • source_updated_at
      2026-09-08T16:04:04-04:00->2026-09-09T00:04:02-04:00
  69. ~
    #655849 2026-09-09 12:01 UTC
    Modified
    • source_updated_at
      2026-09-09T00:04:02-04:00->2026-09-09T04:04:43-04:00
  70. ~
    #659633 2026-09-09 16:02 UTC
    Modified
    • source_updated_at
      2026-09-09T04:04:43-04:00->2026-09-09T08:03:59-04:00
  71. ~
    #663429 2026-09-09 20:02 UTC
    Modified
    • source_updated_at
      2026-09-09T08:03:59-04:00->2026-09-09T12:05:48-04:00
  72. ~
    #670119 2026-09-10 04:06 UTC
    Modified
    • source_updated_at
      2026-09-09T12:05:48-04:00->2026-09-10T00:03:50-04:00
  73. ~
    #674138 2026-09-10 08:13 UTC
    Modified
    • source_updated_at
      2026-09-10T00:03:50-04:00->2026-09-10T04:04:17-04:00
  74. ~
    #677030 2026-09-10 12:14 UTC
    Modified
    • source_updated_at
      2026-09-10T04:04:17-04:00->2026-09-10T08:03:53-04:00
  75. ~
    #681631 2026-09-10 16:15 UTC
    Modified
    • source_updated_at
      2026-09-10T08:03:53-04:00->2026-09-10T12:04:59-04:00
  76. ~
    #686114 2026-09-10 20:16 UTC
    Modified
    • source_updated_at
      2026-09-10T12:04:59-04:00->2026-09-10T16:04:14-04:00
  77. ~
    #692308 2026-09-11 04:18 UTC
    Modified
    • source_updated_at
      2026-09-10T16:04:14-04:00->2026-09-11T00:03:44-04:00
  78. ~
    #699966 2026-09-11 13:21 UTC
    Modified
    • source_updated_at
      2026-09-11T00:03:44-04:00->2026-09-11T08:03:56-04:00
  79. ~
    #703978 2026-09-11 17:29 UTC
    Modified
    • Title
      Senior Software Engineer, Platform Engineering->Senior Software Engineer - Kubernetes & Service Mesh
    • source_updated_at
      2026-09-11T08:03:56-04:00->2026-09-11T12:05:36-04:00