Official Competition Profile and Test Map

Snapshot

Official test format, eligibility, preparation routes, error analysis, EUFTE method and supporting-document planning.

Module status

• •Track: Official competition profile
• •Last verified: 2026-11-01
• •Scope: Independent training aligned to official notice C/2026/4668; official sources always prevail.

Published notice

EPSO published Notice of Competition C/2026/4668 on 8 September 2026. EPSO/AD/430/26 covers two AD 8 fields. Candidates may apply for one field only. The reserve-list targets are 240 successful candidates for artificial intelligence and 254 for cybersecurity.

The application deadline is 13 October 2026 at 12.00 midday, Brussels time. A valid identity card or passport must be uploaded by the same deadline. Other supporting documents are due by 14 January 2027 at 12.00 midday, Brussels time.

Eligibility routes

Candidates need C1 knowledge of one official EU language and B2 knowledge of a different official EU language. For each field, the notice provides four principal education-and-experience routes:

• •a relevant three-year university degree plus seven years of relevant professional experience;
• •a relevant four-year university degree plus six years of relevant professional experience;
• •a relevant five-year university degree plus five years of relevant professional experience; or
• •a three-year university degree in another area plus nine years of relevant professional experience.

The exact accepted study areas, evidence of a field focus and relevant-duty categories differ between artificial intelligence and cybersecurity. Candidates must check Section 3.3 and Annexes II and III of the notice against their own documents.

Published test matrix

All candidates who submit on time are invited to remote-proctored tests. EPSO scores reasoning first. Candidates who pass reasoning have the field MCQ scored. The field score creates the ranking used to decide whose EUFTE script and eligibility are processed. The EUFTE assesses written communication based on documents about EU matters; it is not a factual-knowledge test.

Training boundary

This package now uses the published test clock and maps its AI and cybersecurity study scope to the duty categories in Annex II. The notice does not publish a detailed field-MCQ syllabus. Official notice C/2026/4668, the EPSO competition pages and later candidate messages always prevail.

Build a preparation route for your chosen field

Start with the field selected in your application. AI and cybersecurity share some concerns, including data protection, procurement and incident management, but they have different professional profiles. Studying every technology equally is an inefficient response to a specialist competition.

For AI, work through Chapters 5–10 and use Chapters 11–14 when a problem involves security engineering or operational resilience. For cybersecurity, work through Chapters 11–14 first, then use Chapters 7, 9 and 10 for data governance, AI security and evaluation. Chapters 2–4 explain how to apply specialist judgement in an EU organisation.

The EU Knowledge database remains the reference for institutions, Treaty principles, legislative procedures and the budget. This course uses that foundation in professional decisions. You do not need to repeat the entire general course before starting field practice.

Build a coverage record with four columns: professional duty, supporting chapter, evidence that you understand it, and unresolved weakness. A chapter is complete when you can apply it to a new situation, explain the alternatives and identify the evidence needed for a decision.

Read Annex II as a professional profile

The AI profile includes developing and integrating solutions, ensuring defensible and compliant use, and contributing technical expertise to policy. The cybersecurity profile includes assurance and risk, architecture, operations, governance, and specialist advice. These are preparation boundaries, not a published distribution of examination questions.

Turn a duty into an observable skill. For example, “incident response” should lead to several tasks: interpret a timeline, decide an immediate containment action, preserve evidence, identify reporting responsibilities, and verify recovery. Memorising the name of a response phase demonstrates only a small part of that skill.

Use the same method for AI evaluation. Be able to identify data leakage, select an appropriate metric, distinguish a retrieval failure from a generation failure, and explain why a benchmark does not establish suitability for a different task.

Practise the field test at the right level

Thirty questions in forty minutes give an average of eighty seconds per question. This is a pacing aid, not a requirement to spend exactly eighty seconds on every item. A short recognition question can fund more time for a scenario with several constraints.

Use three passes in a practice session:

1. Answer clear items and mark uncertain ones without repeatedly rereading them.
2. Revisit questions where one missing distinction can resolve the choice.
3. Use remaining time to check the requested action, qualifiers and unanswered items.

Afterwards, classify each error. A knowledge gap needs study; a missed condition needs closer reading; an attractive but incomplete option needs comparison of alternatives; a slow answer needs more fluent application. Repeating the same mock without diagnosing errors can improve recognition while leaving the underlying weakness intact.

An illustrative practice result is 21/30 with six confident errors and three guesses. Reviewing only the guesses misses the greater problem: the six confident errors may reveal incorrect rules that will be applied again. Record why each wrong choice looked convincing and what evidence changes the conclusion.

Keep reasoning practice separate from field knowledge

The reasoning tests assess how you process information, not whether you recognise cybersecurity terminology. Numerical work needs reliable interpretation of units, bases and percentage changes. Verbal work needs conclusions supported by the supplied passage. Abstract work needs rules that explain every relevant feature.

Maintain a separate error log for reasoning. Do not import external knowledge into a verbal passage or assume that a visually plausible abstract option satisfies every rule. Use the official clocks when assessing readiness and untimed practice when learning a method.

The numerical and abstract results have a combined pass rule, but treating one component as expendable creates avoidable risk. Establish a reliable baseline in both before concentrating on marginal speed improvements.

Prepare for EUFTE through evidence and communication

EUFTE assesses written communication. General EU reading can make a dossier easier to understand, but a rehearsed essay can become irrelevant when the task asks a different question.

In a practice essay, identify the audience, requested output, relevant evidence, constraints and recommendation. Organise the response around the decision the reader must make. Explain a trade-off when it changes the recommendation; omit background that does not help answer the task.

A useful forty-minute practice allocation is five minutes to read and plan, thirty to draft and five to review. Adjust it to your reading speed. During review, check whether the opening answers the question, every factual claim is supported, paragraphs have distinct purposes and the conclusion identifies a practical next action.

Use the EUFTE guide through the site's written-preparation navigation for the current method and exercises. Follow the exact task and candidate instructions when they are supplied.

Maintain an evidence file

Eligibility is a separate gate from examination performance. Create a chronology linking qualifications and professional experience to the required field. For each employment period, retain dates, working arrangements, duties and available supporting documents. A job title alone may not demonstrate the work performed.

The published supporting-document deadline is 14 January 2027 at midday Brussels time. The cybersecurity competition page currently indicates January 2027 as an indicative testing period. Treat an indicative period as planning information; an invitation or later official update determines the arrangements that apply to you.

Do not use the training site's “last verified” label as a substitute for checking your candidate account. Keep a dated note of the official source and the specific information verified.

Check your understanding

1. Does 15/30 guarantee that a candidate progresses? No. It is the field-test pass floor; ranking and the other requirements also matter.
2. Should a cybersecurity candidate study all general EU history before practising incidents? No. Use the general database for identified foundations and spend most field preparation on specialist duties.
3. Can a well-written EUFTE answer succeed by ignoring the dossier? A polished response still needs to answer the actual task and use the relevant evidence.
4. Is an indicative testing month a confirmed appointment? No. Follow the official invitation and subsequent candidate messages.

Official sources and next steps

• •Competition notice C/2026/4668: Sections 3–4 and Annex II control eligibility, tests and duties.
• •Cybersecurity competition page: current updates and indicative dates.
• •Official specialist sample tests: familiarisation with EPSO assessment formats.
• •EU Knowledge database: targeted background reading rather than a second compulsory field syllabus.