Feature/update interview guides

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,72 @@
+<!--
+Thanks for contributing an interview experience.
+
+Fill in the details below and tick the checklist. Delete any section that
+doesn't apply (for example, if you're fixing a typo rather than adding a new
+interview, just say so and skip the rest).
+-->
+
+## What's in this PR
+
+<!-- One line: "Adds a DevOps Engineer interview at Acme from March 2026" -->
+
+**Type of change:**
+
+- [ ] New interview write-up
+- [ ] Addition to an existing write-up (more questions from the same interview)
+- [ ] Correction / typo fix
+- [ ] Repo maintenance (tooling, docs, structure)
+
+## Interview details
+
+<!-- Skip this section for corrections and maintenance PRs. -->
+
+| Field | Value |
+| --- | --- |
+| Company | |
+| Role as advertised | |
+| Round(s) covered | <!-- e.g. screening, L2 technical, hiring manager --> |
+| Approximate date | <!-- e.g. March 2026 --> |
+| Years of experience | <!-- the candidate's, if you're comfortable sharing --> |
+| File added | <!-- e.g. Acme/DevOps_Engineer.md --> |
+
+## Checklist
+
+### Content
+
+- [ ] Questions are recorded **as they were actually asked**, not rephrased into polished textbook wording
+- [ ] This is a real interview, not a compiled "top questions" list from elsewhere
+- [ ] No confidential material — no take-home problem statements under NDA, no internal system names, no proprietary architecture details
+- [ ] No personal information about the interviewer (name, contact details, LinkedIn)
+- [ ] Nothing identifying about the candidate beyond role and years of experience
+
+### Frontmatter
+
+- [ ] File starts with YAML frontmatter containing `company`, `role`, and `tags`
+- [ ] `company` matches the folder name, or is `"Unknown"` for entries under `Others/`
+- [ ] `topic/` tags come from the fixed 17-topic vocabulary in the README — no invented topics
+- [ ] Tags reflect what the interview actually covered, not every tool you know
+
+### Placement
+
+- [ ] File is in the correct company folder, or under `Others/` if the company can't be named
+- [ ] Folder name matches the existing convention (underscores for spaces, e.g. `Morgan_Stanley`)
+- [ ] Filename follows `<Role>.md`, numbered if a file for that role already exists (`DevOps_Engineer_2.md`)
+- [ ] An existing file was **not** overwritten or merged into — separate interviews stay in separate files
+
+### Formatting
+
+- [ ] Ran `npx --yes markdownlint-cli2@0.23.2 --fix "**/*.md"` from the repo root
+- [ ] Every code fence has a language tag (```` ```bash ````, ```` ```yaml ````, ```` ```text ````)
+- [ ] Question numbering is intact and sequential — check this by eye after running the fixer
+- [ ] The `Markdown Lint & Format` check passes on this PR
+
+## Anything else
+
+<!--
+Optional. Useful things to mention:
+  - the interview format (live coding, whiteboard, scenario-based, panel)
+  - roughly how long each round ran
+  - whether the questions leaned practical or theoretical
+  - anything that surprised you
+-->

.github/workflows/markdown-lint.yml

@@ -0,0 +1,79 @@
+name: Markdown Lint & Format
+
+on:
+  pull_request:
+    branches: [main]
+
+concurrency:
+  group: markdown-lint-${{ github.event.pull_request.number }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+env:
+  MARKDOWNLINT_VERSION: "0.23.2"
+
+jobs:
+  lint:
+    name: Lint changed markdown
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout PR head
+        uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v7
+        with:
+          node-version: "24"
+
+      - name: Collect markdown files changed in this PR
+        id: changed
+        env:
+          BASE_REF: ${{ github.base_ref }}
+        run: |
+          set -euo pipefail
+          # ACMR: added, copied, modified, renamed — deleted files can't be linted.
+          git diff --name-only --diff-filter=ACMR "origin/${BASE_REF}...HEAD" -- '*.md' > changed.txt
+          COUNT=$(wc -l < changed.txt | tr -d ' ')
+          echo "count=${COUNT}" >> "$GITHUB_OUTPUT"
+          echo "### Markdown files changed: ${COUNT}" >> "$GITHUB_STEP_SUMMARY"
+          if [ "${COUNT}" -gt 0 ]; then
+            sed 's/^/- /' changed.txt >> "$GITHUB_STEP_SUMMARY"
+          fi
+
+      - name: Lint and format check (markdownlint)
+        if: steps.changed.outputs.count != '0'
+        run: |
+          set -euo pipefail
+          # Read-loop rather than mapfile: portable, and keeps paths with spaces intact.
+          FILES=()
+          while IFS= read -r f; do FILES+=("$f"); done < changed.txt
+          npx --yes "markdownlint-cli2@${MARKDOWNLINT_VERSION}" "${FILES[@]}"
+
+      - name: Explain how to fix
+        if: failure()
+        run: |
+          cat >> "$GITHUB_STEP_SUMMARY" <<EOF
+
+          ---
+          ### How to fix
+
+          Almost everything here auto-fixes. From the repository root:
+
+          \`\`\`bash
+          npx --yes markdownlint-cli2@${MARKDOWNLINT_VERSION} --fix "**/*.md"
+          \`\`\`
+
+          Rules that would rewrite list numbering are disabled in
+          \`.markdownlint-cli2.jsonc\`, so \`--fix\` will not renumber your
+          questions. It only touches whitespace, blank lines, and markdown
+          correctness.
+
+          \`MD040 fenced-code-language\` is the one rule that cannot auto-fix:
+          add a language tag to the code fence, for example \`\`\`bash or
+          \`\`\`text for plain output.
+          EOF

.markdownlint-cli2.jsonc

@@ -0,0 +1,37 @@
+{
+  // Lint + format rules for interview-question markdown.
+  //
+  // markdownlint is the ONLY formatter here, on purpose. Prettier was evaluated
+  // and rejected: it renumbers ordered lists, which silently rewrote the
+  // question numbering in 22 of 152 files (one file collapsed 192 numbered
+  // questions to all "1."). In this repo the numbering is content, not style.
+  //
+  // Every rule left enabled below is safe to `--fix` automatically: it only
+  // touches whitespace, blank lines, and markdown correctness.
+  "config": {
+    "default": true,
+
+    // --- Disabled: these rewrite list structure, i.e. the content itself ---
+    "MD029": false, // ol-prefix: would renumber questions
+    "MD030": false, // list-marker-space: churns indentation of every item
+    "MD007": false, // ul-indent: same
+    "MD004": false, // ul-style: bullet char is not worth a repo-wide rewrite
+
+    // --- Disabled: deliberate house style for long-form Q&A ---
+    "MD013": false, // line-length: answers are long-form, wrapping hurts diffs
+    "MD036": false, // no-emphasis-as-heading: **Q:** / **A:** is the style here
+    "MD033": false, // no-inline-html: <details> blocks are used for answers
+    "MD041": false, // first-line-heading: not every fragment starts with an h1
+    "MD024": { "siblings_only": true }, // repeated headings OK across sections
+
+    // --- Enforced (all auto-fixable except MD040) ---
+    // MD012 no-multiple-blanks, MD032 blanks-around-lists, MD034 no-bare-urls,
+    // MD009 trailing-spaces, MD047 single-trailing-newline, MD001
+    // heading-increment, MD040 fenced-code-language, and the rest of defaults.
+  },
+  // NOTE: deliberately no "globs" key. markdownlint-cli2 UNIONS config globs
+  // with the file arguments it is given, so setting it here would make the CI
+  // job lint the whole repo even though it passes only the PR's changed files.
+  // Scope is always controlled by the caller: `markdownlint-cli2 "**/*.md"`.
+  "ignores": ["node_modules/**"]
+}

AMEX/DevOps_Engineer.md

@@ -1,3 +1,15 @@
+---
+company: "AMEX"
+role: "DevOps Engineer"
+tags:
+  - interview
+  - company/amex
+  - role/devops-engineer
+  - topic/kubernetes
+  - topic/docker
+  - topic/sre
+---
+
 # AMEX
 
 **YOE---> 3 yrs**

Accenture/DevOps_Engineer.md

@@ -1,8 +1,21 @@
+---
+company: "Accenture"
+role: "DevOps Engineer"
+tags:
+  - interview
+  - company/accenture
+  - role/devops-engineer
+  - topic/kubernetes
+  - topic/terraform
+  - topic/aws
+  - topic/security
+  - topic/databases
+---
+
 # Accenture
 
 **EXP- 6yrs**
 
-
 - You have created an IAM user in AWS and configured role-based access in EKS. How do you bind the IAM user to the EKS role?
 - Assume you have 10 AWS accounts. How will you securely log in to them, considering access keys are not used for security reasons?
 - What are the ways to log in to an AWS account?

Accion_Labs/SRE.md

@@ -1,3 +1,20 @@
+---
+company: "Accion Labs"
+role: "SRE"
+tags:
+  - interview
+  - company/accion-labs
+  - role/sre
+  - topic/kubernetes
+  - topic/docker
+  - topic/terraform
+  - topic/aws
+  - topic/ansible
+  - topic/linux
+  - topic/sre
+  - topic/scripting
+---
+
 # Accion Labs
 
 **Exp---17yrs SRE**
@@ -12,8 +29,10 @@
 8) What is the Linux command used for mounting a file system?
 9) How do you detect the root cause when an application goes down in the cloud?
 10) How do you respond when:
+
 - a) the master node goes down?
 - b) a worker/slave node goes down?
+
 11) How do you configure a VPC for high availability?
 12) Have you worked on scripting? if so which tool ? explain what you have implemented?
 13) Have you written Terraform code for deployments? If yes, can you explain the implementation?

Accolite/DevOps_Engineer.md

@@ -1,3 +1,17 @@
+---
+company: "Accolite"
+role: "DevOps Engineer"
+tags:
+  - interview
+  - company/accolite
+  - role/devops-engineer
+  - topic/kubernetes
+  - topic/ci-cd
+  - topic/monitoring
+  - topic/scripting
+  - topic/databases
+---
+
 # Accolite
 
 **Exp---- 3yr DevOps Engineer**

Akamai/SRE.md

@@ -1,3 +1,15 @@
+---
+company: "Akamai"
+role: "SRE"
+tags:
+  - interview
+  - company/akamai
+  - role/sre
+  - topic/linux
+  - topic/sre
+  - topic/networking
+---
+
 # Akamai
 
 **Exp---8yrs  SRE**

Alphadyne/DevOps_Engineer_1.md

@@ -1,3 +1,19 @@
+---
+company: "Alphadyne"
+role: "DevOps Engineer"
+interview: 1
+tags:
+  - interview
+  - company/alphadyne
+  - role/devops-engineer
+  - topic/kubernetes
+  - topic/aws
+  - topic/ci-cd
+  - topic/jenkins
+  - topic/networking
+  - topic/security
+---
+
 # Alphadyne
 
 **YOE---> 5 Years**

Alphadyne/DevOps_Engineer_2.md

@@ -1,3 +1,21 @@
+---
+company: "Alphadyne"
+role: "DevOps Engineer"
+interview: 2
+tags:
+  - interview
+  - company/alphadyne
+  - role/devops-engineer
+  - topic/kubernetes
+  - topic/terraform
+  - topic/azure
+  - topic/ansible
+  - topic/linux
+  - topic/monitoring
+  - topic/networking
+  - topic/databases
+---
+
 # Alphadyne
 
 **YOE-->**

Altimetrik/SRE.md

@@ -1,3 +1,19 @@
+---
+company: "Altimetrik"
+role: "SRE"
+tags:
+  - interview
+  - company/altimetrik
+  - role/sre
+  - topic/kubernetes
+  - topic/terraform
+  - topic/aws
+  - topic/gcp
+  - topic/sre
+  - topic/networking
+  - topic/security
+---
+
 # Altimetrik
 
 - Question : How do you import a resource into Terraform that was created manually in AWS or GCP? What command would you use?
@@ -30,17 +46,14 @@
 
 - Question : What is what is an ideal burn rate?
 
-
 - Question : So how you are using terraform to deploy the cluster nodes?
 
 - Question : Set up the nodes and everything. what do you write inside a terraform code basically now what will be inside your provider file provided ATF in your main dotf?
 
 - Question : I'll give you an example like let's talk about AWS. You have you're going to create a VPC and subnet And your provider is AWS and I'm asking you to write in using terraform.
 - Like you have to deploy, you have to basically create VPC and map you have to create a subnet and you have to attach let's be the public or a private submit. It's of your choice to attach it to your VPC.
 
-
 - Question : You have optimized Kubernetes deployment configs. So can you explain me what have what was the role and what what have you done there?
 
-
 - Question : You mentioned about like the are you have architected a blameless postmortem framework, right? So for continuous learning, so how I mean what have you done to improve occurrence of critical incidents that you have mentioned in your resume.
 - You also mentioned about basically to reduce the MTTR so can you explain me what automation that you have done?

Amadeus_Labs/SRE.md

@@ -1,3 +1,16 @@
+---
+company: "Amadeus Labs"
+role: "SRE"
+tags:
+  - interview
+  - company/amadeus-labs
+  - role/sre
+  - topic/kubernetes
+  - topic/linux
+  - topic/sre
+  - topic/security
+---
+
 # Amadeus Labs
 
 **Exp-5yr SRE**