Git

Git interviews test whether you can collaborate on shared history safely—not recite every flag. Strong answers connect the commit graph, branch policy, review workflow, history debugging, and release traceability to team delivery constraints.

This domain spans basics (commit, branch, merge, rebase, cherry-pick, stash, tag, remote), collaboration (pull requests, review, conflicts, branching models), history tools (log, diff, blame, bisect, reflog), and quality practices (atomic commits, messages, release tags).

On interviews: for a team shipping weekly, explain branch protection, PR sizing, when to rebase vs merge, how you would find a regression, and how release tags tie to deployments.

Common pitfalls: treating Git as file backup; rewriting shared history casually; huge PRs; history tools without tests; moving published release tags.

The trade-off is workflow ceremony versus integration speed — match policy to test maturity, release cadence, and rollback needs.

Checklist:

• Start from the commit graph mental model.
• Separate local cleanup from shared integration rules.
• Use history tools with deterministic verification.
• Use child topics for command and workflow depth.