Akhilesh Mishra

Founder, LivingDevOps | AI Platform Engineer | Tech Storyteller
DM/email for collab ( [email protected] )

[Akhilesh Mishra @livingdevops]

After 14 years in production DevOps and training 400+ engineers, I just launched my most advanced bootcamp to date.

28 weeks. 56 live classes. DevOps + MLOps + AIOps.

Built for experienced engineers who want to move into MLOps and AIOps without faking it on their resume.

Check it out 👇
https://t.co/RoVUhLoJMR

Launch offer: up to 30% off if you book by 15th June.

[Akhilesh Mishra @livingdevops]

If you are giving an SRE interview, learn to answer this one question well.

"Walk me through an incident you were part of."

Most candidates prepare for Kubernetes and Terraform questions.

But this is the question that tells the interviewer who you really are.

Here is how to structure your answer.

1. How you found out.
- Was it an alert you built?
- A customer complaint or Pure luck? -
- Be honest. If it was luck, say what you changed so it wouldn't be luck next time.
- This shows how you think about detection.

2. Where you got stuck.
- Don't tell a clean story.
- Name the moment you were wrong. - Say what you assumed, and what evidence changed your mind. - Interviewers trust people who admit wrong turns.

3. What you did after.
- The fix that got things running is only half the answer.
- Talk about the work nobody asked for. - The alert you added.
- The runbook you rewrote.
- The toil you automated.

4. Who else was in the story.
- Reliability is a team sport.
- Mention the handoffs.
- How you communicated with stakeholders.
- Who you pulled in, and why.

Tools can be learned in weeks.

Judgment under pressure takes years. So does the habit of leaving systems better than you found them.

Pick one real incident today.

Write it down using these four points. Practice it out loud.

That one story can carry your interview.

[Akhilesh Mishra @livingdevops]

@Jacobmalherbe21 +1 towards your goal

[Akhilesh Mishra @livingdevops]

@aksh_ray07 Let’s connect

[Akhilesh Mishra @livingdevops]

@PedroGuiti Let’s connect

[Akhilesh Mishra @livingdevops]

@i_mika_el Great point to add

[Akhilesh Mishra @livingdevops]

If you are giving an SRE interview, learn to answer this one question well.

"Walk me through an incident you were part of."

Most candidates prepare for Kubernetes and Terraform questions.

But this is the question that tells the interviewer who you really are.

Here is how to structure your answer.

1. How you found out.
- Was it an alert you built?
- A customer complaint or Pure luck? -
- Be honest. If it was luck, say what you changed so it wouldn't be luck next time.
- This shows how you think about detection.

2. Where you got stuck.
- Don't tell a clean story.
- Name the moment you were wrong. - Say what you assumed, and what evidence changed your mind. - Interviewers trust people who admit wrong turns.

3. What you did after.
- The fix that got things running is only half the answer.
- Talk about the work nobody asked for. - The alert you added.
- The runbook you rewrote.
- The toil you automated.

4. Who else was in the story.
- Reliability is a team sport.
- Mention the handoffs.
- How you communicated with stakeholders.
- Who you pulled in, and why.

Tools can be learned in weeks.

Judgment under pressure takes years. So does the habit of leaving systems better than you found them.

Pick one real incident today.

Write it down using these four points. Practice it out loud.

That one story can carry your interview.

[Akhilesh Mishra @livingdevops]

@_jaydeepkarale My brain be like 🍻🍻

[Akhilesh Mishra @livingdevops]

@_jaydeepkarale 😀😀

[Akhilesh Mishra @livingdevops]

@bkarishma360 Thats the audience for this tweet

[Akhilesh Mishra @livingdevops]

Throw your 8GB RAM laptop in the trash. It’s 2026.

16GB is the bare minimum now.

32GB is what I would get.

[Akhilesh Mishra @livingdevops]

DevOps, SRE, and Platform Engineering will be the same job by 2027.

