Platform Engineer
Build and operate the internal developer platform — the CI/CD pipelines, Kubernetes clusters, service mesh, secrets management, observability stack, and IaC modules — that every other engineer in the company ships on. Platform engineers turn raw cloud (AWS/GCP/Azure) into a paved road: a developer pushes code, the platform takes it from commit to canary to production with logs, metrics, and rollback baked in. In India, the role is concentrated at product unicorns (Razorpay, Zerodha, CRED, PhonePe, Swiggy), GCCs of global firms (Microsoft, Atlassian, Stripe, Walmart Global Tech), and SaaS companies scaling past 200 engineers — typically the point at which a dedicated platform team starts paying for itself in shipping velocity.
Overview
Build and operate the internal developer platform — the CI/CD pipelines, Kubernetes clusters, service mesh, secrets management, observability stack, and IaC modules — that every other engineer in the company ships on. Platform engineers turn raw cloud (AWS/GCP/Azure) into a paved road: a developer pushes code, the platform takes it from commit to canary to production with logs, metrics, and rollback baked in. In India, the role is concentrated at product unicorns (Razorpay, Zerodha, CRED, PhonePe, Swiggy), GCCs of global firms (Microsoft, Atlassian, Stripe, Walmart Global Tech), and SaaS companies scaling past 200 engineers — typically the point at which a dedicated platform team starts paying for itself in shipping velocity.
A Day in the Life
Open laptop in Bengaluru / Hyderabad office or home; pull main, scan #platform-help Slack channel for overnight asks from product teams.
Check Grafana / Datadog dashboards for platform health — node disk pressure, CI runner queues, cluster autoscaler activity, cost anomalies.
Filter coffee or chai; reply to overnight Slack DMs from product engineers blocked on a Helm values issue or a Terraform plan.
15-minute standup over Zoom with the platform pod — yesterday's progress, today's plan, blockers, on-call status.
Deep-work block 1: 2 hours writing Go for the internal developer portal — a new self-service form that lets product teams provision a Service Bus namespace without filing a ticket.
Lunch — office cafe thali or home dabba; informal chat with the SRE lead about whether to migrate logs from ELK to Grafana Loki.
Review 2-4 Terraform PRs from product teams — push back on a missing tag, an over-permissioned IAM role, and a cost-untracked GPU instance.
30-minute platform office-hours session over Slack — answer K8s, Helm, and CI questions from engineers across the org.
Investigate a flaky CI pipeline reported in #platform-help; repro locally, find a transient image-pull issue, fix the root cause, document it in the runbook.
Deep-work block 2: continue the internal portal feature, write Playwright tests for the form, push the PR; request review from a senior.
Sit with a product team for 30-45 minutes to debug their staging deploy — usually a Helm values mistake, a missing IAM role, or a misconfigured ingress.
Monitor cost dashboards (Cost Explorer, CloudHealth); flag a runaway Lambda from yesterday's experiment; file a ticket with the owning team.
Final commits, EOD Slack update; if on-call this week, set up phone with PagerDuty; pages possible at 2 AM IST if the cluster has issues.
Common Mistakes
7- ⚠️Trying to jump directly into platform engineering as a fresherWhy: Indian platform hiring managers expect 2-3 years of SDE or DevOps experience first because good platform engineers need empathy for what app developers need; pure platform freshers build platforms developers hate using.Instead: Start as SDE or DevOps at a product company for 2-3 years; build Kubernetes, Terraform, observability, and one cloud (usually AWS) deeply; then specialize into platform.
- ⚠️Skipping CKA / CKAD / CKS certificationsWhy: Kubernetes certs are unusually load-bearing in platform hiring because they short-circuit screening at Indian product cos and GCCs; engineers without them lose interview slots to peers with the cert.Instead: Earn CKA before your first platform switch; CKS within 18 months of becoming senior; budget 6-8 weeks evening prep per cert and treat it as required.
- ⚠️Focusing only on tools, ignoring developer experience (DevEx)Why: Platforms that are technically correct but painful to use have low adoption; engineers who optimize only for K8s elegance get overlooked at promotion because their platform doesn't move shipping velocity for the org.Instead: Treat product engineers as your customers; measure DevEx (deploy time, P50 ticket resolution, # self-service flows); ship one DevEx win per quarter alongside infra work.
- ⚠️Building everything yourself instead of buying / using OSSWhy: Building a custom CI / observability / IDP stack burns 12-18 months of platform-team time that could have gone to high-leverage work; the build-it-all approach also lacks the docs and community support of OSS alternatives.Instead: Default to managed (GitHub Actions, Datadog, Backstage) or OSS (Argo, Prometheus, Crossplane); build only when no OSS fits; defend build-vs-buy decisions with explicit cost models.
- ⚠️Treating on-call and incident response as someone else's jobWhy: Platform engineers who duck on-call cap out at platform-2 because they cannot demonstrate the senior-track skills (incident leadership, postmortem ownership, reliability culture).Instead: Volunteer for on-call from month 6 at a new role; pair-page with a senior; lead at least 5-10 incidents end-to-end by year 2; treat blameless postmortems as your senior portfolio.
- ⚠️Staying at a low-traffic / small-scale company past 3 yearsWhy: Platform skills compound only at companies with real scale problems — 200+ engineers, 1000+ services, multi-region. A small-scale platform role plateaus comp and skill growth within 2-3 years.Instead: By year 3-4, target a high-scale product company (Razorpay, Flipkart, Swiggy, Atlan, Postman) or a global remote role at HashiCorp, Datadog, GitLab; the platform-at-scale war stories are what get you to senior.
- ⚠️Not building a public profile (blog, GitHub, talks)Why: Senior platform hiring is unusually portfolio-driven — open-source contributions to Argo / Backstage / Crossplane / Terraform, blog posts on platform design, conference talks at KubeCon / Rootconf move offers from screening to 'we want them'.Instead: Publish one technical blog post per quarter; submit a talk to Rootconf or KubeCon India once a year; contribute one PR to a CNCF project.
Salary by Indian City (Mid-level total cash comp)
6| City | Range |
|---|---|
| Bangalore | INR 22-35L base + ESOPs |
| Hyderabad | INR 20-32L base + ESOPs |
| Pune | INR 18-28L base + ESOPs |
| NCR (Gurgaon / Noida) | INR 18-28L base + ESOPs |
| Mumbai | INR 18-28L base + ESOPs |
| Remote-international | USD 75-150K (INR 62-125L) all-in |
Notable Indians in this career
6Communities + forums
7- Global Platform Engineering community Slack with an active India channel; topics include Backstage, internal developer platforms, golden paths, build-vs-buy debates.
- KubeCon + CloudNativeCon IndiaConference + YouTubeCNCF's India-region KubeCon; sessions on Kubernetes, observability, service meshes, IDPs; the canonical platform / SRE conference for Asian engineers.
- Rootconf IndiaConference + YouTubeIndia's flagship DevOps / platform / SRE conference; annual event in Bengaluru with talks from Razorpay, Flipkart, Swiggy, Cloudflare engineering leaders. Recordings free on YouTube.
- DevOps Bangalore MeetupMeetupLong-running Bengaluru DevOps / platform meetup; in-person and hybrid sessions; speakers from Razorpay, Flipkart, Cloudflare, Atlassian.
- CNCF SlackSlackOfficial Cloud Native Computing Foundation Slack; channels for Kubernetes, Prometheus, OpenTelemetry, Argo, Istio, Crossplane; Indian platform engineers working with these tools are active here.
- Kubernetes IndiaSlack + MeetupIndia-focused Kubernetes community; regional chapters in Bengaluru, Hyderabad, Pune, Mumbai; topical talks on K8s operators, multi-cluster, GitOps.
- r/devopsRedditGlobal DevOps / platform subreddit; daily threads on Kubernetes, Terraform, IDPs, hiring; Indian seniors active.
What to read / watch / follow
10- Team TopologiesBookby Matthew Skelton, Manuel PaisThe canonical reference on how to structure platform teams as 'enabling' teams serving 'stream-aligned' product teams; required reading for Indian senior platform engineers.
- Site Reliability Engineering (the SRE book)Book (free online)by Beyer, Jones, Petoff, Murphy (Google)Defines SLOs, error budgets, on-call practices that platform engineers also own; free from Google; cited in Indian senior platform interviews.
- Kubernetes Up and RunningBookby Hightower, Burns, BedaThe default Kubernetes reference for Indian platform engineers prepping CKA and senior platform interviews; covers fundamentals and operator patterns.
- Terraform Up and RunningBookby Yevgeniy BrikmanThe canonical Terraform book; covers modules, workspaces, state management, and production patterns; required for any senior platform interview.
- Internal Developer Platform community blogBlogby internaldeveloperplatform.orgThe reference site for IDP design; covers Backstage, golden paths, platform-as-product thinking; widely shared in Indian platform Slack channels.
- Platform Weekly newsletterNewsletterby Various editorsWeekly curated platform-engineering links; IDP design, GitOps, observability, cost engineering; Indian senior platform engineers subscribe.
- Charity Majors' blog (charity.wtf)Blogby Charity MajorsSharp opinionated writing on observability, on-call, and engineering culture; influential in Indian platform thinking on team design.
- HashiCorp blog + Cloudflare blogBlogby HashiCorp, Cloudflare engineeringHigh-signal content on Terraform, Vault, Consul, edge computing, and platform design; required reading for Indian senior platform engineers.
- KubeCon talks (CNCF YouTube)YouTubeby CNCF KubeCon speakersAnnual KubeCon talks from Google, Razorpay, Spotify, Adobe platform teams; canonical content for senior platform interview preparation.
- Rootconf India recordingsYouTubeby Rootconf IndiaIndian-context platform / DevOps talks from Razorpay, Flipkart, Swiggy, Hotstar engineers; closest equivalent to KubeCon for India-scale problems.
Daily Responsibilities
7- Review and merge 2-4 Terraform pull requests from product teams asking for new infrastructure (databases, queues, IAM roles) — push back on cost or security misuse before approving.
- Investigate a flaky CI pipeline reported in #platform-help: reproduce locally, check runner logs, fix the root cause (often a transient image-pull issue or a timeout) and document it.
- Push a small change to the internal developer portal — a new self-service form, a doc update, or a deprecation banner — that removes a ticketed ask from the team's queue.
- Sit with a product team for 30-45 minutes to debug their staging deploy: usually a Helm-values mistake, a missing IAM role, or a misconfigured ingress.
- Work on the current quarter's platform initiative — for example, migrating logs from ELK to Grafana Loki, or rolling out OpenTelemetry tracing across services.
- Run a brief platform office-hours session (Slack thread or Zoom drop-in) where any engineer can ask K8s, Terraform, or CI questions; this is the team's primary support channel.
Advantages
- High leverage — one good Terraform module or one fixed CI pipeline saves dozens of engineers hours per week, and that compounding impact gets noticed at promotion time.
- Strong, durable demand in India — every product company past Series B builds a platform team, and the supply of senior platform engineers is tight enough that switches command 40-60% jumps.
- Skills travel well: Kubernetes, Terraform, observability, and SRE practices are near-identical across fintech, SaaS, and B2B — you can move from Razorpay to a SaaS to a global GCC without retraining.
- Mostly-remote friendly — platform work is async-heavy and tooling-driven, so most Indian product companies and many GCCs hire pan-India remote at SDE-2 level and above.
- Career optionality — strong platform engineers move into SRE, infra-focused staff IC tracks, engineering management, or DevTools founder roles (the founders of Harness, Spacelift, and Tailscale all came from this lineage).
Challenges
- Invisible-when-it-works problem — when the platform hums, nobody notices; when it breaks, the entire engineering org is blocked and you own the postmortem.
- On-call is heavier than for product engineers — the platform underlies every service, so a flaky cluster or a bad Terraform apply can wake you at 3 AM with hundreds of impacted engineers.
- The surface area never stops growing — you need working knowledge of K8s, Terraform, at least one cloud's IAM model, networking, observability, secrets, supply-chain security, and shell scripting; the learning curve is steep and never quite settles.
- Low product visibility — you ship internal tools to engineers, not features to customers, so the dopamine loop of seeing a real user use your work is much weaker than for app developers.
- Vendor / tooling churn — the CNCF landscape adds and deprecates tools every quarter, and the team that picked the wrong bet (e.g. Flux v1 in 2020) carries that migration debt for years.
Education
6- Required (most common): B.Tech / B.E. in Computer Science, IT, or Electronics — most platform engineers in India enter via SDE or DevOps roles first, then specialize after 3-5 years.
- Strong alternatives: BCA, MCA, or B.Sc. (Computer Science) — fully accepted at product companies and GCCs once the candidate has 2+ years of hands-on infra work.
- Premium signal: degree from IIT, NIT, IIIT, BITS, or a top global CS program — useful for the first job, much less load-bearing once you have production K8s and IaC scars.
- Self-taught + portfolio: a public GitHub with Terraform modules, a homelab K8s cluster, contributions to CNCF projects (Argo, Flux, Crossplane) carries real weight — Indian startups will hire on this signal alone past 3 years experience.
- Bootcamps: KodeKloud, Linux Academy / A Cloud Guru, and CNCF kubestronaut tracks — pair these with a real production migration or homelab project; certificates alone won't land the role.