How Multiple Interview Experiences from the Same Company Are Handled in the DevOps Interview Guide

The DevOps-Interview-Guide repository handles multiple interview experiences from the same company by storing them as separate Markdown files with numeric suffixes inside a company-named folder.

The litu54/DevOps-Interview-Guide repository aggregates DevOps interview experiences from various tech companies. When multiple candidates share experiences from the same organization, the repository uses a systematic file naming convention to prevent collisions and maintain chronological order.

Repository Structure and Naming Convention

Company-Level Folder Organization

Each company receives its own dedicated directory at the repository root. Top-level folders such as Wipro/, Capgemini/, and Infosys/ serve as containers for all experiences related to those specific organizations.

Distinguishing Multiple Experiences

When a company folder contains several interview rounds, files follow the pattern <Role>_<Number>.md. The numeric suffix distinguishes between different interview tracks, timestamps, or candidate submissions. Single entries use the simplified format <Role>.md without numeric suffixes.

For example, the Wipro folder contains five separate experience files:

• Wipro/DevOps_Engineer_1.md
• Wipro/DevOps_Engineer_2.md
• Wipro/DevOps_Engineer_3.md
• Wipro/DevOps_Engineer_4.md
• Wipro/DevOps_Engineer_5.md

Similarly, Capgemini maintains three distinct experiences at Capgemini/DevOps_Engineer_1.md, Capgemini/DevOps_Engineer_2.md, and Capgemini/DevOps_Engineer_3.md, while Infosys houses three separate entries at Infosys/DevOps_Engineer_1.md, Infosys/DevOps_Engineer_2.md, and Infosys/DevOps_Engineer_3.md.

Companies with single submissions, such as Sony, use the format Sony/DevOps_Engineer.md without numeric suffixes.

Programmatically Accessing Interview Files

You can leverage this predictable structure to extract interview data programmatically. The following Python snippet demonstrates how to list all experiences for a given company according to the repository's organization:

import os
from pathlib import Path

def list_interview_files(company: str, base_path: str = "Wipro"):
    """
    Returns a sorted list of interview markdown files for the specified company.
    """
    company_dir = Path(base_path) / company
    if not company_dir.is_dir():
        raise FileNotFoundError(f"Company folder {company_dir} does not exist.")

    md_files = sorted(
        f.name for f in company_dir.glob("*.md") if f.is_file()
    )
    return md_files

# Example usage:

print(list_interview_files("Wipro"))

# Output:

# ['DevOps_Engineer_1.md', 'DevOps_Engineer_2.md', 'DevOps_Engineer_3.md',

#  'DevOps_Engineer_4.md', 'DevOps_Engineer_5.md']

To construct direct GitHub URLs for each file:

BASE_URL = "https://github.com/litu54/DevOps-Interview-Guide/blob/main"

def github_url(company: str, filename: str) -> str:
    return f"{BASE_URL}/{company}/{filename}"

for f in list_interview_files("Wipro"):
    print(github_url("Wipro", f))

Summary

• Company folders serve as the top-level organizational unit, with each folder named exactly after the company (e.g., Wipro/, Capgemini/, Infosys/)
• Numeric suffixes (_1, _2, _3, etc.) distinguish multiple interview experiences from the same company, appended to the base filename format <Role>_<Number>.md
• Single entries omit the numeric suffix entirely, using only <Role>.md (as seen in Sony/DevOps_Engineer.md)
• Chronological ordering is preserved through the numeric sequence, allowing readers to track the evolution of interview processes over time
• Collision avoidance is achieved without modifying existing files, enabling contributors to add new experiences by simply incrementing the highest existing number

Frequently Asked Questions

What happens if two people submit interviews for the same company on the same day?

The repository maintains separate files with incremented numeric suffixes regardless of submission date. Each experience receives the next available number in the sequence (e.g., DevOps_Engineer_6.md following five existing entries), ensuring unique filenames without timestamp dependencies.

How do I add a new interview experience for a company that already has multiple entries?

Navigate to the existing company folder (such as Wipro/), identify the highest numbered file (e.g., DevOps_Engineer_5.md), and create a new file with the next sequential number (e.g., DevOps_Engineer_6.md). This approach follows the established convention and avoids filename collisions.

Are there any companies with single interview experiences that don't use numbers?

Yes. Companies with only one submission use the simplified format <Role>.md without numeric suffixes. For example, Sony/DevOps_Engineer.md contains a single experience, while folders like Wipro/ contain multiple numbered variants.

Can I rely on the numeric suffixes to determine which interview is most recent?

While numeric suffixes often reflect chronological submission order, they primarily serve as unique identifiers. The repository does not enforce temporal metadata in filenames, so you should verify dates within the Markdown content itself when determining recency.

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