Feature/update interview guides

[mchittineni]

---

Pull Request / Branch Summary: feature/update-interview-guides

1. Overview & Goal

This update introduces repository-wide standardization for interview question guides, adds native Obsidian vault support with structured metadata tags, implements automated PR linting/formatting checks, and enhances documentation across 150+ interview guide files across 35+ company directories.

---

2. Key Enhancements

🏷️ Obsidian Vault & Structured YAML Metadata Support

• Added standardized YAML frontmatter to interview Markdown files (company, role, interview round index, and tags).
• Established a fixed 17-topic vocabulary (kubernetes, docker, terraform, aws, azure, gcp, ci-cd, jenkins, ansible, linux, git, monitoring, sre, networking, security, scripting, databases).
• Enables the repository to be opened directly as an Obsidian vault (Open folder as vault), allowing tag-tree navigation and complex tag queries (e.g. tag:#topic/kubernetes tag:#topic/terraform).

⚙️ CI/CD & Code Quality Automation

• New GitHub Action: markdown-lint.yml runs on every pull request to automatically lint changed Markdown files using markdownlint-cli2.
• Linting Config: Created .markdownlint-cli2.jsonc. Custom rules were configured to ensure auto-fixing preserves question list numbering (MD029, MD030, MD007 disabled), preventing content corruption while enforcing clean formatting (whitespace, blank lines, bare URLs, code block languages).
• PR Template: Added .github/PULL_REQUEST_TEMPLATE.md with a clear checklist covering contribution type, interview details, YAML frontmatter compliance, placement conventions, and formatting checks.

📖 Documentation & README Improvements

• Updated README.md with detailed instructions on:
  • Using the repository as an Obsidian vault.
  • File naming & placement rules (<Role>.md, numbered sequences like DevOps_Engineer_2.md).
  • Formatting guidelines & running the local auto-fix command (npx --yes markdownlint-cli2@0.23.2 --fix "**/*.md").
  • Submitting pull requests using the template.

📝 Interview Markdown Standardizations (35+ Directories)

• Formatted code blocks with language identifiers (e.g. bash, yaml, text).
• Cleaned up stray trailing whitespaces, unformatted inline links, and list block spacing across interview files for companies including:
  • Accenture, Accion Labs, Accolite, Akamai, AMEX, Amazon, Capgemini, Cisco, Commonwealth Bank, Deloitte, EPAM, EY, F5, HCL, IBM, Infosys, JPMorgan, LTIMindtree, Oracle, TCS, Verizon, Wipro, ZS Associates, Others, and more.

---

3. Directory-by-Directory Commit Breakdown

Target Directory / File	Summary of Changes
.github/	Added PR template & GitHub Action workflow for PR markdown linting
.markdownlint-cli2.jsonc	Created markdownlint configuration tailored for ordered Q&A lists
README.md	Added Obsidian vault guide, tag schema, and contribution/formatting steps
Accenture/	Metadata tag fixes and formatting updates in Accenture guides
Accion_Labs/	Formatting and topic tag alignment for SRE interview guide
Altimetrik/	Code fence formatting & list layout fixes
Amazon/	Standardized YAML frontmatter and formatting for DevOps Consultant roles
CGI/	Question listing & YAML header updates
CTS/	Updated 3 DevOps Engineer round files with topic tags
Capgemini/	Standardized formatting for Capgemini DevOps Engineer 1, 2, & 3
Deloitte/	Updated 4 Deloitte interview files with standard tags & code blocks
EPAM/	Standardized 3 EPAM DevOps Engineer interview files
EY/	Added tags and cleaned up formatting in EY interview entries
HCL/	Updated 4 HCL interview guides with proper frontmatter
IBM/	Updated Cloud Engineer and DevOps Engineer 1, 2, 3 files
Infosys/	Standardized Infosys DevOps Engineer & SRE interview guides
JPMorgan/	Updated JPMorgan DevOps & SRE interview files
LTIMindtree/	Standardized 5 LTIMindtree interview entries
Others/	Standardized 20 unnamed interview entries under Others/ (company: "Unknown")
TCS/	Updated TCS DevOps Engineer & SRE files
Wipro/	Standardized 5 Wipro DevOps Engineer files
(Other Companies)	Standardized frontmatter, code blocks, and markdown rules across remaining directories

[mchittineni]

@litu54 PR please.