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

Guides

DevOps vs SRE vs Platform Engineer: तुमच्यासाठी कोणती भूमिका?

JD मध्ये DevOps, SRE आणि Platform Engineer मिसळतात. समान cloud, वेगळा daily focus. हा guide 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 stand-in

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 stage = 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 release tags आणि deploy jobs 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 — promise ठेवा

Why: Flipkart sale किंवा Netflix-scale वर users errors/latency पाहतात. 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: Strength पासून सुरू.

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 Primary pain Interview
DevOps धीमी/risky releases Pipeline debug
SRE Outages + toil Incident timeline
Platform Teams 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 promise राखतो. Platform road तयार करतो. 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.