Skip to main content

PWC Interview experience for Junior DevOps Engineer

 PWC Interview experience for Junior DevOps Engineer role


✅ Round 1: Screening Round (30 minutes)

- Walk me through your current project architecture and your role in it.

- Which DevOps tools have you worked with in the last 2 years?

- What AWS services have you used in production?

- How do you expose a Kubernetes application to external traffic?

- What is the purpose of a NAT Gateway?

- How do you check running processes in Linux?

- What command would you use to find files larger than 100MB?

- What is the difference between Deployment and StatefulSet in Kubernetes?

- What is a ConfigMap, and how is it different from a Secret?

- How do you check network connectivity between two servers?

- Describe your experience with CI/CD pipelines.


✅ Round 2: Technical Round (60 minutes)

- You have an application in Account A that needs to access an S3 bucket in Account B. How would you configure this?

- Write a Dockerfile for a Node.js application with multi-stage builds.

- How do you handle Terraform state file corruption?

- Your EC2 instance in a private subnet needs to download packages without NAT Gateway. What alternatives exist?

- How do you debug a container that has exited?

- You need to import an existing AWS VPC into Terraform. What are the steps?

- How would you implement blue-green deployment in Kubernetes?

- How do you manage secrets in Terraform without hardcoding them?

- What's the difference between COPY and ADD commands in Dockerfile?

- How would you implement cross-account resource provisioning using Terraform?

- How would you handle secrets in a Docker container for a PHP application connecting to MySQL?

- An S3 bucket was created via Terraform, but someone manually added a policy. How do you handle this drift?

- How do you implement network policies to restrict pod-to-pod communication in Kubernetes?

- Write a Python script to backup all files older than 30 days from a directory.

- Your company's cloud costs are increasing rapidly. - How would you approach cost optimization without impacting performance?

- How would you set up geolocation-based routing using AWS services?

- A critical production Kubernetes cluster is experiencing multiple issues. Pods are stuck in ImagePullBackOff, some pods are being evicted, and users are reporting 503 errors from the application. What troubleshooting process will you follow, and how can to avoid this in the future?


✅ Round 3: Behavioral Round

- How do you handle a situation where you're asked to work on a technology you have no experience with?

- Describe a time when you had to work with tight deadlines and limited resources.

- Tell me about a mistake you made in production and how you handled it.

- Describe the most challenging technical problem you've solved in your career.

- How would you convince stakeholders to adopt a new technology or process?

- Tell me about a time when you had to learn a new tool quickly to solve a business problem.

Comments

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 ðŸ”¹ Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...