hh-skill-verifications-quizzes is a Russian question bank for the hh.ru skill tests, not a certification tool

Seventeen topic folders, each split by difficulty level

The structure of the repository is the whole design. There is no code, no build, and no tool. There are folders named after skills, and inside each folder one or more Markdown files named after a level.

The coverage is broad for a job board assessment suite. English is covered at B1, B2, and C1. Object oriented programming has basic, intermediate, and advanced. Git has basic, intermediate, and advanced, as do CSS, API, Python, SQL, Scrum, Docker, and Copywriting. JavaScript, HTML, MS Excel, AutoCAD, Java, PostgreSQL, and Agile Project Management each have advanced files, and Agile Project Management also has an intermediate one, while Copywriting and AutoCAD start at basic.

That levelling is the useful part. The project page links out to the hh.ru page listing the skill verification methods, so the intended workflow is to pick the skill you want confirmed, open the matching file, and work through the questions at the level the test expects. Someone who has used Git professionally but never sat the Russian assessment gets a different set of questions from a junior candidate, and the folder names make that difference explicit.

Everything is in Markdown, in Russian, which is the single biggest constraint on the repository for anyone outside that market.

Why a confirmed skill matters at all on a Russian job board

The project page explains the motivation, and it is a platform mechanic rather than a technical one. The key skills section of a resume is one of the most important for job search, and many employers use a key skills filter when searching for candidates on hh.ru.

After you pass the testing, a badge saying that skills are confirmed appears on your resume in search results, and inside the resume itself a confirmed skill is highlighted in green. That is the entire mechanism. The badge is a visual differentiator in a list of applicants, and the filter is something employers can apply, so a candidate without a confirmed skill is effectively less findable for those searches.

This reframes what the repository is. It is not a learning resource in the general sense, and it is not a reference implementation. It is preparation for a specific assessment, aimed at a specific outcome: a green badge that changes how a recruiter's search treats your resume.

That is also why the level split matters so much. The test you sit determines which badge you get, and a badge for a different skill or a different level does not help the search you care about.

A disclaimer that names the trademark problem and the risk

The repository is unusually explicit about what it is not, in both Russian and English. The English notice reads that this is an independent study project, not affiliated with, endorsed by, or connected to HeadHunter (hh.ru), and that it exists for informational and educational purposes only. The longer disclaimer adds that all trademarks and brand names are the property of their respective owners and are used solely to indicate the subject matter the content relates to, and that any actions taken with the content are the sole responsibility of the user.

A note at the top of the project page repeats the same point in both languages, and it is repeated again in the disclaimer section near the end.

That repeated framing is not decoration. A repository whose whole content is organised around a commercial job board's assessment tests is exactly the kind of project where the line between preparing for a test and circumventing one matters, and the authors have chosen to state the position rather than leave it implicit. Read that sentence as the project's own characterisation of its scope, and treat the fact that everything sits under an AGPL-3.0 licence as applying to the question and answer content rather than to any code, since there is no code.

The repository doubles as a marketing page for the author's mentoring service

Here is the thing a reader should know before spending an afternoon with the files. The project page is not only a table of contents. A large share of it is promotion for the author's paid mentoring and recruitment services, delivered through Telegram.

The author describes himself as a lead and mentor with more than 18 years in web development, working with the US, UK, and EU markets since 2021, and the repository contains calls to action pointing at a Telegram bot that offers a two minute readiness test for the international market, a table of more than 500 companies with Russian speaking roots, a LinkedIn profile prompt, and a free consultation channel. There is also a case list with income figures for individuals, and a claim about thirty or more students who received offers with an average time to offer of two to five months.

None of that is a reason to reject the question bank. It is a reason to know what you are reading. The question files are the useful artefact and they are free and open. The surrounding page is a sales funnel, and the badge in the corner linking to the owner profile is part of the same design.

A practical consequence: the project is maintained as a funnel, not as a curated curriculum. Topic coverage reflects what is marketable on the platform, not a curriculum design.

Why the answer keys are structured as questions rather than as a tool

The interesting engineering question here is the one that was deliberately not answered. Most projects that provide answers to a test system ship a script, a browser extension, or a bot that reads the test and selects the answer for you. This repository has no such thing. It is a set of Markdown files.

That choice changes what you can do with it and what you cannot. You can read the question pool, learn the shape of the questions, and see the expected depth of an answer. You cannot submit answers on the hh.ru site from this repository, because nothing in it talks to hh.ru.

The tradeoff is obvious and worth stating plainly. A tool that fills in answers would be faster for a candidate who only wants the badge, and it would be useless for someone who wants to be able to answer under pressure in the actual assessment interface. The static form is slower to use and better at its stated purpose, which is described as a collection of questions and content for independent preparation for the tests.

Whether that is sufficient preparation depends on what the assessment actually asks, which is something the repository does not document, so you should treat the files as a question bank rather than as a specification of the test.

Maintenance reality: recent commits, no releases, a licence that most employers dislike

The last push to the repository was on 2026-09-25, so the content is being touched on a recent schedule. There are no GitHub releases, which is normal for a repository of documents, and it means there is no version history to cite when the question pools change.

The licence is AGPL-3.0, and that is an unusual choice for a personal study project. AGPL is the strongest copyleft in common use, and it obliges you to offer the corresponding source of any modified networked program you distribute. For a Markdown question bank that most people read and copy from, that obligation is mostly theoretical. It becomes real if you build something on top of the content and distribute it as a service, and for anyone considering reusing the questions in a paid course or a tool, the licence is the first thing to read carefully.

The repository structure is minimal and consistent with the purpose. There is a .gitignore, a LICENSE, a README, and then the seventeen topic directories, each holding Markdown files named basic, intermediate, or advanced. There is no build tooling, no CI configuration, no test suite, and no scripts directory, which is worth knowing if you were hoping to automate anything with it.

What this repository is not, and when to reach for something else

Two situations call for a different resource.

If you want to learn a skill rather than pass a test on one, this is the wrong tool. The files are organised by assessment level, and a file titled advanced for a given topic is a set of questions with answers, not a curriculum, not a book, and not exercises that build up. Nobody explains the subject to you in order.

If you need a portable qualification for a CV outside Russia, a badge on hh.ru does not carry far. The confirmation travels with the resume on that platform and with the recruiter who reads it there, and it is not a certificate issued by any standards body.

What it does suit is the narrow case it was built for: someone who already knows the subject, has a specific test date, and wants to walk the question pool for that skill and level to see what kind of question gets asked and how detailed the expected answer is.

One more practical point. The assessment is in Russian, and the questions are too, so for a non Russian speaker the repository is useful mainly as a translation reference rather than as preparation. If that is your situation, and you need an English language assessment instead, this project has nothing to offer you.

Editorial conclusion

This repository fits a Russian-speaking developer who is preparing to sit hh.ru skill confirmation tests and wants to see the question format and the expected level of depth per topic before booking a slot. It does not fit an English-reading developer, since the content is written in Russian, and it does not fit anyone who needs a recognised certification, because a badge on hh.ru is not a portable qualification. Before relying on it, check the level files match the test you are booking, and note that the project itself carries a disclaimer saying it is an independent study project with no connection to HeadHunter.

Frequently asked questions

Official sources

1. Issues
2. License: AGPL-3.0
3. Londeren/hh-skill-verifications-quizzes on GitHub
4. Project website
5. README