Ravindra BagaleCourses & study guides मराठी Track your progress

Guides

DevOps vs SRE vs Platform Engineer: आपके लिए कौन सी भूमिका?

JD में DevOps, SRE और Platform Engineer मिलते हैं। समान cloud, अलग daily focus। यह गाइड duties, tools और interview की तुलना करती है।

Friends, titles change every year. Ask what you will own on call. Chala mitrano — pick the pain you like to fix.

Quick answer

Hold this vertical picture:

  1. DevOps = shipping pipelines।
  2. SRE = reliability और toil।
  3. Platform = कई teams के लिए paved road।
  4. Apply से पहले pager pain मिलाएँ।
  5. उस title की interview style का अभ्यास करें।

Language: English · मराठी · हिंदी

DevOps EngineerShip: CI/CD, build, deploy SREReliability: SLOs, toil, incidents Platform EngineerShared tools for many teams Your fitMatch skills + pager pain
Three roles — different daily focus

पद क्यों भ्रमित करती हैं

Infosys, TCS, Amazon, Google में समान tools तीन नामों से आते हैं।

Why: Title marketing है; रोज़ का काम ownership है। What: तीन भूमिकाएँ, अलग primary pain। How: नीचे duties पढ़ें और story मिलाएँ।

Concept 1: DevOps — change ship करें

Why: Business को weekend panic नहीं चाहिए। What: CI/CD, Docker/K8s, IaC, basic monitoring। How: Commit से environment तक pipeline own करें।

Example 1: Pipeline status

Type this:

printf '%s\n' 'stage=test' 'result=SUCCESS' > /tmp/ci-status.txt
cat /tmp/ci-status.txt

You will see:

stage=test
result=SUCCESS

What it means: Green = tests चले।

Example 2: Release tag

Type this:

cd /tmp && mkdir -p ship-lab && cd ship-lab
printf 'v1\n' > VERSION
git init -q -b main
git add VERSION
git -c user.email=a@b.c -c user.name=Lab commit -q -m "release: 1.0.0"
git tag -a v1.0.0 -m "ship 1.0.0"
git tag -l

You will see:

v1.0.0

What it means: DevOps tags और deploy own करता है।

Example 3: Artifact

Type this:

test -f /tmp/ship-lab/VERSION && echo ARTIFACT_OK

You will see:

ARTIFACT_OK

What it means: Shipping = known build।

Concept 2: SRE — वादा निभाएँ

Why: Flipkart sale या Netflix-scale पर users errors देखती हैं। What: SLI/SLO, error budget, toil, incidents। How: एक SLO तय करें, मापें, budget जलने पर page करें।

Example 4: Availability

Type this:

python3 -c "ok=995; total=1000; print(round(100*ok/total,2))"

You will see:

99.5

What it means: SLO 99.9 हो तो 99.5 budget जलाता है।

Example 5: Budget left

Type this:

python3 -c "slo=99.9; actual=99.5; budget=100-slo; used=slo-actual; print('budget_pct_left', round(100*(budget-used)/budget,1))"

You will see:

budget_pct_left 60.0

What it means: SRE budget left में बात करता है।

Example 6: Toil

Type this:

printf '%s\n' 'restart nginx' 'restart nginx' 'restart nginx' | sort | uniq -c

You will see:

3 restart nginx

What it means: तीन समान tickets = toil।

Concept 3: Platform — shared path

Why: बीस teams बीस Jenkinsfiles न बनाएँ। What: Templates, golden paths, self-service। How: एक paved road: repo + pipeline + envs।

Example 7: Tenants

Type this:

printf '%s\n' team-a team-b team-c > /tmp/platform-tenants.txt
wc -l < /tmp/platform-tenants.txt

You will see:

3

What it means: सफलता = कई teams एक path पर।

Example 8: Golden path

Type this:

printf '%s\n' 'repo-template=yes' 'ci-template=yes' 'dev-env=yes' 'prod-gate=yes' > /tmp/golden.txt
cat /tmp/golden.txt

You will see:

repo-template=yes
ci-template=yes
dev-env=yes
prod-gate=yes

What it means: Defaults चाहिए, wiki dump नहीं।

Example 9: Tickets saved

Type this:

python3 -c "manual=12; after=3; print('tickets_saved', manual-after)"

You will see:

tickets_saved 9

What it means: Platform = कम tickets।

Concept 4: Fit चुनें

Why: गलत title छह महीने बर्बाद। What: Skills + pager pain + interview focus। How: तीन bullets लिखें; सबसे मज़बूत रखें।

Example 10: Skill map

Type this:

printf '%s\n' 'linux=strong' 'ci=medium' 'slo=weak' 'k8s=medium' > /tmp/skill-map.txt
grep strong /tmp/skill-map.txt

You will see:

linux=strong

What it means: ताकत से शुरू करें।

Example 11: Focus

Type this:

printf '%s\n' 'DevOps: pipeline debug' 'SRE: incident + SLO' 'Platform: template design'

You will see:

DevOps: pipeline debug
SRE: incident + SLO
Platform: template design

What it means: JD के title के हिसाब से अभ्यास।

Example 12: Pitch

Type this:

printf '%s\n' 'I own CI from commit to ECS and cut failed deploys by half in a lab.'

You will see:

I own CI from commit to ECS and cut failed deploys by half in a lab.

What it means: Ownership > buzzwords।

सारांश

Role Pain Interview
DevOps धीमी releases Pipeline debug
SRE Outages Incident
Platform Reinvent Golden path

Infosys account

Title DevOps हो तो भी काम Jenkins+Linux हो सकता है। On-call पूछें।

Ravindra Bagale's Tip

In the interview at Google-style SRE or Amazon DevOps, say which pager pain you enjoy. Reliability, shipping, or shared platforms — pick one story.

Check yourself (quiz)

Q1. DevOps मुख्यतः क्या own करता है?

Shipping: CI/CD और deploys।

Q2. SRE कौन सा आँकड़ा देखता है?

SLO और error budget left।

Q3. Golden path क्या है?

Repo, CI, env के लिए shared template।

Q4. Infosys-style पर on-call क्यों पूछें?

Title DevOps होने पर भी रात के restarts हो सकते हैं।

Q5. Fit कैसे चुनें?

Skills + pager pain + lab story।

Reading tracking

Mark this guide when you finish. Your browser remembers it on this device.

Title = ownership। DevOps ship करता है। SRE वादा रखता है। Platform सड़क बनाता है। Did you understand? Let us try it once more.

Frequently asked questions

DevOps vs SRE vs Platform — short answer?

DevOps owns shipping pipelines; SRE owns SLOs and toil; Platform owns shared golden paths for many teams.

Do they use different clouds?

Often the same tools; the daily ownership differs.

What should Infosys-style candidates ask?

What on-call looks like — the title may say DevOps while the pain is night restarts.

What is a golden path?

A default template for repo, CI and environments that many teams share.

How do I pick a fit?

Match skills plus the pager pain you can prove with a lab story.

Where to read interview questions?

Chapter 70 and the DevOps Interview Hub.