Qualification requirements

The qualification process involves an automatic analysis of repositories, contributions, activities, social metrics, inferred ratings, etc. on GitHub. Custom algorithms and machine-learning models are used for that. Additionally, each certificate is manually approved by a subject-matter expert from our team.

You are not expected to be an Open-Source guru to obtain a certificate. Just be a dedicated and active community member:

• Push your experiments from a local drive
• Add tags and descriptions to your repositories
• Follow people who inspire you
• Raise issues, ask questions in discussions, save gists
• Fork and collaborate
• Star projects you worked with or find interesting

All that is clearly valuable regardless of DevScanr. Being proactive, open and social will help you to grow a stronger online presence, to learn, to find valuable connections.

Formal requirements

Profile

Your GitHub profile must look like a professional document. To qualify for a certificate:

• Account must not be in the HIDDEN mode.
• Public `Name` has to match real name and surname of a profile owner.
• Public `Avatar` should be a portrait (photo) of a profile owner, in reasonable quality. This one is optional, though, we encourage everyone to have a professional photo, whenever possible. Mismatching avatar will not be added to a certificate.
• Public `Bio` (description) has to contain a job title / specialization.
• Public `Location` must be filled – at least a country of residence.
• Free-form Profile-level README has to be present.

For juniors

At least one year of GH activity

Quality over quantity. Repositories with tags and descriptions, with earned stars and a commit history are ranked much higher than a bunch of empty or cloned repos – just as any educated viewer would rank them. Don’t be shy to share you experiments. Yes, your code is imperfect but it’s better to show it and get a feedback. When it’s negative – you learn something new. When it’s positive – you know it wasn’t that bad...

For other seniorities

2+ years of GH activity

DevScanr algorithms and ML models are designed to operate in a way human specialist would. It means that both “too few” and “too many” extremes, when it comes to data, can be equally bad. Everything should be real and reflect the amount of time you’ve been using GitHub. Fake activity will be detected by anti-fraud heuristics and an account will be skipped.

A DevScanr certificate can only be issued for profiles where our ML was able to infer competences (and, if necessary, a seniority). In infrequent cases, such as for rare specializations and skills, it might fail. We’re sorry for all bugs and imperfections, knowledge analysis and evaluation are challenging tasks. To underline, the more work and activity you share – the more precise our inference can be. But we dont demand anything supernatural.