Interview Q&A

Master technical and career interviews with structured answers—short definition, real examples, pitfalls, and how to answer in 60–90 seconds.

4608 total questions 4508 technical 100 career & HR 4272 from PDF library

Showing 1626–1650 of 3281

Career & HR topics

By tech stack

Popular tracks

Mid PDF
GitHub workflow?

Short answer: A common collaboration model involving forking, branching, pull requests, and code review. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never rea…

Version Control Read answer
Mid PDF
Code review?

Short answer: improve quality, and ensure best practices. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed. Say this in the interv…

Version Control Read answer
Mid PDF
Code review?

Short answer: The process of other developers examining source code to find bugs, improve quality, and ensure best practices. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so br…

Version Control Read answer
Mid PDF
GitHub Actions?

Short answer: An automation platform that allows you to define custom workflows to build, test, and deploy code directly from GitHub. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI chec…

Version Control Read answer
Mid PDF
Pull Request?

Short answer: nother, typically involving code review. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed. Say this in the interview…

Version Control Read answer
Mid PDF
Pull Request?

Short answer: A request to merge changes from one branch (often from a fork) into another, typically involving code review. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so brok…

Version Control Read answer
Mid PDF
Git LFS? Git Large File Storage - a Git extension for versioning large files outside

Short answer: the main repository, storing pointers in Git while files are on a remote server. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach product…

Version Control Read answer
Mid PDF
Git hooks?

Short answer: receive. Used for automation and enforcing policies. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed. Say this in t…

Version Control Read answer
Mid PDF
Git hooks?

Short answer: Scripts that Git executes before or after events like commit, push, and receive. Used for automation and enforcing policies. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI…

Version Control Read answer
Mid PDF
Git submodules?

Short answer: subdirectory, maintaining separate histories. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed. Say this in the inte…

Version Control Read answer
Mid PDF
Git submodules?

Short answer: Allows you to embed one Git repository inside another as a subdirectory, maintaining separate histories. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken bu…

Version Control Read answer
Mid PDF
'Detached HEAD'?

Short answer: branch name, meaning you're not on any branch. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed. Say this in the int…

Version Control Read answer
Mid PDF
'Detached HEAD'?

Short answer: When your HEAD pointer points directly to a commit instead of a branch name, meaning you're not on any branch. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so bro…

Version Control Read answer
Mid PDF
Interactive HEAD?

Short answer: Interactive Rebase: git rebase -i <commit> - allows you to squash, reorder, edit, or drop commits during a rebase operation. Interactive Rebase: git rebase -i <commit> - allows you to squash, re…

Version Control Read answer
Mid PDF
Interactive HEAD?

Short answer: (Typo for "Interactive Rebase"?) Interactive Rebase: git rebase -i <commit> - allows you to squash, reorder, edit, or drop commits during a rebase operation. Real-world example (ShopNest) Sh…

Version Control Read answer
Mid PDF
Git bundle?

Short answer: objects into a single file for easy transfer without a network connection. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production un…

Version Control Read answer
Mid PDF
Git bundle?

Short answer: git bundle create <file.bundle> <ref> - packs Git refs and objects into a single file for easy transfer without a network connection. Real-world example (ShopNest) ShopNest’s team uses GitHub PR…

Version Control Read answer
Mid PDF
Git blame?

Short answer: git blame <file> - shows who last modified each line of a file and when. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach productio…

Version Control Read answer
Mid PDF
Git worktree?

Short answer: directory linked to your main repository, allowing you to work on multiple branches simultaneously. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds…

Version Control Read answer
Mid PDF
Git worktree?

Short answer: git worktree add <path> <branch> - creates a new working directory linked to your main repository, allowing you to work on multiple branches simultaneously. Real-world example (ShopNest) ShopNes…

Version Control Read answer
Mid PDF
Bare repository?

Short answer: used as a central remote repository (e.g., on a server). Say this in the interview Define — one clear sentence (the short answer above). Example — relate it to a project like ShopNest or your real work. Tra…

Version Control Read answer
Mid PDF
Bare repository?

Short answer: A Git repository that does not have a working directory, typically used as a central remote repository (e.g., on a server). Say this in the interview Define — one clear sentence (the short answer above). Ex…

Version Control Read answer
Mid PDF
git stash?

Short answer: llowing you to switch branches and come back to them later. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed. Say th…

Version Control Read answer
Mid PDF
git stash?

Short answer: Temporarily saves changes that are not ready to be committed, allowing you to switch branches and come back to them later. Real-world example (ShopNest) ShopNest’s team uses GitHub PRs with reviews and CI c…

Version Control Read answer
Mid PDF
Squashing commits?

Short answer: commit, typically done during an interactive rebase. Real-world example (ShopNest) Prefer clear commits: fix(cart): prevent negative quantities instead of update . Say this in the interview Define — one cle…

Version Control Read answer

Git & GitHub Developer Essentials · Version Control

Short answer: A common collaboration model involving forking, branching, pull requests, and code review.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: improve quality, and ensure best practices.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: The process of other developers examining source code to find bugs, improve quality, and ensure best practices.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: An automation platform that allows you to define custom workflows to build, test, and deploy code directly from GitHub.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: nother, typically involving code review.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: A request to merge changes from one branch (often from a fork) into another, typically involving code review.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: the main repository, storing pointers in Git while files are on a remote server.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: receive. Used for automation and enforcing policies.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: Scripts that Git executes before or after events like commit, push, and receive. Used for automation and enforcing policies.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: subdirectory, maintaining separate histories.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: Allows you to embed one Git repository inside another as a subdirectory, maintaining separate histories.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: branch name, meaning you're not on any branch.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: When your HEAD pointer points directly to a commit instead of a branch name, meaning you're not on any branch.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: Interactive Rebase: git rebase -i <commit> - allows you to squash, reorder, edit, or drop commits during a rebase operation. Interactive Rebase: git rebase -i <commit> - allows you to squash, reorder, edit, or drop commits during a rebase operation.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: (Typo for "Interactive Rebase"?) Interactive Rebase: git rebase -i <commit> - allows you to squash, reorder, edit, or drop commits during a rebase operation.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: objects into a single file for easy transfer without a network connection.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: git bundle create <file.bundle> <ref> - packs Git refs and objects into a single file for easy transfer without a network connection.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: git blame <file> - shows who last modified each line of a file and when.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: directory linked to your main repository, allowing you to work on multiple branches simultaneously.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: git worktree add <path> <branch> - creates a new working directory linked to your main repository, allowing you to work on multiple branches simultaneously.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: used as a central remote repository (e.g., on a server).

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: A Git repository that does not have a working directory, typically used as a central remote repository (e.g., on a server).

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: llowing you to switch branches and come back to them later.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: Temporarily saves changes that are not ready to be committed, allowing you to switch branches and come back to them later.

Real-world example (ShopNest)

ShopNest’s team uses GitHub PRs with reviews and CI checks so broken builds never reach production unnoticed.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share

Git & GitHub Developer Essentials · Version Control

Short answer: commit, typically done during an interactive rebase.

Real-world example (ShopNest)

Prefer clear commits: fix(cart): prevent negative quantities instead of update.

Say this in the interview

  1. Define — one clear sentence (the short answer above).
  2. Example — relate it to a project like ShopNest or your real work.
  3. Trade-off — when you would not use it.
Permalink & share
Toolliyo Assistant
Ask about tutorials, ebooks, training, pricing, mentor services, and support. I use public site content only—not admin or internal tools.

care@toolliyo.com

Need callback? Share your details