COORDINATRICE
Anonymized
Role Overview
Here's a thinking process:
Analyze User Request:
Role:
Write job offer descriptions in French for a recruitment platform.
Output format:
Simple HTML compatible with CKEditor.
Constraints:
Paragraphs and lists only
No markdown
No main title
No invented information
Use only provided info
Structure: short intro, main missions, required profile, offer conditions
No coordinates, salary, or benefits not in the data
Analyze Provided Data:
Professional Info:
Name: SPA LA FLECHE BLEU ALGERIENNE
Company: SPA LA FLECHE BLEU ALGERIENNE
Role: Responsable de service
Sector: Services
Wilaya: 35
Size: 100 à 499 personnes
Website: (empty)
Offer Info:
Poste: COORDINATRICE
Date: 2026-08-01
Metier: Coordinatrice d'administration
Metier_id: 408
Wilaya: Boumerdès
Wilaya_id: 35
Commune: Corso
Commune_id: 350011
Type_contrat: CDD
Niveau_requis: Master1
Experience: 2 (presumably years)
Nombre_postes: 1
Visibilite: Normal
Notice:
There's a slight inconsistency: professional role says "Responsable de service", but offer says "COORDINATRICE" / "Coordinatrice d'administration". I should stick strictly to the offer info, as the user says "Utilise uniquement les informations fournies" and "Ne pas inventer". I'll use the offer details for the job description structure, but I need to be careful not to mix contradictory info unless it's clearly the same role. The structure expects: short intro, main missions, required profile, offer conditions. I'll map the offer fields accordingly.
Map to structure:
Short intro: Could include poste, metier, wilaya, commune, type_contrat, nombre_postes
Main missions: Not explicitly provided. I should not invent missions. The user says "Si une information manque, ne l invente pas." So I should either omit missions section or put placeholder that no missions are listed? But the structure expects "missions principales". I need to check if mission data is provided. It's not. I must not invent. I could write something like "Non spécifiées dans l'offre" but that might be considered invented? Better to simply not include content that isn't there, or use very generic phrasing based strictly on what's given. Wait, the user says "Structure attendue: courte introduction, missions principales, profil recherche, conditions de l offre." and "Utilise uniquement les informations fournies. Si une information manque, ne l invente pas." This means I should structure the output with those sections, but only fill with actual provided info. If missions aren't provided, I should either leave that section empty or put a note that it's not specified, but carefully. Actually, I think I can structure it with headings/paragraphs, but only put content that exists. Maybe I can derive missions from the role title "Coordinatrice d'administration" but that would be inferring. Better to strictly use only the given fields. I'll make the intro cover what's given, and for missions, I'll either omit the section or put a line saying "Non précisées". But the user might want the structure present. I'll include the section headings as HTML elements, but only fill with actual data. If data is missing, I'll leave the paragraph empty or with a minimal "Non spécifié" but that might be seen as invented. Let's re-read: "Retourne uniquement un HTML simple compatible CKEditor: paragraphes et listes, sans markdown, sans titre principal et sans informations inventees." "Structure attendue:
Analyze User Request:
Role:
Write job offer descriptions in French for a recruitment platform.
Output format:
Simple HTML compatible with CKEditor.
Constraints:
Paragraphs and lists only
No markdown
No main title
No invented information
Use only provided info
Structure: short intro, main missions, required profile, offer conditions
No coordinates, salary, or benefits not in the data
Analyze Provided Data:
Professional Info:
Name: SPA LA FLECHE BLEU ALGERIENNE
Company: SPA LA FLECHE BLEU ALGERIENNE
Role: Responsable de service
Sector: Services
Wilaya: 35
Size: 100 à 499 personnes
Website: (empty)
Offer Info:
Poste: COORDINATRICE
Date: 2026-08-01
Metier: Coordinatrice d'administration
Metier_id: 408
Wilaya: Boumerdès
Wilaya_id: 35
Commune: Corso
Commune_id: 350011
Type_contrat: CDD
Niveau_requis: Master1
Experience: 2 (presumably years)
Nombre_postes: 1
Visibilite: Normal
Notice:
There's a slight inconsistency: professional role says "Responsable de service", but offer says "COORDINATRICE" / "Coordinatrice d'administration". I should stick strictly to the offer info, as the user says "Utilise uniquement les informations fournies" and "Ne pas inventer". I'll use the offer details for the job description structure, but I need to be careful not to mix contradictory info unless it's clearly the same role. The structure expects: short intro, main missions, required profile, offer conditions. I'll map the offer fields accordingly.
Map to structure:
Short intro: Could include poste, metier, wilaya, commune, type_contrat, nombre_postes
Main missions: Not explicitly provided. I should not invent missions. The user says "Si une information manque, ne l invente pas." So I should either omit missions section or put placeholder that no missions are listed? But the structure expects "missions principales". I need to check if mission data is provided. It's not. I must not invent. I could write something like "Non spécifiées dans l'offre" but that might be considered invented? Better to simply not include content that isn't there, or use very generic phrasing based strictly on what's given. Wait, the user says "Structure attendue: courte introduction, missions principales, profil recherche, conditions de l offre." and "Utilise uniquement les informations fournies. Si une information manque, ne l invente pas." This means I should structure the output with those sections, but only fill with actual provided info. If missions aren't provided, I should either leave that section empty or put a note that it's not specified, but carefully. Actually, I think I can structure it with headings/paragraphs, but only put content that exists. Maybe I can derive missions from the role title "Coordinatrice d'administration" but that would be inferring. Better to strictly use only the given fields. I'll make the intro cover what's given, and for missions, I'll either omit the section or put a line saying "Non précisées". But the user might want the structure present. I'll include the section headings as HTML elements, but only fill with actual data. If data is missing, I'll leave the paragraph empty or with a minimal "Non spécifié" but that might be seen as invented. Let's re-read: "Retourne uniquement un HTML simple compatible CKEditor: paragraphes et listes, sans markdown, sans titre principal et sans informations inventees." "Structure attendue: