Ravindra BagaleCourses & study guides मराठी

Chapter 70: DevOps Interview Questions by Topic and Company

70.13 DevOps Interview Questions by Company: TCS, Infosys, Wipro, Amazon and More

Konti company kay vicharte he ithe ekatra ahe. Pan lakshat theva - prashna sagalikade sarkhech astat.

What you will learn in this lesson

  • Which questions were asked at 17 companies
  • Where to find each full answer
  • How to prepare for a company in one week

Why: the problem

Before an interview at TCS or Amazon, you want to know what they ask. Public interview stories on LinkedIn, Glassdoor, AmbitionBox and GeeksforGeeks help with that.

What: how this list was made

We read public interview stories from candidates. A company is named only when a story says the question was asked there. We wrote every answer ourselves, in simple English.

How: prepare for one company in 4 steps

1. Read its question list below 2. Open each answer in the topic lesson 3. Practise aloud with a timer 4. Do one lab for each weak topic
Prepare for one company
  1. Read the company list below.
  2. Click each question to open its answer.
  3. Practise aloud, 60 seconds each.
  4. Do a small lab for the topics you find hard.

Questions by company

Wipro (48 questions)

LTIMindtree (45 questions)

TCS (42 questions)

Deloitte (38 questions)

Tech Mahindra (37 questions)

Infosys (35 questions)

Capgemini (29 questions)

Amazon (28 questions)

Accenture (23 questions)

Walmart Global Tech (20 questions)

HCLTech (19 questions)

Google (12 questions)

IBM (9 questions)

Flipkart (8 questions)

Barclays (5 questions)

Oracle (3 questions)

Goldman Sachs (3 questions)

Companies with few public questions

For Microsoft, JPMorgan, Cognizant, Paytm, Zomato and Swiggy we found no clear public DevOps question lists we could trust. Oracle, Goldman Sachs and Barclays have only a few. Prepare the topic lessons; they cover what these companies usually ask.

Practice tasks

Easy Write a Jenkins pipeline to build and push a Docker image.

Why: Saying it once with your own words makes it stick.

What to do: Answer this question as if the interviewer just asked it.

How:
  1. Open a lab VM or container, never production.
  2. Run or write the example from the answer.
  3. Read the output line by line.
  4. Say the answer aloud in under 60 seconds.

Check: Your answer has a reason, a plain meaning and one command.

Easy What is EBS?

Why: Saying it once with your own words makes it stick.

What to do: Answer this question as if the interviewer just asked it.

How:
  1. Open a lab VM or container, never production.
  2. Run or write the example from the answer.
  3. Read the output line by line.
  4. Say the answer aloud in under 60 seconds.

Check: Your answer has a reason, a plain meaning and one command.

Easy Which AWS services have you used?

Why: Saying it once with your own words makes it stick.

What to do: Answer this question as if the interviewer just asked it.

How:
  1. Write three short points: why, what, how.
  2. Add one example from your own project.
  3. Say it aloud in under 60 seconds.

Check: Your answer has a reason, a plain meaning and one example.

Easy What is AWS Lambda?

Why: Saying it once with your own words makes it stick.

What to do: Answer this question as if the interviewer just asked it.

How:
  1. Write three short points: why, what, how.
  2. Add one example from your own project.
  3. Say it aloud in under 60 seconds.

Check: Your answer has a reason, a plain meaning and one example.

Easy What is the difference between EBS, S3 and EFS?

Why: Saying it once with your own words makes it stick.

What to do: Answer this question as if the interviewer just asked it.

How:
  1. Write three short points: why, what, how.
  2. Add one example from your own project.
  3. Say it aloud in under 60 seconds.

Check: Your answer has a reason, a plain meaning and one example.

Easy What is an S3 lifecycle policy?

Why: Saying it once with your own words makes it stick.

What to do: Answer this question as if the interviewer just asked it.

How:
  1. Open a lab VM or container, never production.
  2. Run or write the example from the answer.
  3. Read the output line by line.
  4. Say the answer aloud in under 60 seconds.

Check: Your answer has a reason, a plain meaning and one command.

Medium How do you secure an S3 bucket?

Why: Saying it once with your own words makes it stick.

What to do: Answer this question as if the interviewer just asked it.

How:
  1. Open a lab VM or container, never production.
  2. Run or write the example from the answer.
  3. Read the output line by line.
  4. Say the answer aloud in under 60 seconds.

Check: Your answer has a reason, a plain meaning and one command.

Medium Tell me about a time you had a conflict with a teammate.

Why: Saying it once with your own words makes it stick.

What to do: Answer this question as if the interviewer just asked it.

How:
  1. Write three short points: why, what, how.
  2. Add one example from your own project.
  3. Say it aloud in under 60 seconds.

Check: Your answer has a reason, a plain meaning and one example.

Homework: try at home

  1. Pick your target company.
  2. Answer all its questions aloud in one sitting.
  3. Mark the ones you could not answer and study those lessons.

Recap

In short

  • Companies ask mostly the same core topics.
  • Tags come only from public interview stories.
  • Each question links to its full answer.

FAQ

Should I memorise these answers?

No. Understand the why, then say it in your own words. Interviewers notice memorised lines.

What if I do not know an answer?

Say so honestly. Then explain how you would find out, step by step.

Are these questions only for one company?

No. "Asked at" shows where people said it was asked. Other companies ask the same things.

How long should an answer be?

About 30 to 60 seconds. Give a reason, a plain meaning and one example.

Is a lab really needed?

Yes. Running the command once makes your answer real and confident.

Interview questions

These were asked at three or more companies:

Quick quiz

Q1. When is a question tagged with a company?

Only when a public interview story says it was asked there.

Q2. Do different companies ask different DevOps basics?

Mostly no. The core topics are the same everywhere.

Q3. How long should a spoken answer be?

About 30 to 60 seconds.

Q4. What should every answer include?

Why, what, how, and one example.

Q5. What do you do if you do not know an answer?

Say so honestly and explain how you would find out.

Samajla ka?

Ravi Sir's Cards for this lesson

मराठी cards