Sign in
← All guides
Software developer / ITISCO 2512Grounded in official sources · 2026-07-26

How to verify a Software developer / IT CV — standards

Software developer and IT CVs (ISCO 2512 for software developers, 3512 for ICT support) are among the hardest to assess. There is no single trade licence to look at, job titles mean different things in different companies, and a list of technologies says nothing about the level at which someone actually worked.

There are official reference points. EN 16234-1, the European e-Competence Framework (e-CF), describes 41 ICT competences on proficiency levels e-1 to e-5. Vendor certifications (AWS, Azure, GCP, CKA/CKAD, Cisco) and ISTQB for testing carry IDs, levels and expiry dates. A rigorous check maps the CV to e-CF competences, validates certificate IDs, and confirms production references and public code. WorkerProof verifies each CV three times against these sources.

What a strong CV must contain

e-CF competences and levels, not buzzwords

A strong CV maps its claims to EN 16234-1 (e-CF) competences — for example programming, solution deployment or security management — with a proficiency level from e-1 to e-5. That tells you whether the candidate executes tasks, designs solutions or leads on architecture.

Certificate IDs and expiry dates

Vendor certifications such as AWS, Azure, GCP, Kubernetes (CKA/CKAD), Cisco (CCNA/CCNP) and ISTQB carry a level, an ID and an expiry date. The CV should list all three so they can be checked against the issuer's register rather than taken on trust.

Production system references

Ask for references to systems that actually ran in production, with the scale (users, requests, data volume) and the stack. This is the ICT equivalent of a work record: it shows the environment the candidate operated in, not just the tools they have read about.

Public code or portfolio

A GitHub profile, portfolio or reviewable code sample lets you see commit history, code quality and consistency with the claimed seniority. It is the fastest independent evidence for the e-CF level a candidate claims.

Formal education mapped to EQF

Degrees should be stated with the EQF level, and bootcamps should be paired with documented practice. Neither replaces the other: education plus applied work is what makes a claimed e-CF level plausible.

Documentation and requirements work

Look for concrete evidence of ESCO skills such as define technical requirements and provide technical documentation, plus debug software and utilise computer-aided software engineering (CASE) tools. Ask for a sample specification or documentation artefact where confidentiality allows.

⚠️ Red flags to watch for

Technology list without contextTwenty technologies with no project, no scale and no role attached. Without a production reference or e-CF level, the list cannot be verified and usually reflects exposure rather than competence.
Certifications without IDs or dates"AWS certified" or "Kubernetes certified" with no certificate ID, level or expiry date. Vendor certifications are verifiable by design, so missing identifiers are a signal to request the original credential.
Expired credentials presented as currentAWS, Azure, GCP, CKA/CKAD and Cisco certifications expire. A certificate listed with no date, or an expired one presented as active, changes what the candidate can be assigned to today.
Senior title, junior evidenceAn architect or lead title alongside public code and project descriptions that match e-1 or e-2 tasks. The gap between claimed and demonstrated e-CF level should be resolved before an interview is scheduled.
No verifiable code or reference at allNeither public code, nor a portfolio, nor a nameable production system, nor a contactable reference. There is then nothing to verify beyond the document itself, which is a risk for international placements in particular.

Questions to ask the candidate

  1. 01Which EN 16234-1 (e-CF) competences describe your work best, and at which level (e-1 to e-5) would you place yourself — with an example from a project?
  2. 02Please give the certificate ID, level and expiry date for each of your vendor certifications (AWS, Azure, GCP, CKA/CKAD, Cisco) and for ISTQB, so we can check them with the issuer.
  3. 03Describe a production system you worked on: what was the stack, what scale did it run at, and what exactly was your part in it?
  4. 04Which repository, portfolio or code sample can you show us, and can you walk us through a commit where you had to debug software under time pressure?
  5. 05How do you define technical requirements and provide technical documentation in your current team — and which CASE or supporting tools do you use for it?

The official standards behind the score

WorkerProof checks every CV against this verified matrix.

Frameworks & certification
  • EN 16234-1 — European e-Competence Framework (e-CF)
  • Vendor certifications (AWS / Azure / GCP / CKA / Cisco)
  • ISTQB (software testing)
Skills evidence
  • Production system references (scale, stack)
  • Public code (GitHub / portfolio)
  • EQF degrees / bootcamp + practice
Official ESCO skills for this occupation · software developer
View on ESCO portal
use technical drawing softwaredebug softwaretechnical drawingsprovide technical documentationutilise computer-aided software engineering toolsdefine technical requirements

Frequently asked questions

Is there an official standard for IT skills in Europe?

Yes. EN 16234-1, the European e-Competence Framework (e-CF), is the official European standard for describing ICT skills. It defines 41 competences, from programming to security management, on proficiency levels e-1 to e-5, in a vendor-neutral way.

How do I verify an AWS, Azure or Kubernetes certification?

Vendor certifications have a level, a certificate ID and an expiry date, so they can be checked against the issuer's verification service. Ask the candidate for all three; a certification named without an ID or date cannot be confirmed.

Do vendor certifications replace a degree in IT?

They cover different things. Vendor exams such as AWS, Azure, GCP, CKA/CKAD, Cisco and ISTQB play the role that trade certificates play in other occupations, while EQF-rated degrees or a bootcamp combined with documented practice cover the educational side. Strong CVs show both plus production experience.

What evidence proves a developer's actual level?

Three sources together: e-CF competences with a stated level, production system references including scale and stack, and public code or a portfolio. Each can be checked independently, which is why they are more reliable than job titles.

Does WorkerProof confirm that a qualification is recognised in my country?

No. WorkerProof verifies documents and the claims made in the CV — certificate details, references, education records and their mapping to EN 16234-1 and ESCO skills — three times per CV. Formal recognition of qualifications is decided by the competent national authorities, not by us.

Stop guessing. Verify.

Upload a CV and get a scored, 3×-verified report against these exact standards in minutes.

Analyze a CV free
10 free analyses · no card required