for intro paragraphs and general text,

for section headers (Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). The job description includes many sections. We need to map them. We need to keep all original content word-for-word, no changes. So we must copy exactly the text as given, preserving punctuation, line breaks, etc. But we need to wrap paragraphs in

. Also list items in

• . Section headers must be

  . The given description uses

  ,

  , , , etc. We need to convert to

  for section headers. Which sections are present? Let's identify: - "Contexte:" is a header? It is

  Contexte:

  . That's a section header. Should be

  Contexte:

  maybe include the colon. Keep original content word-for-word, but we need to wrap in

  . The original text includes the etc. We need to preserve content exactly, but we can't keep the HTML tags. The rule: "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That means we must keep the text exactly as in the description, not modify words. However we can wrap with

  tags, which adds tags but not change words. The content inside must be exactly as original. The original header text is "Contexte:" (including colon). The surrounding tags are not part of content. So we need to output

  Contexte:

  . But does that preserve the original content? The original includes Contexte:. The words are "Contexte:". So we need to keep that phrase exactly. So

  Contexte:

  is fine. - "Résumé du poste :" is Résumé du poste :. That's a header maybe "Résumé du poste". Should be

  Résumé du poste

  (maybe include colon?). The original includes colon after "poste". The phrase is "Résumé du poste :". So we need to keep colon. So

  Résumé du poste :

  . - "Responsabilités :" is Responsabilités :. So

  Responsabilités :

  . - "Résolution de problèmes et impact :" is Résolution de problèmes et impact :. So

  Résolution de problèmes et impact :

  . - "Supervision exercée/reçue :" is Supervision exercée/reçue :. So

  Supervision exercée/reçue :

  . - "Formation :" is Formation :. So

  Formation :

  . - "Expérience :" is Expérience :. So

  Expérience :

  . - "Exigences physiques habituelles :" is Exigences physiques habituelles :. So

  Exigences physiques habituelles :

  . - "Technologies à utiliser :" is Technologies à utiliser :. So

  Technologies à utiliser :

  . - "The expected hiring salary range..." is a paragraph with bold. Not a header but maybe we treat as content. No specific header required, but maybe "Key Duties" etc. The description includes "Key Duties" maybe not. There's "Comment postuler" maybe not. There's "How to Apply" maybe not present. The description includes "Résumé du poste" which is about duties. There's also "Contexte". There's no explicit "Qualifications" header but there is "Exigences" etc. The instructions say use

  for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role). So we need to map the sections accordingly. Let's map: - "Contexte" -> maybe "About the Role" or "About the Role"? Not exactly. But we can treat "Contexte" as "About the Role". However the instruction says use

  for section headers like Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. So we need to ensure we have appropriate headers for each major section. The description includes: 1. "Contexte" (Context) – could be "About the Role" or maybe "About the Role" is more about description. But we can treat "Contexte" as "About the Role". However there is also "Résumé du poste" which is also about role. Might be redundant. Let's see the mapping: - "Résumé du poste" – maybe "About the Role". So we can use

  About the Role

  but we need to keep original content word-for-word. The original header text is "Résumé du poste :". That is not "About the Role". The instruction says we must use

  for section headers, but also preserve original content word-for-word. So we cannot rename the header; we must keep the exact text. So we need to use

  Résumé du poste :

  (since that's the original header). That satisfies both: it's a section header and uses original text. Similarly, "Responsabilités :" ->

  Responsabilités :

  . "Résolution de problèmes et impact :" ->

  Résolution de problèmes et impact :

  . "Supervision exercée/reçue :" ->

  Supervision exercée/reçue :

  . "Formation :" ->

  Formation :

  . "Expérience :" ->

  Expérience :

  . "Exigences physiques habituelles :" ->

  Exigences physiques habituelles :

  . "Technologies à utiliser :" ->

  Technologies à utiliser :

  . "Résumé du poste" maybe also "Key Duties"? But we have "Responsabilités" which is duties. So "Résumé du poste" could be "About the Role". But we keep original header. Now we need to ensure we have

  for introductory paragraphs and general text. The description starts with

  ... then

  Intitulé du poste... then

  Lieu... then
  etc. We need to convert to

  tags for each paragraph. Also list items need

  • . We must be careful to preserve all original content word-for-word, including spaces, line breaks, special characters. However we cannot keep
    tags; we need to replace them with

    or just separate paragraphs. The description includes many
    tags. We need to treat each

    as a paragraph. Also there are
    tags that separate paragraphs; we need to ensure we have appropriate

    tags. Let's parse the description sequentially: 1.

    Avis de Recrutement

    – This is a title, not a section header defined. The rules say use

    for section headers like Responsibilities, etc. The title is not a section header; maybe we treat it as a header but not required. However we must not add any new tags beyond allowed. The title is not a section header; but we can keep it as is? The rule: "Use

    for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". The title is not among those; but we could treat it as a header maybe

    but not allowed? The rule says use

    for section headers, but doesn't forbid other headings. However we must not add any tags beyond allowed. The allowed tags are

    ,

    ,

    ,
    • . No

      ,

      , etc. So we cannot use

      . The title is currently

      . We need to convert to something allowed. Since it's not a section header defined, maybe we treat it as a paragraph? But it's a title. The instruction says "If text has no clear sections, just wrap paragraphs in

      tags". The title is a line; maybe we can treat it as a paragraph? But it's a heading. However we cannot use

      . So maybe we wrap the title text in

      . But that would lose the heading semantics. However the rule says "Use

      for section headers". The title is not a section header; it's a page title. So we could treat it as a paragraph:

      Avis de Recrutement

      . But we need to preserve the content word-for-word, including the underline tags. The original text includes Avis de Recrutement . The words are "Avis de Recrutement ". There's a trailing space. Should we keep that space? Probably yes, preserve exactly. So we need to extract the text inside the tags, including the space? The text is "Avis de Recrutement ". There's a space after "Recrutement". We need to keep that exactly. However we cannot keep the tags. So we need to output

      Avis de Recrutement

      . That includes the trailing space. Might be okay. But maybe we can keep the title as a paragraph, but the rule says "Use

      for introductory paragraphs and general text". The title is not a paragraph but we can treat it as a paragraph. Let's go through the whole text and decide how to structure. Full text (including line breaks) as given:

      Avis de Recrutement

      Intitulé du poste : Assistant(e) de programme, STRIDES SÉNÉGAL

      Lieu : Dakar, Sénégal

      
      

      Contexte:

      FHI 360 est une organisation à but non lucratif dédiée au développement humain, qui oeuvre à améliorer durablement les conditions de vie en promouvant des solutions intégrées et portées par les acteurs locaux. Notre équipe compte des experts dans les domaines de la santé, des menaces pour la santé publique, de l’éducation, de la nutrition, de l’environnement, du développement économique, de la jeunesse, de la recherche, de la technologie, de la communication et du marketing social, créant ainsi une combinaison unique de compétences pour relever les défis de développement interdépendants d’aujourd’hui.

       

      Résumé du poste :

      L’assistant(e) de programme du projet STRIDES (STRengthening Infectious disease DEtection Systems) au Sénégal est principalement chargé(e) d’apporter un soutien logistique, programmatique, opérationnel et administratif au projet. Il/elle travaillera avec le directeur du projet STRIDES Sénégal et ses collègues sur le terrain pour assurer la mise en place, la mise en œuvre et le bon fonctionnement des programmes nationaux, ainsi que le suivi et le reporting continus de ces programmes. Il/elle prépare des documents et des rapports, utilise les outils bureautiques, compile des données, organise et gère les dossiers, publie des informations et apporte son aide à ses collègues. L’assistant(e) de programme collecte et vérifie les données, synthétise et recoupe les informations, et coordonne et assure la gestion des archives. Il/elle constitue la principale ressource d’assistance pour le projet.

      
      

      Responsabilités :

      • Assiste le personnel chargé des programmes dans le traitement des demandes émanant des équipes régionales, du siège et d’autres membres du personnel.
      • Coordonne les visites techniques, les autorisations de déplacement, les notes de frais, les paiements et les contrats afin de soutenir la mise en œuvre des programmes nationaux.
      • Élabore des projets de budgets d’activités conformément aux termes de référence approuvés.
      • Apporte son soutien à la révision des rapports trimestriels et organise les réunions téléphoniques consacrées à ces rapports.
      • Apporte son soutien aux achats et assure le suivi des dépenses liées aux activités, selon les besoins.
      • Planifie et participe aux réunions téléphoniques régulières avec les pays, prend des notes et assure le suivi des actions à mener.
      • Gère les bases de données, les fichiers internes partagés, ainsi que l’intégrité et la sécurité des données, conformément aux normes de qualité et à la politique de l’entreprise.
      • Effectuer les tâches quotidiennes de manière autonome et de sa propre initiative.
      • Prépare des documents, des rapports et des supports d’information destinés aux consultants, au personnel et aux bailleurs de fonds.
      • Participe à l’intégration et à la formation des nouveaux membres du personnel administratif et de soutien.
      • Effectue des tâches techniques de base liées au programme, telles que la révision des plans de travail.
      • S'assure que la documentation et les rapports font l'objet d'un suivi régulier et respectent les normes nationales et régionales.
      • Effectue d’autres tâches connexes qui lui sont confiées.

      
      

      Résolution de problèmes et impact :

      • Traite des problèmes de nature courante relevant des procédures et politiques standard.
      • Travaille de manière autonome et au sein d’une équipe sur des projets ou programmes spéciaux, ponctuels ou récurrents.
      • Fait preuve de discernement dans le cadre de pratiques et de politiques définies pour s’acquitter de ses tâches.
      • Les décisions prises ont généralement une incidence sur son propre poste ou sur un domaine fonctionnel spécifique.

      
      

      Supervision exercée/reçue :

      • N’a aucune responsabilité de supervision.
      • Fait preuve d’autonomie de jugement pour déterminer l’organisation du travail et les priorités.
      • Reçoit des instructions concernant les nouvelles missions.
      • Relève du directeur de projet pour le Sénégal, STRIDES.

      
      

      Formation :

      Au minimum un diplôme de niveau bac +2 (ou son équivalent international) en services de la connaissance/de l’information, en communication, en éducation, en santé, en sciences du comportement, en sciences de la vie et sciences sociales, en développement international, en développement humain ou dans un domaine connexe ; un diplôme de niveau bac +4 est préférable.

      
      

      Expérience :     

      • Généralement, 0 à 2 ans d’expérience dans le domaine des programmes et du soutien administratif sont requis.    
      • Exprimé clairement, professionnel et capable de communiquer de manière claire et positive avec les clients et le personnel.    
      • Doit être capable de lire, d'écrire et de parler couramment le français ; une maîtrise professionnelle de l'anglais est souhaitée.      
      • Une expérience préalable au sein d’une organisation non gouvernementale (ONG) est un atout.

      
      

      Exigences physiques habituelles :

      • Environnement de bureau classique.
      • Capacité à passer de longues heures devant un écran d’ordinateur et à effectuer des tâches répétitives au clavier.
      • Capacité à rester assis et debout pendant de longues périodes.
      • Capacité à soulever/déplacer jusqu’à 2,5 kg.

      
      

      Technologies à utiliser :

      Ordinateur de bureau/portable, applications Microsoft (c'est-à-dire Office 365, SharePoint, Skype/Zoom/Teams), téléphone portable/technologies mobiles et matériel de bureau standard.

      
      
      

      The expected hiring salary range for this role is XOF 9,400,000 - 11,000,000 for annual basic salary. When determining an offer amount, FHI 360 factors in multiple considerations, including but not limited to: relevant years of experience and education possessed by the applicant, internal equity, market pay, and budget.  For internal candidates, salary placement will also follow FHI 360’s current promotional increase guidelines.

      
      

      This job posting summarizes the main duties of the job. It neither prescribes nor restricts the exact tasks that may be assigned to carry out these duties. This document should not be construed in any way to represent a contract of employment. Management reserves the right to review and revise this document at any time.

      
      

      FHI 360 is an equal opportunity employer whereby we do not engage in practices that discriminate against any person employed or seeking employment based on race, color, religion, sex, sexual orientation, gender identity, national or ethnic origin, age, marital status, physical or mental disability, protected Veteran status, or any other characteristic protected under applicable law.

      
      

      Our values and commitments to safeguarding: FHI 360 is committed to preventing any type of abuse, exploitation and harassment in our work environments and programs, including sexual abuse, exploitation and harassment. FHI 360 takes steps to safeguard the welfare of everyone who engages with our organization and programs and requires that all personnel, including staff members and volunteers, share this commitment and sign our code of conduct. All offers of employment will be subject to appropriate screening checks, including reference, criminal record and terrorism finance checks. FHI 360 also participates in the Inter-Agency Misconduct Disclosure Scheme (MDS), facilitated by the Steering Committee for Humanitarian Response. In line with the MDS, we will request information from job applicants’ previous employers about any substantiated findings of sexual abuse, exploitation and/or harassment during the applicant’s tenure with previous employers. By applying, job applicants confirm their understanding of these recruitment procedures and consent to these screening checks.

      
      

      FHI 360 will consider for employment all qualified applicants, including those with criminal histories, in a manner consistent with the requirements of applicable state and local laws.

      
      

      FHI 360 will never ask you for your career site username or password, and we will never request money, goods or services during the application, recruitment or employment  process. If you have questions or concerns about correspondence from us, please email CareerCenterSupport@fhi360.org.
      
      FHI 360 fosters the strength and health of its workforce through a competitive benefits package, professional development and policies and programs that support a healthy work/life balance. Join our global workforce to make a positive difference for others — and yourself.

      
      

      Please click here to continue searching FHI 360's Career Portal.
       

      Now we need to convert to HTML with allowed tags. We need to ensure we have

      for each section header. Let's list sections: - Title: "Avis de Recrutement " (maybe not a section header; but we can treat as

      because not a section header defined. However we could also treat as

      but that would be adding a new header not in list. The rule says "Use

      for section headers (e.g. Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role)". The title is not among those, so we should not use

      . So we will wrap it in

      . - "Contexte:" is a header; we need

      Contexte:

      . But the original includes Contexte:. The words are "Contexte:". So we output

      Contexte:

      . - "Résumé du poste :" is a header; we need

      Résumé du poste :

      . - "Responsabilités :" header;

      Responsabilités :

      . - "Résolution de problèmes et impact :" header;

      Résolution de problèmes et impact :

      . - "Supervision exercée/reçue :" header;

      Supervision exercée/reçue :

      . - "Formation :" header;

      Formation :

      . - "Expérience :" header;

      Expérience :

      . - "Exigences physiques habituelles :" header;

      Exigences physiques habituelles :

      . - "Technologies à utiliser :" header;

      Technologies à utiliser :

      . Potential other sections: maybe "Intitulé du poste" and "Lieu" are not section headers but could be considered part of the job description. They are not in the list of allowed headers, but we can keep them as

      . The instruction says "If text has no clear sections, just wrap paragraphs in

      tags". So we can treat "Intitulé du poste : Assistant(e) de programme, STRIDES SÉNÉGAL" as a paragraph. Similarly "Lieu : Dakar, Sénégal". Also the salary paragraph is a paragraph. Now we need to ensure we preserve all original content word-for-word. That includes special characters like + which is HTML entity for plus sign. We must keep them exactly as they appear. Also we must keep the spaces, line breaks (but we will not include
      tags; we will just have separate

      elements). The original includes many
      tags; we need to replace them with appropriate

      tags. We need to be careful to not lose any content. For example, the paragraph after "Contexte:" includes a lot of text. We need to keep it exactly. Also note that there are some empty paragraphs (

       

      ) which contain just a non-breaking space. We need to preserve them? The instruction says preserve all original content word-for-word. An empty paragraph with a space might be considered content. But we can keep it as

       

      (the space). However we need to ensure we don't add extra spaces. The original includes a space character (maybe a non-breaking space). We'll just include a space inside the

      tags. Now we need to map each paragraph to

      . Let's go step by step. 1. Title:

      Avis de Recrutement

      -> we need to output

      Avis de Recrutement

      . Keep the trailing space. 2. "Intitulé du poste : Assistant(e) de programme, STRIDES SÉNÉGAL" ->

      Intitulé du poste : Assistant(e) de programme, STRIDES SÉNÉGAL

      3. "Lieu : Dakar, Sénégal" ->

      Lieu : Dakar, Sénégal

      4. Then

      Contexte:

      -> we need

      Contexte:

      5. Paragraph after that: "FHI 360 est une organisation à but non lucratif..." ->

      FHI 360 est une organisation à but non lucratif dédiée au développement humain, qui oeuvre à améliorer durablement les conditions de vie en promouvant des solutions intégrées et portées par les acteurs locaux. Notre équipe compte des experts dans les domaines de la santé, des menaces pour la santé publique, de l’éducation, de la nutrition, de l’environnement, du développement économique, de la jeunesse, de la recherche, de la technologie, de la communication et du marketing social, créant ainsi une combinaison unique de compétences pour relever les défis de développement interdépendants d’aujourd’hui.

      6. Then

       

      (empty). We'll keep

       

      (space). Might be okay. 7. Résumé du poste : ->

      Résumé du poste :

      8. Paragraph after that: "L’assistant(e) de programme du projet STRIDES (STRengthening Infectious disease DEtection Systems) au Sénégal est principalement chargé(e) d’apporter un soutien logistique, programmatique, opérationnel et administratif au projet. Il/elle travaillera avec le directeur du projet STRIDES Sénégal et ses collègues sur le terrain pour assurer la mise en place, la mise en œuvre et le bon fonctionnement des programmes nationaux, ainsi que le suivi et le reporting continus de ces programmes. Il/elle prépare des documents et des rapports, utilise les outils bureautiques, compile des données, organise et gère les dossiers, publie des informations et apporte son aide à ses collègues. L’assistant(e) de programme collecte et vérifie les données, synthétise et recoupe les informations, et coordonne et assure la gestion des archives. Il/elle constitue la principale ressource d’assistance pour le projet." We need to wrap each sentence? The instruction: Use

      for introductory paragraphs and general text. So we can keep the whole paragraph as one

      . That's fine. 9.
      

      Responsabilités :

      ->

      Responsabilités :

      then the list. But note there is a

      before the list. The original has

      Responsabilités :

      . So we need to output

      Responsabilités :

      then the

      list. The

      tag is not needed because we have a header; but we can just put the header directly before the

      . However we need to preserve the content. The header text is "Responsabilités :". So we output

      Responsabilités :

      then
      ...list items...
      . No extra

      . But we need to ensure we keep the list items exactly as they appear, including punctuation and spaces. The list items are within

      • tags. We'll copy them exactly. 10. After the list, there is
        

        ... maybe a paragraph? Actually after the list, there is
        

        Résolution de problèmes et impact :

        . So we need

        Résolution de problèmes et impact :

        then another
        list. 11. Then
        

        Supervision exercée/reçue :

        ->

        Supervision exercée/reçue :

        then
        list. 12. Then

        Formation :

        ->

        Formation :

        then a

        containing the education details. So we need to keep that as

        text. 13. Then

        Expérience :     

        ->

        Expérience :

        then
        list. 14. Then

        Exigences physiques habituelles :

        ->

        Exigences physiques habituelles :

        then
        list. 15. Then

        Technologies à utiliser :

        ->

        Technologies à utiliser :

        then a

        with technologies text. 16. Then
        
        

        The expected hiring salary range ...

        -> This is a paragraph with bold. We need to keep it as

        text. The content includes ... . We need to preserve the formatting? The instruction says preserve all original content word-for-word, including tags? It says "Preserve ALL original content word-for-word — do not add, remove, summarise, or rephrase". That includes the HTML tags? The original includes ... . We need to preserve that exactly. However we are only allowed to use

        ,

        ,

        ,
        • . We cannot keep or tags because they are not allowed. But we must preserve content word-for-word, which includes the tags? The instruction ambiguous: "Preserve ALL original content word-for-word". That likely means the textual content, not the markup. But we cannot use or tags, so we need to remove them but keep the text. However the text includes the words "The expected hiring salary range for this role is XOF 9,400,000 - 11,000,000 for annual basic salary. When determining an offer amount, FHI 360 factors in multiple considerations, including but not limited to: relevant years of experience and education possessed by the applicant, internal equity, market pay, and budget.  For internal candidates, salary placement will also follow FHI 360’s current promotional increase guidelines." The original had around it. We need to preserve the text exactly, but we cannot keep the tags. So we will output the paragraph as

          The expected hiring salary range for this role is XOF 9,400,000 - 11,000,000 for annual basic salary. When determining an offer amount, FHI 360 factors in multiple considerations, including but not limited to: relevant years of experience and education possessed by the applicant, internal equity, market pay, and budget.  For internal candidates, salary placement will also follow FHI 360’s current promotional increase guidelines.

          . We need to keep the non-breaking spaces? The original includes   maybe. We'll just keep spaces. 17. Then

          This job posting summarizes the main duties of the job... etc. ->

          This job posting summarizes the main duties of the job. It neither prescribes nor restricts the exact tasks that may be assigned to carry out these duties. This document should not be construed in any way to represent a contract of employment. Management reserves the right to review and revise this document at any time.

          18. Then

          FHI 360 is an equal opportunity employer ... -> This includes an anchor tag. The instruction says "Do not add any commentary, headers, etc." But we can keep the anchor tag as is because it's part of the content. However the allowed tags are only

          ,

          ,

          ,
          • . The anchor tag is not allowed. But the content includes an HTML anchor. The instruction says "Use

            for introductory paragraphs and general text". It doesn't forbid other tags, but the rules say "No CSS classes, no inline styles, no

            s, no
            tags". It doesn't forbid tags. However the allowed tags list is limited, but maybe we can keep because it's part of the content. The instruction says "Use

            for introductory paragraphs and general text" and "Use

            for section headers" and "Use

            • for list items". It doesn't explicitly forbid tags, but the overall rule says "No CSS classes, no inline styles, no
              s, no
              tags". So is allowed. However the content includes . That's okay. But we need to preserve the text exactly, including the anchor tag. However we cannot embed the anchor tag inside

              because that would be mixing tags. The anchor is part of the paragraph content. We can keep the anchor tag as part of the paragraph text. For example:

              FHI 360 is an equal opportunity employer whereby we do not engage in practices that discriminate ...

              . That's fine. Similarly later there is another anchor: CareerCenterSupport@fhi360.org. We'll keep that. Also there is another anchor: competitive benefits package. Keep as is. And another anchor: here. Keep. Now we need to ensure we have

              for each section header. Let's map all sections: - Title: not a section header, so

              . - "Intitulé du poste" and "Lieu" are not section headers; they are just info lines. We'll keep as

              . - "Contexte:" ->

              Contexte:

              - "Résumé du poste :" ->

              Résumé du poste :

              - "Responsabilités :" ->

              Responsabilités :

              - "Résolution de problèmes et impact :" ->

              Résolution de problèmes et impact :

              - "Supervision exercée/reçue :" ->

              Supervision exercée/reçue :

              - "Formation :" ->

              Formation :

              - "Expérience :" ->

              Expérience :

              - "Exigences physiques habituelles :" ->

              Exigences physiques habituelles :

              - "Technologies à utiliser :" ->

              Technologies à utiliser :

              Potential other sections: maybe "The expected hiring salary range..." is not a header but we can keep as paragraph. Now we need to ensure we have

              • for list items. The list items are already in
                tags in the original. We'll keep them as is, but we need to ensure they are inside
                tags. The original already has
                ...
                • ...
                ...
                . So we just need to keep them. But we need to ensure that each list is preceded by the appropriate

                header. Also we need to ensure that we don't have stray

                tags that contain only the header text. For example, after "Responsabilités :" there is a

                containing the Responsabilités :. We need to replace that with

                Responsabilités :

                and then the
                . So we need to remove the

                wrapper and the inner tags. So we will output:

                Responsabilités :

                ... list items ...
                Similarly for other sections. Now we need to ensure we preserve all original content word-for-word. That includes the spaces after colons, the special characters, the non-breaking spaces, etc. We must be careful not to alter any text. Let's rewrite step by step, ensuring we keep everything. First part:

                Avis de Recrutement

                (title). Actually the original had around it, but we remove that. Keep the trailing space. Then:

                Intitulé du poste : Assistant(e) de programme, STRIDES SÉNÉGAL

                Lieu : Dakar, Sénégal

                Now the "Contexte:" header:

                Contexte:

                FHI 360 est une organisation à but non lucratif dédiée au développement humain, qui oeuvre à améliorer durablement les conditions de vie en promouvant des solutions intégrées et portées par les acteurs locaux. Notre équipe compte des experts dans les domaines de la santé, des menaces pour la santé publique, de l’éducation, de la nutrition, de l’environnement, du développement économique, de la jeunesse, de la recherche, de la technologie, de la communication et du marketing social, créant ainsi une combinaison unique de compétences pour relever les défis de développement interdépendants d’aujourd’hui.

                Then an empty paragraph:

                 

                (space). Keep it. Now "Résumé du poste :" header:

                Résumé du poste :

                L’assistant(e) de programme du projet STRIDES (STRengthening Infectious disease DEtection Systems) au Sénégal est principalement chargé(e) d’apporter un soutien logistique, programmatique, opérationnel et administratif au projet. Il/elle travaillera avec le directeur du projet STRIDES Sénégal et ses collègues sur le terrain pour assurer la mise en place, la mise en œuvre et le bon fonctionnement des programmes nationaux, ainsi que le suivi et le reporting continus de ces programmes. Il/elle prépare des documents et des rapports, utilise les outils bureautiques, compile des données, organise et gère les dossiers, publie des informations et apporte son aide à ses collègues. L’assistant(e) de programme collecte et vérifie les données, synthétise et recoupe les informations, et coordonne et assure la gestion des archives. Il/elle constitue la principale ressource d’assistance pour le projet.

                Now "Responsabilités :" header:

                Responsabilités :

                • Assiste le personnel chargé des programmes dans le traitement des demandes émanant des équipes régionales, du siège et d’autres membres du personnel.
                • Coordonne les visites techniques, les autorisations de déplacement, les notes de frais, les paiements et les contrats afin de soutenir la mise en œuvre des programmes nationaux.
                • Élabore des projets de budgets d’activités conformément aux termes de référence approuvés.
                • Apporte son soutien à la révision des rapports trimestriels et organise les réunions téléphoniques consacrées à ces rapports.
                • Apporte son soutien aux achats et assure le suivi des dépenses liées aux activités, selon les besoins.
                • Planifie et participe aux réunions téléphoniques régulières avec les pays, prend des notes et assure le suivi des actions à mener.
                • Gère les bases de données, les fichiers internes partagés, ainsi que l’intégrité et la sécurité des données, conformément aux normes de qualité et à la politique de l’entreprise.
                • Effectuer les tâches quotidiennes de manière autonome et de sa propre initiative.
                • Prépare des documents, des rapports et des supports d’information destinés aux consultants, au personnel et aux bailleurs de fonds.
                • Participe à l’intégration et à la formation des nouveaux membres du personnel administratif et de soutien.
                • Effectue des tâches techniques de base liées au programme, telles que la révision des plans de travail.
                • S'assure que la documentation et les rapports available for for,,,,,,

            Translated by AI — may not be perfect

            Show original