Git test for hiring
See how candidates reason through everyday Git work in a shared repository.
- 10 分钟
- 15 道题
- Intermediate
- Multiple choice
- Questions in 英语
- Phone and desktop
简短回答
The Git test is a 10-minute, 15-question hiring assessment for software engineers, DevOps and site reliability engineers, build and release engineers, systems administrators, and others working in shared Git repositories. It measures practical command use, branching and merging, history rewriting and recovery, and understanding of commits, trees and references through short multiple-choice situations.
测量内容
Practical knowledge of Git, from everyday commands and branching to history rewriting, recovery and Git's object model.
Everyday Git
Candidates pick the commands that record work and share it with teammates, and read what a short terminal session did.
Branching and merging
Candidates predict what a commit history looks like after a merge or a rebase, and choose which fits a team situation.
History rewriting and recovery
Candidates decide how to reshape commits safely and how to get back work that seems lost.
How Git stores data
Candidates reason about commits, trees and references, the objects behind every branch and tag.
Question formats
Multiple choice
The candidate: Reads a short situation, table or statement and picks the right answer, or every right answer.
You see: Whether the candidate knows the material well enough to apply it, not just recognize it.
15 questions in 10 minutes, served one at a time.
Roles this test fits
Software engineers, DevOps and site reliability engineers, build and release engineers, systems administrators, and other roles that work in shared Git repositories.
What this Git test can show
Applied command knowledge
Questions ask candidates to interpret short terminal sessions and choose what a command does or which command fits a situation. This gives you evidence of applied Git knowledge, not only familiarity with command names.
Reasoning about repository changes
A small commit history or a short situation can show how a candidate thinks about the repository after a merge, rebase, history rewrite or recovery action.
Coverage beyond daily commands
The test includes everyday Git, branching and merging, history rewriting and recovery, and Git's object model. Questions on how Git stores commits, trees and references show whether a candidate understands what commands change, not only which ones to type.
A focused screening step
The 10-minute test has 15 questions. Use its score as one piece of evidence to decide where a work sample or structured interview should probe further, rather than treating it as a hiring decision.
What you get for each candidate
- Stayed on the test tab throughout
- No pasted answers
- Answered at a steady pace
Scores, profiles and integrity signals are evidence for you to review alongside an interview, never an automatic decision.
Test format and integrity signals
Each candidate gets a different set of questions drawn from large question pools. Questions appear in a different order for each attempt, and answer options are shuffled. The browser receives one question at a time, and answer keys stay on HireValid’s servers. Timing runs on the server; reloading brings back the same question with only the time that remained. Candidates cannot copy or select question text, and a blocked copy attempt is recorded in the timeline. The test takes 10 minutes, has 15 questions, and does not allow candidates to go back to earlier questions. HireValid records signals such as time away from the test tab, pastes into answers, and answers faster than a question can be read. It summarizes them in an Integrity Score and evidence timeline for the employer to review; it does not decide on its own. With candidate consent, an employer can add webcam photos at random moments.
我们如何防范 AI 作弊 · Integrity signals
Use the score as evidence
Review the score alongside a work sample and a structured interview. It is one signal about practical Git knowledge, not a pass mark, cut-off or decision. For a work sample, give the candidate a small, relevant task in a shared repository and ask them to explain their choices around recording changes, branching, merging or recovery. Use the interview to explore how they would apply those choices with teammates. Keep the same job-related prompts for each candidate and consider the context of the role. For guidance on a candidate-friendly process, see the candidate-friendly hiring guide.
Structured Git interview prompts
A teammate has committed changes on a branch, and your work is on another branch. How would you decide what to do next?
Listen for a clear account of the repository state, the candidate’s intended outcome and how they would choose between relevant branch integration options.
A change has been shared with the team, and someone asks you to rewrite its history. How would you assess the request and explain your approach?
Listen for attention to whether the history is shared, the possible effect on teammates and a reasoned approach to the requested change.
You notice an unexpected result after a Git command. Talk me through how you would inspect the repository and recover if needed.
Listen for a step-by-step investigation, use of repository history or state, and care before making further changes.
How would you help a teammate understand why the repository looks different after a merge or rebase?
Listen for an explanation grounded in the repository’s changes and history, rather than a memorized definition.
Understand scoring and benchmarks
Match the test to the work
This Git test is designed for intermediate-level work in shared Git repositories. It fits software engineers, DevOps and site reliability engineers, build and release engineers, systems administrators, and other roles that work in those repositories. Use the role’s actual responsibilities to decide whether Git knowledge is relevant, then pair the score with evidence from a task that reflects that work. To ask every candidate the same follow-up questions about that work, see the structured interviews guide.
What the questions look like
Candidates answer multiple-choice questions about short situations. They may read a terminal session or a small commit history, then choose what a command does, what the repository looks like afterward, or which command fits the situation. Some items ask for every right answer. The questions cover Git on the command line, including recording and sharing changes, branches, merges and rebases, history rewriting, recovery, and how Git stores commits, trees and references. The Git assessment does not cover a hosting service or graphical tool. A practice set has 4 questions and takes 4 minutes.
Keep the rest of the screen relevant
This test covers Git itself. If a role also depends on Linux or infrastructure work, consider whether a separate skills test is useful alongside a Git work sample. HireValid also offers Linux and Terraform tests. Choose additional assessments based on the tasks in the role, and review each result as separate evidence rather than combining scores into a single decision. Questions use made-up projects, file names and contributors, cover Git on the command line, and follow current Git releases with default settings; any setting that changes an outcome is stated in the question.
Fairness and accommodations
Questions use made-up projects, file names and contributors with names from many backgrounds, and cover Git itself on the command line, not any hosting service or graphical tool. Behavior follows current Git releases with default settings, and any setting that changes the outcome is stated in the question. Terminal output is kept short so each question can be read in the time given.
You can give any candidate extra time as an accommodation. Results are evidence for a person to review, never an automatic decision.
Provisional: reliability is reported once 200 candidates have completed it.
Test details
Short questions on using Git day to day in a team: recording and sharing changes, working with branches, merges and rebases, rewriting and recovering history, and how Git stores commits, trees and references. Most questions show a terminal session or a small commit history and ask what a command does, what the repository looks like afterward, or which command fits a situation.
- Questions are in English.
- No aids are needed.
- Each question is answered once, in order, with no going back.
- 4 practice questions, 4 minutes, before the timed test.
Git is a trademark of its owner. HireValid is not affiliated with or endorsed by it.
常见问题
What does the Git test measure?+
It measures practical Git knowledge across everyday commands, branching and merging, history rewriting and recovery, and Git's object model. Questions use short situations, terminal sessions or small commit histories to ask what a command does, what the repository looks like afterward, or which command fits a situation.
Who is the Git test for?+
It is intended for hiring into intermediate-level roles that work in shared Git repositories. That includes software engineers, DevOps and site reliability engineers, build and release engineers, systems administrators, and other roles with shared-repository work. Use the role's responsibilities to decide whether this assessment fits.
Does the Git test cover hosting services or graphical tools?+
No. The questions cover Git itself on the command line, not a hosting service or graphical tool. They use made-up projects, file names and contributors. Terminal output is kept short so each question can be read in the time given.
How long is the Git test, and can candidates go back?+
The test has 15 questions and takes 10 minutes. Candidates cannot go back to an earlier question. There is also a practice set with 4 questions that takes 4 minutes, so candidates can see the question experience before the test.
How should I use a Git assessment score?+
Treat the score as evidence for a person to review, not as a pass mark or a standalone hiring decision. Compare it with a job-relevant work sample and a structured interview. For example, ask the candidate to explain a repository change or how they would investigate an unexpected result, then consider that evidence with the role's actual requirements.
Do all candidates get the same Git questions?+
No. Each candidate gets a different set of questions drawn from large question pools. Questions appear in a different order for each attempt, and answer options are shuffled. The questions follow current Git releases with default settings, and any setting that changes the outcome is stated in the question.
What should I listen for in a Git interview after the test?+
Ask candidates to reason through a shared-repository situation, such as what they would inspect after an unexpected command result or how they would handle a requested history rewrite. Listen for an explanation of the repository state, likely effects on teammates and a careful next step, then review that evidence alongside the test score.
相关测试
Use the Git test in your next hire
Free 套餐包含 5 项基础测试；付费套餐包含 完整测试题库。