If you look at job postings, you'll see the thin lines between them are already gone.

Open any three postings with these titles.
You'll see the same list:

→ Kubernetes
→ Terraform
→ CI/CD pipelines
→ Observability
→ On-call and incident response
→ Cloud, multi-cloud
→ Building internal tooling for developers
→ LLM, AI agents
→ Python, Go

Different titles. Same job.
Companies don't care what you call yourself.

They care if you can keep production running and help developers ship faster.

So companies won't hire three people for three titles. They'll hire one engineer who understands the whole system.

SOMEONE WITH:
→ End-to-end understanding. Code to cloud to cost.
→ Reliability thinking. SLOs, failure modes, blast radius.
→ Platform mindset. Build things others can use without you.
→ Decision making. AI gives you options. You pick one and own it.
→ Communication. Explaining trade-offs to leadership.

And AI will be a big part of your workflow
→ AI will generate most of the pipelines, manifests, and IaC.
→ AI will take up the toil work
→ AI will help you troubleshoot faster. But someone still has to own the incident.
→ You will build, run and monitor AI agents like you used to do it for apps
→ AI observability will become a core skill. Models fail differently than servers.

The engineers who own outcomes will win.
And the ones waiting to be told what to do will become obsolete.

[Akhilesh Mishra @livingdevops]

DevOps, SRE, and Platform Engineering will be the same job by 2027.

If you look at job postings, you'll see the thin lines between them are already gone.

Open any three postings with these titles.
You'll see the same list:

→ Kubernetes
→ Terraform
→ CI/CD pipelines
→ Observability
→ On-call and incident response
→ Cloud, multi-cloud
→ Building internal tooling for developers
→ LLM, AI agents
→ Python, Go

Different titles. Same job.
Companies don't care what you call yourself.

They care if you can keep production running and help developers ship faster.

So companies won't hire three people for three titles. They'll hire one engineer who understands the whole system.

SOMEONE WITH:
→ End-to-end understanding. Code to cloud to cost.
→ Reliability thinking. SLOs, failure modes, blast radius.
→ Platform mindset. Build things others can use without you.
→ Decision making. AI gives you options. You pick one and own it.
→ Communication. Explaining trade-offs to leadership.

And AI will be a big part of your workflow
→ AI will generate most of the pipelines, manifests, and IaC.
→ AI will take up the toil work
→ AI will help you troubleshoot faster. But someone still has to own the incident.
→ You will build, run and monitor AI agents like you used to do it for apps
→ AI observability will become a core skill. Models fail differently than servers.

The engineers who own outcomes will win.
And the ones waiting to be told what to do will become obsolete.

[Akhilesh Mishra @livingdevops]

@_jaydeepkarale I wish my manager had read this post 😀😀

[Akhilesh Mishra @livingdevops]

@Love_India07 But recruiters will reach out to seekers.

[Akhilesh Mishra @livingdevops]

Dear job seekers from India.

If you are not getting interview calls from Naukri even after updating your profile, do this.

- Delete your current Naukri account
- Create a new one with different email
- Update a ATS compliant resume that shows relevant skills and experience
- Use metrics in your resume points with right context ( Achieved this by doing that and Star format)

Add some AI relevent experience and you will start getting a lot of calls.

[Akhilesh Mishra @livingdevops]

@Jeet_chetwani17 You can create a new account. I don’t like multiple accounts with same info laying around

[Akhilesh Mishra @livingdevops]

@Devvora15 Got one more

[Akhilesh Mishra @livingdevops]

@anurag_gharat Everyone knows about that one

[Akhilesh Mishra @livingdevops]

If you haven’t worked with AI tools and workflows then please learn, build some good POC, keep an eye on development in AI and try to learn them.

[Akhilesh Mishra @livingdevops]

@e_opore Yes it did work. Naukri is a place with tricks

[Akhilesh Mishra @livingdevops]

@devops_nk This isn’t a trick, it’s what i experienced it 2 days back