Project Objective – But du projet

The “Smart Borders” project is an initiative aimed at optimizing control at the external borders of the Schengen Area Member States. Smart Borders is part of the Schengen Information System, which is defined by the Schengen Borders Code (Regulation (EU) 2016/399), and itself consists of two sub-projects: EES and ETIAS.

ETIAS (European Travel Information and Authorisation System — Regulation (EU) 2018/1240): this is a future automated computer system aimed at strengthening checks on foreign travelers who are exempt from a short-stay visa to enter European territory, in order to detect potential threats. It is a travel authorization, not a visa.

The Entry/Exit System (EES — Regulations (EU) 2017/2226 and (EU) 2017/2225): this concerns the development of services and web applications for controlling the Schengen borders within the framework of the European Entry Exit System (EES). This includes processing travelers’ alphanumeric and biometric data, verification in the European central systems, and integration into the national border control systems.

Mission – Mission

• You design, develop, and test applications for mobile and fixed devices based on preliminary functional and technical analyses;

• You ensure quality control and development of C# applications in a multi-user environment, with high availability and high visibility;

• You keep up with technological developments, provide technical advice in your specific area of expertise, and propose possible adjustments to projects;

• You analyze, in collaboration with the functional analysts, the needs of the users;

• You meet the expectations and technical specifications of users, taking into account feasibility and the rules and standards within the administration;

• You create and maintain technical documentation;

• You help ensure the maintenance of applications to improve or adapt them to developments in software and hardware;

• You provide adequate technical support;

• You assist in coaching colleagues;

• You work on the full development cycle: back-end (services) and front-end (user interface);

• You develop new applications and improve existing ones;

• You work on complex applications and will play a role in projects with a large scope.

Duration of the mission – Durée de la mission

220 days per year – 220 jours annuels

Development platform – Plateforme de développement

Applications written in the .NET framework, for Windows (and optionally for mobile: Android & iOS, via Xamarin).

Work environment: Windows 10, Office 365, Visual Studio 2019.

Development language – Language de développement

C#, .NET Framework (Pro: knowledge of/connaissance de Xamarin)

Required skills – Compétences recherchées

• You have obtained an ICT-oriented master’s degree or you hold a bachelor’s or master’s in computer science;

• You possess extensive knowledge of Microsoft .NET technology and development tools (C#);

• You have a good knowledge of SQL;

• You have experience using development environments in GIT and DevOps;

• You have a good knowledge of developing and using REST web services, applied in C#;

• Experience in a similar position is a strong asset;

• You possess knowledge of the methods and techniques of functional and technical analysis;

• You possess knowledge of the methods and techniques of process description;

• You possess knowledge of analysis in the form of Use Cases, depending on the project;

• You are familiar with Agile and Scrum;

• Optional: You have demonstrable experience in developing mobile applications with Xamarin, at least for the Android operating system;

• You can work independently;

• You can manage your time well and respect deadlines;

• You have a strong team spirit and analytical skills;

• Preferably, you are bilingual (Dutch, French) or, if not, you have sufficient basic knowledge of the second national language to be able to participate smoothly in meetings with other specialists and with user representatives;

• Knowledge of technical English is required.

Expected output type – Type output attendu

Technical analysis, activity diagrams, database schema, source code with comments, unit tests, scenario tests, setup files (MSI, APK, …)

Frequency of output availability – Périodicité de mise à disposition des outputs

At the end of each sprint (2 or 4 weeks). – En fin de sprint (2 ou 4 semaines).

Method for defining the expected content/period (sprint)

The Business Unit Manager or the person designated by him defines the