Site Reliability Engineer Intern

The role

Most engineering internships are about building something new. This one is about keeping something running.
 

Ryt Bank serves real customers with real money, which means our platform doesn't get to have a bad day quietly. Our SRE team is small, which means an intern here isn't fetching coffee for a twelve-person org — you'll be given a scoped piece of the platform, a mentor, and enough context to make decisions about it.

You'll learn how a bank's infrastructure actually holds together: why a deployment goes through the gates it does, what an alert should and shouldn't wake someone up for, and how much of reliability engineering is really about removing work rather than adding it.
 

What you'll actually do

• Take ownership of one meaningful project end to end — scoped so you can ship it, not so you can survive it

• Build and refine dashboards and alerts, and learn the difference between a signal and a distraction

• Write Terraform that goes into our real estate, reviewed like anyone else's

• Automate something tedious that a human is currently doing by hand

• Sit in on incident reviews and see how failures get diagnosed and prevented, not just fixed

• Leave behind documentation good enough that the next person doesn't need to ask you

What we're looking for

You're partway through a Computer Science, Computer Engineering, Software Engineering or related degree. Beyond that, we care more about instincts than credentials:

• You're comfortable in a terminal and can write a script that does something useful

• You've bumped into Linux, containers, networking, or a cloud console somewhere — coursework, side projects, or curiosity all count

• When something breaks, your first move is to find out why, not to restart it and hope

• You ask questions when you're stuck, and you finish what you pick up

We don't expect production experience. We expect you to want it.
 

What you'll get out of it

Infrastructure work at a licensed bank is a genuinely different discipline from infrastructure work anywhere else — every change is auditable, every control has a regulator behind it, and "it works on my machine" was never an option. It's a rare thing to see early in a career, and it makes everything afterwards easier.

You'll also get a mentor who's accountable for your growth, not just your tickets.
 

What you'll work with

• Public cloud at production scale

• Container orchestration

• Infrastructure-as-code

• GitOps-based delivery

• Metrics, logging and alerting

• Automation in a general-purpose scripting language

We'll go into specifics at interview.
 

How we work

Small team, high trust, low ceremony. We'd rather explain a decision than defend it, and we'd rather fix the cause than the symptom. If that sounds like your kind of environment, we'd like to meet you.