Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Jobs, guidance and training

    Understand Web careers and prepare your path.

    Design, development, content, visibility, quality and project work: this guide introduces the main career families, training routes and reliable resources that can help you move forward.

    It also states Française du Numérique’s recruitment position clearly: we are not currently hiring for any job, internship, apprenticeship or other work-study position.

    Recruitment information · updated 14 August 2026

    We have no positions to fill.

    Française du Numérique currently has no job, internship, apprenticeship or professional work-study contract available. This section is a careers guide; it does not collect applications for an existing vacancy.

    Recruitment closed
    Career guide

    Four families for understanding a diverse sector.

    A title alone never defines a role. Smaller organisations may combine several functions, while larger teams often divide them into narrower specialisms.

    Colour cards arranged in a circle on a light background
    01

    Design and experience

    Understand users, organise information and design clear, accessible and consistent interfaces.

    UX designer

    Studies user needs, journeys and pain points to make a digital service easier to understand and use.

    Typical work: Observe journeys, interview people and check assumptions against real tasks.

    Work sample: A needs summary, journey map and tested prototype.

    Try it: Ask two people to find one fact on a public website, then note where their journeys diverge and what they understood.

    Review question: Which observation changed an initial assumption, and what issue remains after testing?

    Collaboration: Work with writers to check understood wording and with product teams to prioritise obstacles.

    User researchJourneysPrototyping

    UI designer

    Designs interface components and visual systems with close attention to readability, consistency and accessibility.

    Typical work: Define component states, typography and contrast, including common error states in forms.

    Work sample: A documented component library and screens ready for implementation.

    Try it: Sketch the normal, focus, error and disabled states of a form field; check that meaning does not depend on colour alone.

    Review question: Are empty, loaded, disabled and error states documented as carefully as the ideal screen?

    Collaboration: Work with front-end and QA teams to preserve consistent states during implementation.

    InterfaceDesign systemAccessibility

    Web designer

    Translates an identity and its content into Web pages suited to different screens and project objectives.

    Typical work: Design pages with real content, then check narrow screens and longer text.

    Work sample: Mock-ups and visual specifications that an implementation team can use.

    Try it: Design a page with a real heading, two paragraphs and an image, then adapt it to a phone without removing information.

    Review question: Does the visual choice remain readable with real text, a missing image and a small screen?

    Collaboration: Work with writers and implementers to test layouts against real content.

    Art directionResponsive designMock-ups

    Product designer

    Follows a digital product from understanding the problem through to testing and iterative improvement.

    Typical work: Connect research, design decisions and post-launch feedback to improve a feature.

    Work sample: A defined problem, reasoned alternatives and a decision checked in use.

    Try it: State one journey problem, propose two solutions and have someone try a simple prototype before choosing.

    Review question: Which criterion will determine whether to keep, change or retire the feature after delivery?

    Collaboration: Work with analytics and project teams to connect a measurement with design decisions.

    ProductTestingCollaboration
    Laptop, notebook, phone and mug on a desk
    02

    Development and quality

    Turn requirements into reliable, fast, maintainable and secure interfaces and services.

    Front-end developer

    Builds the visible and interactive part of a website or application from designs and specifications.

    Typical work: Turn components into interfaces usable by keyboard and on different devices, then verify their behaviour.

    Work sample: Working pages, tests and component documentation.

    Try it: Build a responsive card with a link, visible focus state and an image alternative suited to its context.

    Review question: Does the journey work with a keyboard, after a network error and with longer translated text?

    Collaboration: Work with design, back-end and QA teams to align behaviours, responses and states.

    HTML & CSSJavaScriptPerformance

    Back-end developer

    Builds server-side logic, databases, data exchanges and the business rules behind a service.

    Typical work: Design processing rules, validate input and permissions, and prepare exchanges with other services.

    Work sample: A documented API or service, tests and a deployment procedure.

    Try it: Describe a small catalogue API with valid inputs, possible errors and tests for a missing item.

    Review question: Can a restricted account trigger an operation or read a resource it is not allowed to access?

    Collaboration: Work with front-end teams to document errors and operations teams to make incidents observable.

    ServerAPIsDatabases

    Full-stack developer

    Works across the interface and server, often with a broad view of architecture and deployment.

    Typical work: Connect an interface to processing and stored data while keeping each layer’s responsibilities clear.

    Work sample: A complete feature tested end to end and ready for handover.

    Try it: Build a filterable list from sample data and check empty, error and item-update cases end to end.

    Review question: Does the displayed result match an operation actually recorded, including after a retry?

    Collaboration: Work with stakeholders and QA to choose cases spanning the complete chain.

    Front endBack endArchitecture

    Web integrator

    Combines content, components and styles to produce accurate, responsive and accessible pages.

    Typical work: Combine templates with real content and check interactions, image alternatives and screen variations.

    Work sample: Implemented pages and a record of differences between design and live rendering.

    Try it: Implement a real article with meaningful headings, links, images and keyboard reading on a narrow screen.

    Review question: Do heading structure, links and reading order survive a content update?

    Collaboration: Work with content and design teams to explain rules that editors can apply in the CMS.

    IntegrationCMSAccessibility

    Web QA tester

    Plans and performs checks that reveal functional, visual, technical or accessibility defects.

    Typical work: Describe expected journeys and edge cases, reproduce defects and check the fixes.

    Work sample: An acceptance plan, reproducible reports and retest results.

    Try it: Write five acceptance cases for a form, including a network failure and recovery after invalid input.

    Review question: Can the defect be reproduced from steps, environment, expected behaviour and observed result?

    Collaboration: Work with each owner to define correction evidence and areas to retest.

    Test plansAcceptance testingAutomation
    Camera, lens and notebook on a wooden table
    03

    Content and visibility

    Create useful information, help audiences find it and measure the quality of real visits.

    Web writer

    Structures and writes useful, understandable content suited to its audience and reading environment.

    Typical work: Interview the audience, organise its questions and revise copy after feedback.

    Work sample: Structured pages with sources, useful headings and update instructions.

    Try it: Rewrite an unclear service description, then ask someone outside the project to summarise the offer.

    Review question: Can a claim be traced to a source and a person able to maintain it?

    Collaboration: Work with subject experts and content teams to validate meaning, sources and review dates.

    EditorialResearchClarity

    SEO consultant

    Improves how a site is understood and discovered through content, technical quality and internal linking.

    Typical work: Examine existing pages and queries, fix crawl barriers and align content with the intended task.

    Work sample: A prioritised diagnosis, page-level recommendations and a measurement method.

    Try it: Choose one page and three plausible queries; identify gaps between intent, answer and next action.

    Review question: Does the change improve a useful answer, and how will its effects be separated from other changes?

    Collaboration: Work with writers, developers and analysts to interpret results without promising rankings.

    AuditingSemanticsData

    Content manager

    Plans, coordinates, publishes and maintains consistent content across digital channels.

    Typical work: Maintain an inventory, schedule contributions, assign review and retire outdated information.

    Work sample: An editorial calendar, publishing rules and a traceable change history.

    Try it: Make a four-item editorial calendar with owner, source, approval date and trigger for revision.

    Review question: Which content lacks an owner, is outdated or remains without an explicit purpose?

    Collaboration: Work with writers, stakeholders and translators to organise approval and replacements.

    StrategyEditorial calendarCMS

    Web analyst

    Turns traffic and journey data into useful findings while respecting visitors and applicable rules.

    Typical work: Define a measurable event or goal, validate collection and explain the limits of the figures.

    Work sample: A measurement plan, readable reports and decisions tied to results.

    Try it: Define two useful journey events, validate their collection and state what the figures cannot prove.

    Review question: Does the metric use a consistent definition and scope, and which decision does it change?

    Collaboration: Work with product and technical teams to distinguish real change, collection errors and scope changes.

    MeasurementDashboardsAnalysis
    Spiral notebook and phone in front of a potted plant
    04

    Project and operations

    Connect objectives, users, content, technology, budgets and continuous improvement.

    Digital project manager

    Frames the need, organises each stage, coordinates contributors and monitors decisions, deadlines and risks.

    Typical work: Clarify scope, order dependencies and resolve requests with accountable stakeholders.

    Work sample: A shared brief, schedule and record of decisions and risks.

    Try it: Plan a small redesign with deliverables, dependencies, owners, approval decision and one risk to monitor.

    Review question: Does a blocking decision have an owner, deadline and described consequence?

    Collaboration: Work with all contributors to expose dependencies and organise acceptance.

    ScopingCoordinationBudget

    Product owner

    Prioritises product needs, clarifies acceptance criteria and connects business teams with delivery teams.

    Typical work: Break needs into testable items, set priorities and clarify acceptance criteria.

    Work sample: An understandable backlog and criteria that support real acceptance testing.

    Try it: Break a search improvement into five ordered items, each with an example of an acceptable outcome.

    Review question: Does the priority reflect an observed need and acceptance criteria understood by the team?

    Collaboration: Work with design, stakeholders and developers to agree scope and trade-offs.

    PrioritisationBacklogProduct

    Webmaster

    Keeps a website running day to day through publishing, small improvements, quality checks and coordination.

    Typical work: Publish and correct content, monitor incidents and coordinate technical updates.

    Work sample: A change log, regular checks and a recovery procedure.

    Try it: Plan a week of site checks: links, dated content, forms, available backup and a log of corrections.

    Review question: Can the next team understand, publish and maintain the site without relying on one person?

    Collaboration: Work with project teams, editors and operations to prepare handover and continuity.

    PublishingMaintenanceVersatility
    Related roles

    Understand what each role contributes to a project

    Eight comparisons explore the sixteen roles presented. Responsibilities vary by organisation; one person may combine roles. The work excerpts below are fictional.

    On a small screen, scroll the tables horizontally to read all three columns.

    UX designer and UI designer

    Research into use and interface design complement each other. Onisep describes observing journeys in UX and collaboration with UI work, which focuses more on graphic design.

    UX designer and UI designer
    Role to exploreWorking questionIllustrative deliverable excerpt
    UX designerWhich obstacle prevents someone finding how to book an appointment?During the observed task, a person opens Prices and then returns home without finding availability. Keep that observation separate from its interpretation.
    UI designerHow can the action and its states be understandable?The component has an explicit label, a visible focus state and a distinct message when no slot is available.

    What passes between the roles

    The task context, observed obstacles and content constraints inform interface proposals. The solution is then checked in use; a design alone does not establish that the obstacle has disappeared.

    References for further reading : Onisep · UX designer (French). Consulted on . The examples were written for these comparisons and do not come from the references.

    Front-end and back-end development

    A single form connects an interface with server processing. MDN distinguishes browser validation from server-side checks and explains that the former does not replace the latter.

    Front-end and back-end development
    Role to exploreWorking questionIllustrative deliverable excerpt
    Front-end developerHow can someone enter and correct an enquiry?The email field keeps its value after an error and displays an explanation associated with the field. Confirmation appears when processing allows it.
    Back-end developerWhich data should be accepted and what happens after receipt?The handler checks incoming data, applies the agreed rules and returns a result the interface can explain.

    What passes between the roles

    Both sides need a shared understanding of fields, accepted formats and possible responses. Checking the journey means examining failure, success and actual enquiry handling beyond the appearance of the button.

    References for further reading : MDN · Form validation (English). Consulted on . The examples were written for these comparisons and do not come from the references.

    Digital project manager and Product Owner

    Project coordination and product accountability are different. In Scrum, the Product Owner is accountable for maximising product value and effective Product Backlog management. This framework does not describe every job carrying that title.

    Digital project manager and Product Owner
    Role to exploreWorking questionIllustrative deliverable excerpt
    Digital project managerWhich people and decisions affect the next stage?Approval of booking conditions awaits an identified person; the open point and its effect on the next review are tracked.
    Product OwnerWhich product need should be clarified and ordered first?A slot request is prioritised before instant confirmation because actual availability still needs to be established with the people concerned.

    What passes between the roles

    Product choices and delivery constraints are discussed with the team. In this example, priority and dependency are separate pieces of information; neither supports promising an unconfirmed date or feature.

    References for further reading : Scrum Guide 2020 · Product Owner (English). Consulted on . The examples were written for these comparisons and do not come from the references.

    Web designer and digital Product designer

    Two perspectives on one service: page identity and the product’s usefulness over time. Product means a digital service here, not industrial design.

    Web designer and digital Product designer
    Role to exploreWorking questionIllustrative deliverable excerpt
    Web designerHow can two offers be presented consistently on phones and computers?A mock-up specifies heading hierarchy, image treatment and card variants. It describes what happens when a title is long or an image is missing.
    Digital Product designerWhich difficulty should be resolved before adding another interface?A comparison plan connects the observed problem, hypothesis, variant to try and decision after testing. A visual preference is not presented as evidence of use.

    What passes between the roles

    Share the visual proposal and the question to check together: mock-up version, target task, constraints and observations. Agree who continues the tests and who decides on changes.

    References for further reading : Onisep · Webdesigner (French) · Design Council · Framework for Innovation (English). Consulted on . The examples were written for these comparisons and do not come from the references.

    Full-stack developer and Web integrator

    In this catalogue example, integration builds the pages and full-stack development connects interface and data. Responsibilities can overlap.

    Full-stack developer and Web integrator
    Role to exploreWorking questionIllustrative deliverable excerpt
    Full-stack developerHow should the displayed filter match catalogue data and rules?A data contract describes accepted values, an empty result and the error returned for an unknown value. The journey is tested from interface to processing, beyond a simulated response.
    Web integratorHow can filters and results be assembled without losing the page’s meaning?A template associates labels with fields, organises headings and covers empty, loading and error states. Long content is checked on small screens and with a keyboard.

    What passes between the roles

    Share display states, data formats and a common test dataset. An interface using mock data does not validate the real exchange; a working server alone does not validate the interface either.

    References for further reading : Onisep · Développement informatique (French) · Onisep · Intégration web (French). Consulted on . The examples were written for these comparisons and do not come from the references.

    QA / Web tester and webmaster

    Checking behaviour and operating a website complement each other. A correction must be traceable and verifiable.

    QA / Web tester and webmaster
    Role to exploreWorking questionIllustrative deliverable excerpt
    QA / Web testerHow can a removed document link still appearing in internal search be reproduced?A defect record gives environment, version, entered query, returned address, expected result and observed result. Repeat the same task after correction without declaring the whole website approved.
    WebmasterWhich updates must be reconciled after the document is removed?An intervention log records the content owner’s decision, affected links, index to refresh and public check performed. Technical credentials stay out of the published log.

    What passes between the roles

    The reproduction record accompanies the intervention and corrected version. Separate the removal decision, operational action and post-change check, with an identifiable owner for each step.

    References for further reading : Onisep · Test en informatique (French) · Onisep · Webmestre (French). Consulted on . The examples were written for these comparisons and do not come from the references.

    Web writer and Content manager

    Writing a page and coordinating its versions are different tasks. Here, a service change affects several pieces of content.

    Web writer and Content manager
    Role to exploreWorking questionIllustrative deliverable excerpt
    Web writerHow can a temporary closure be explained without promising an unconfirmed deadline?The draft answers audience questions using approved facts: affected service, known period, contact alternative and remaining uncertainty. Claims point to their business source.
    Content managerWhich pages and languages must change together, and who approves them?A schedule links each item to its owner, version, review status and next review date. An unapproved translation is not marked ready merely because the source text is ready.

    What passes between the roles

    The text, sources and open questions enter the approval process together. Follow-up also retains related pages, languages and the person who will review the content when circumstances change.

    References for further reading : Apec · Rédacteur (French) · Apec · Brand content manager (French). Consulted on . The examples were written for these comparisons and do not come from the references.

    SEO consultant and Web analyst

    Search visibility and journey analysis provide complementary perspectives. The same word “result” can refer to different events.

    SEO consultant and Web analyst
    Role to exploreWorking questionIllustrative deliverable excerpt
    SEO consultantWhich page answers a customer’s search, and which information is missing?A priority-page list connects the audience question, existing content, information to add and useful internal links. Recommendations promise neither rankings nor AI citations.
    Web analystWhat does each metric measure before two periods are compared?A measurement dictionary distinguishes a visit, contact click and enquiry actually received. It specifies unit, period, filters and collection limits before interpreting a change.

    What passes between the roles

    Share changed pages and their dates alongside measurement definitions. An observed increase alone does not establish the effect of an SEO action; other changes and data limitations need examination.

    References for further reading : Onisep · Référencement web (French) · Onisep · Web analytique (French). Consulted on . The examples were written for these comparisons and do not come from the references.

    Training routes

    Different paths, one requirement: show what you can do.

    The right route depends on the career, your starting point, the time available and the framework you need. A broad promise of a “job in digital” is no substitute for a precise syllabus.

    Books, notes and stationery on a desk
    01

    Academic education

    A technical diploma, bachelor’s degree, master’s degree, specialist school or engineering degree may be relevant. The right level and subject depend on the target role, not merely on the word “digital”.

    02

    Vocational qualification

    Career-focused training can support a specialisation or career change. Always verify the stated qualification, its current status and the awarding organisation.

    03

    Work-study training

    This combines teaching with experience in an organisation. Consider the timetable, actual duties, supervision and qualification together.

    04

    Independent learning

    Courses, documentation and personal projects can build skills, but those skills must be demonstrated through explained and verifiable work.

    Choosing training

    Four signposts for comparing training

    In France, these four signposts answer different questions. Match each claim to the document that lets you check it.

    • RNCP

      A register of vocational qualifications associated with occupations.

      Check : Compare the code, validity, level and provider authorised to prepare candidates.

      Official documentation : France compétences · RNCP

    • RS

      A register of certifications and authorisations without a level in the national qualifications framework.

      Check : Read the assessed skills and the validation requirements.

      Official documentation : France compétences · RS

    • Qualiopi

      The quality of a provider’s processes, for a defined scope of activities.

      Check : Check the certificate’s scope separately from the qualification being prepared.

      Official documentation : Mon Compte Formation · Qualiopi

    • CPF

      A funding scheme, distinct from the qualification sought.

      Check : Compare the offer, entry requirements, dates and remaining amount to pay.

      Official documentation : Mon Compte Formation · Choisir une formation

    Documentation consulted on .

    Resource directory

    14 resources for guidance, training and job searches.

    This selection prioritises French public services, official organisations and specialist bodies with a clearly identifiable destination.

    14 resources displayed

    Training and qualifications

    Afpa · Web developer

    Review the syllabus, entry requirements and delivery arrangements for the Web and mobile Web developer course.

    afpa.frOpen official website

    Service destinations and purposes checked on .

    This selection covers French services independent of Française du Numérique. Inclusion does not imply a partnership or guarantee admission, funding or employment.

    From interest to a practical plan

    Build evidence, not just a list of tools.

    A personal, voluntary, academic or professional project becomes useful evidence when it explains the problem, your decisions, the constraints and the outcome.

    Find the right resources
    1. 01

      Choose a direction

      Compare the routine activities of two or three related careers before selecting a course.

    2. 02

      Practise on a real case

      Complete a small project and document the need, your role, decisions, trade-offs and limits.

    3. 03

      Ask for informed feedback

      Have the content, technology, accessibility and presentation reviewed by people who can explain their comments.

    4. 04

      Adapt each application

      Connect each piece of evidence to the advertised duties instead of sending the same material to every employer.

    Frequently asked questions

    Recruitment, career guidance and choosing training.

    These answers clarify the purpose of this section and the important checks to make before committing.

    No. As of 14 August 2026, Française du Numérique has no permanent or fixed-term position, paid role, internship, apprenticeship or other work-study contract available. This page is an editorial guide and is not a job advertisement. The situation may change; any genuine opening will be published explicitly with its duties, employment framework and application process.

    There is currently no recruitment, internship or apprenticeship need to which an application could be attached. The contact form is intended for Web project and quotation enquiries, not for an unlisted position. Before making any future application, please check that an active vacancy is explicitly published on this page.

    Start with the activities you would like to practise every week: designing an experience, creating an interface, programming, writing, analysing, testing or coordinating. Read several career profiles, examine real work and try a small related activity. Job titles vary considerably between organisations, so compare duties, tools, autonomy and working conditions rather than relying on a title alone.

    Requirements vary greatly by profession, responsibility level and employer. A degree or vocational qualification may help with access to some roles, but completed work, method, the ability to explain decisions and transferable skills also matter. A short course does not guarantee employment, while independent learning does not remove the need to demonstrate a professional standard.

    Identify the target occupation and the skills taught. If a qualification is advertised, check its active record, awarding body, expiry date and authorised training provider on France compétences; for RNCP, also check the level. RS has no level in the national qualifications framework. Compare the syllabus, entry requirements, assessments, total cost, support and documented outcomes. An attendance certificate does not replace the qualification sought.

    No. They are independent public services, official organisations or specialist bodies. These links are starting points, not partnerships or guarantees of training, funding, admission or employment. Content and conditions may change, so always confirm current information on the relevant third-party website.
    Cross-role exercises

    Three small projects for comparing roles in practice.

    Commerce journey: prepare three fictional product entries, then a test grid for basket, declined payment, confirmation and fulfilment. Writing, design, development and testing contribute at different moments; record what each role must deliver and check. The checkout test guide gives observable cases.

    Evidence-led content: write a short explainer from two accessible primary sources. Separate fact, interpretation and example, then ask someone else to retrieve the evidence and flag claims that are too broad. This reveals editorial, research, accessibility and review tasks. Use the source verification guide.

    Simulated incident: imagine a contact form silently stops delivering enquiries. Without changing a real site, write a dated finding, a clear visitor notice, a recovery plan and journeys to retest. Compare the contributions of support, development, project management and communication. The incident response guide describes the steps.

    In a portfolio, state your exact role, constraints, failed trials and changes after feedback. These are simulations; do not present them as client commissions or professional experience you have gained.