BACK

Work with me

Four things I do outside the day job

Coaching one engineer, training a whole team, running the interview loop you are about to face, and building sites for people whose work deserves better than a template.

🎓

One-to-one DevOps coaching

For the engineer who is the platform team

Six years of building this layer for consumer-scale companies, taught the way I'd want to learn it: real clusters, real pipelines, real incidents. Not slides about what Kubernetes is. We break something, then you fix it, and you keep the runbook. Standing weekly slot, your own backlog, and you bring the problem you are actually stuck on.

Who it's for

  • Engineers who can run kubectl but can't debug a CrashLoopBackOff at 2am
  • The one person holding up CI for a whole org, with nobody to ask
  • People switching into DevOps who want a route that isn't a certificate mill
  • Seniors preparing to own a platform, not just operate one

What it covers

  • ·Whatever you are actually stuck on — your cluster, your pipeline, your incident
  • ·Reading a failure properly: what the events, the sidecar log and the probe are each telling you
  • ·Kubernetes in anger — scheduling, probes, resource limits, the failure modes
  • ·Terraform and GitOps habits that hold up when someone else inherits them
  • ·How to argue for platform work in a language your manager will fund
  • ·A gap list between sessions, so the time compounds instead of resetting

Used only to reply to you. Not shared, not added to any list.

🧑‍🏫

Team training, delivered as a cohort

For teams who inherited a platform nobody understands

A scheduled programme for a whole team rather than an individual, run on a cluster we stand up for it. Every module ends with something broken that the team has to diagnose and fix, and the commands that found it go into your runbook. Delivered remote or on-site in Bengaluru, in English, Hindi or Kannada.

Who it's for

  • Teams moving from VMs to Kubernetes and unsure what changes underneath
  • Orgs whose CI works because one person remembers how
  • Platform teams inheriting something the original authors have left
  • Engineering managers who need the whole team at one level, not one hero

What it covers

  • ·Kubernetes in anger — scheduling, probes, resource limits, the failure modes
  • ·CI/CD with security baked in, not bolted on: SAST, artifact provenance, short-lived credentials
  • ·Terraform and GitOps that survive more than one engineer
  • ·Observability that answers questions, and alerting people don't ignore
  • ·Cloud cost work that doesn't quietly trade away availability
  • ·A live incident drill on a real cluster, debriefed the way a real postmortem is

Used only to reply to you. Not shared, not added to any list.

🎤

Mock interview series

Four rounds, recorded, with the feedback nobody gives you

Most DevOps and SRE loops are not knowledge tests — they are debugging under observation, and that is a separate skill. A series of rounds run the way real loops run, each recorded, each followed by written feedback on what your answer signalled rather than just whether it was right. I have been on both sides of these.

Who it's for

  • Engineers targeting DevOps, SRE or platform roles and guessing at the bar
  • Anyone who knows the material and still freezes when someone is watching
  • People moving from support or admin work into engineering interviews
  • Seniors going for a lead role where the rounds change shape entirely

What it covers

  • ·Troubleshooting round — a broken cluster, shared screen, think out loud
  • ·Systems design — multi-region, failure domains, and the trade-offs you are expected to name
  • ·CI/CD and IaC deep dive, including the questions that are really about blast radius
  • ·Behavioural round on incidents: how you talk about an outage you caused
  • ·Written feedback per round, plus the gap list to work on between them
  • ·A resume and profile pass, since the loop starts before the first call

Used only to reply to you. Not shared, not added to any list.

🎬

Websites for content creators

You have an audience. A Linktree is not a home.

A site that looks like you rather than like a template — motion, 3D, the kind of thing people screenshot. Built on the same stack as this portfolio, which is the demo. Fast, works on a phone, and yours to keep.

Who it's for

  • Creators outgrowing link-in-bio pages
  • Photographers and videographers who need work to load fast and look right
  • Anyone whose brand deserves better than a drag-and-drop builder
  • Small studios wanting something bespoke without agency pricing

What it covers

  • ·Custom design — no themes, built around your work
  • ·3D and motion where it earns its place, not everywhere
  • ·Genuinely fast: static rendering, optimised images, real mobile testing
  • ·Analytics you own, in a spreadsheet, not a dashboard you rent
  • ·Contact and booking forms wired to your inbox
  • ·Deployed on your domain, with the handover documented

Used only to reply to you. Not shared, not added to any list.

All four run in evenings and weekends alongside a full-time role, so I take a small number at a time. Mail me directly at ck.shrini@gmail.comif you'd rather skip the form.