DevOps-Interview-Guide Repository Structure: Complete Directory Breakdown

The DevOps-Interview-Guide repository follows a hierarchical "company → interview file" structure where top-level directories represent specific employers, and Markdown files within them contain role-specific interview experiences with numeric suffixes indicating multiple rounds.

The DevOps-Interview-Guide is an open-source collection of real-world DevOps interview experiences organized for rapid navigation and community contributions. Understanding the DevOps-Interview-Guide repository structure helps you locate specific company interviews quickly and ensures your submissions follow the established conventions used across the project.

Root Level and Company Directories

At the repository root, the [README.md](https://github.com/litu54/DevOps-Interview-Guide/blob/main/README.md) file provides the primary documentation alongside top-level directories named after specific companies. Each company folder—such as Infosys/, Amazon/, or Wipro/—acts as a container for one or more Markdown files representing distinct interview experiences.

This flat hierarchy eliminates nested navigation, allowing you to access any company's interviews by entering a single directory level.

Interview File Naming Conventions

Files within company folders follow strict naming patterns that indicate the role and interview sequence:

• DevOps_Engineer.md – Default naming when documenting a standard DevOps role
• DevOps_Engineer_2.md, DevOps_Engineer_3.md – Numeric suffixes denoting subsequent interviews for the same company and role
• SRE_principal.md – Explicit role designation when the position differs from standard DevOps titles, such as Site Reliability Engineering

For example, the file [Infosys/DevOps_Engineer_1.md](https://github.com/litu54/DevOps-Interview-Guide/blob/main/Infosys/DevOps_Engineer_1.md) represents the first documented interview experience for that company, while DevOps_Engineer_2.md would indicate a separate candidate's experience or a different interview round.

Anonymous Submissions and the Others Folder

When contributors cannot disclose the company name, submissions reside in the Others/ directory. This folder maintains identical naming conventions to company-specific folders, enabling private contributions without breaking the organizational pattern.

For instance, [Others/DevOps_Engineer_behavioral.md](https://github.com/litu54/DevOps-Interview-Guide/blob/main/Others/DevOps_Engineer_behavioral.md) contains behavioral interview questions from an undisclosed employer, following the same Markdown format as named company files.

Repository Metadata and Supporting Files

Beyond interview content, the repository includes auxiliary files supporting maintenance and tooling:

• opencode.json – Contains repository metadata used by hosting platforms for indexing and display purposes
• .git/ – Standard Git version-control data tracking repository history
• README.md – Provides high-level overview, contribution guidelines, and usage instructions

These files reside at the root level alongside company directories but do not contain interview content.

Practical Commands for Repository Navigation

Use these shell commands to efficiently explore the DevOps-Interview-Guide structure locally:

List All Company Directories

To see every company represented in the collection:

# Show only top-level directories (company folders)

find . -mindepth 1 -maxdepth 1 -type d -not -path "./.git" -printf "%f\n"

Search for Specific Topics Across Interviews

Find every interview file mentioning Kubernetes:

# Search the whole repo for the keyword "Kubernetes"

grep -Ri "Kubernetes" ./**/*.md

Open Specific Interview Files

Using VS Code to open a particular interview:

# Replace <Company> and <File> with the desired values

code <Company>/<File>.md

# Example:

code Infosys/DevOps_Engineer_1.md

Generate Random Interview Selection

For daily interview preparation, retrieve a random write-up:

#!/usr/bin/env bash

# Pick a random markdown file from any company folder

shuf -n1 <(find . -type f -name "*.md" -not -path "./README.md") | xargs -r cat

Summary

• The DevOps-Interview-Guide uses a flat hierarchy where top-level directories represent companies like Infosys/ and Amazon/
• Interview files follow the pattern <Role>_<Number>.md with optional numeric suffixes for multiple rounds at the same company
• The Others/ folder handles anonymous submissions using identical naming conventions to maintain organizational consistency
• Auxiliary files like opencode.json and README.md reside at the root level and provide metadata and contribution guidelines
• All interview content uses Markdown format for consistent searchability across specific technologies and tools

Frequently Asked Questions

What is the purpose of the numeric suffix in interview filenames?

The numeric suffix (e.g., _1, _2) distinguishes between multiple interview experiences submitted for the same company and role. For example, DevOps_Engineer_1.md and DevOps_Engineer_2.md represent two different candidates' experiences or separate interview rounds at the same company, allowing the repository to maintain multiple data points per employer without naming collisions.

How does the repository handle confidential or anonymous company interviews?

Anonymous submissions that cannot disclose the employer name are placed in the Others/ directory at the repository root. These files follow the same naming conventions as company-specific folders, allowing contributors to share experiences while maintaining privacy, as demonstrated by files like Others/DevOps_Engineer_behavioral.md.

Where can I find the main documentation explaining how to contribute to the repository?

The main documentation resides in [README.md](https://github.com/litu54/DevOps-Interview-Guide/blob/main/README.md) at the repository root. This file explains the collection's purpose, provides contribution guidelines, and offers a high-level overview of the content structure according to the DevOps-Interview-Guide source code organization.

What file types are used for interview content in the repository?

All interview content uses Markdown (.md) files exclusively. This ensures consistent formatting, renders properly on GitHub, and enables text-based search across the repository for specific technologies like Kubernetes or Terraform using standard grep or IDE search functions.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}