PROGRAMLAMA BECERILERI

GitHub test for hiring

See how candidates handle everyday GitHub work before your technical interview.

10 dakika
15 soru
Intermediate
Multiple choice
Questions in İngilizce
Phone and desktop

Use this test free See the question formats

Kısa yanıt

The GitHub assessment is a 10-minute check of practical Git and GitHub skills for developers, software engineers, DevOps and QA engineers, and other technical roles working in shared repositories. Candidates read command sequences, workflow files, pull request states and project boards, then choose what happens next or what to do.

Ölçtüğü şey

Practical Git and GitHub skills: version control, pull request collaboration, GitHub Actions workflows and project tracking.

Git and GitHub basics

Covers everyday version control and how Git and GitHub behave in practical situations.

Collaboration tools

Covers team collaboration through pull requests and their states.

CI/CD with GitHub Actions

Covers automation with GitHub Actions by asking candidates to interpret workflow files.

Project management

Covers planning work with issues and project boards.

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

Front-end, back-end and full-stack developers, software engineers, DevOps and QA engineers, and other technical roles that work in shared GitHub repositories every day.

A focused view of shared-repository skills

Look beyond resume claims
See candidates reason through command sequences, pull request states and project boards, not just describe their experience.
Cover practical workflows
Check version control, pull request collaboration and GitHub Actions workflows in one short assessment.
Use interview time with focus
Use results to choose which GitHub situations to explore in a work sample or structured interview.

What you get for each candidate

Example report (fictional data)GitHub

%72Percentile 48. Benchmark: HireValid candidates, n = 2.392

Git and GitHub basics%74

Collaboration tools%55

CI/CD with GitHub Actions%88

Project management%69

Integrity ScoreYüksek güven

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.

Use this test free

Assessment controls and review signals

Each attempt draws a different question set from large pools, changes question order and shuffles answer options. The browser receives one question at a time, and answer keys stay on HireValid’s servers. The 10-minute timer runs on the server; reloading restores the same question with only the time left, and candidates cannot go back. Question text cannot be copied or selected. HireValid records signals such as time away from the test tab, pastes into answers and answers faster than a question can be read. An Integrity Score and evidence timeline give you signals to review, not an automated decision. Learn how HireValid builds tests and compare with the Git test.

Yapay zekâyla kopya çekmeyi nasıl önlüyoruz · Integrity signals

Use the score as one piece of evidence

Review the score alongside a job-relevant work sample and a structured interview. Ask candidates to explain their choices on a realistic repository task, including how they would handle a pull request or plan work with issues. The assessment is a starting point for your review, not a decision on its own. You can also compare it with the Software Engineer test when choosing an assessment for that role.

Follow up with practical questions

A pull request has conflicts with another branch. How would you handle the change before asking for review?
Listen for a clear sequence of steps and attention to the shared work.
A pull request's checks fail after you push an update. What would you do next?
Listen for how they would inspect the workflow result and decide on a next action.
How would you track a small feature from initial request through completion using issues and a project board?
Listen for a practical approach to organizing and updating work.

Understand scoring and benchmarks

Fairness and accommodations

Questions ask how Git and GitHub behave, not where a button sits or which editor or operating system a candidate uses. Every feature asked about is available to a public repository on GitHub's free plan, so no question depends on access to a paid plan. Questions use plain US English, short code samples and small tables, with people's names from many backgrounds, and no question needs a calculator.

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.

Adil yaklaşımımızı okuyun

Test details

A short, timed check of working knowledge of Git and GitHub. Candidates read command sequences, workflow files, pull request states and project boards, and decide what happens next or what to do. It covers everyday version control, team collaboration through pull requests, automation with GitHub Actions, and planning work with issues and projects.

Questions are in English.
No aids are needed.
Each question is answered once, in order, with no going back.
4 practice questions, 3 minutes, before the timed test.

Git, GitHub, GitHub Actions are trademarks of their owners. HireValid is not affiliated with or endorsed by them.

Sık sorulan sorular

What does the GitHub assessment measure?+

It measures practical Git and GitHub skills: everyday version control, collaboration through pull requests, GitHub Actions workflows, and planning work with issues and projects. Candidates interpret command sequences, workflow files, pull request states and project boards.

Who should use the GitHub assessment?+

It is designed for hiring front-end, back-end and full-stack developers, software engineers, DevOps and QA engineers, and other technical roles that work in shared GitHub repositories every day.

How long is the GitHub assessment?+

The assessment has 15 multiple-choice questions and takes 10 minutes. Candidates can try a separate practice set with 4 questions in 3 minutes. The assessment works on desktop and mobile, but candidates cannot return to an earlier question.

Does the GitHub assessment depend on a paid plan or a particular editor?+

No. Every feature it asks about is available to a public repository on GitHub's free plan, and questions ask how Git and GitHub behave, not where a button sits or which editor or operating system a candidate uses. Questions use short code samples and small tables, and none needs a calculator.