Here’s a thinking process:

1. **Analyze the Request:**
– **Role:** Professional job ad writer in Brazilian Portuguese
– **Task:** Expand a short, truncated job snippet into a complete, well-organized HTML description
– **Constraints:**
– Use only `

` and `

/
• ` tags (no headings, no markdown)
  – Do NOT invent specific facts not implied in the snippet or provided fields
  – CAN use general industry-standard language appropriate to the role, but treat suppositions as natural descriptions, not confirmed facts
  – Keep it truthful, professional, legible
  – Write entirely in Brazilian Portuguese, natural and clear, no unnecessary anglicisms
  – Target size: ~700 words
  – Output ONLY the HTML description, no title, no introduction, no code block markers

  2. **Analyze the Input Data:**
  – **Job Title:** Analista da Qualidade Pl. (Especializado em Equipamentos da Qualidade)
  – **Company:** Ardagh Group
  – **Location:** Alagoinhas, Bahia
  – **Contract:** CLT / Indeterminado (Com experiência de 90 dias)
  – **Schedule:** Administrativo
  – **Area:** Qualidade
  – **Manager:** Gerente da Qualidade
  – **Vacancies:** 01
  – **Pré-Requisitos (Requirements):**
  – Ensino Superior Completo (Desejável em Engenharia em Geral, Administração ou cursos correlatos)
  – Curso Técnico Completo (Eletrônica, automação, instrumentação ou mecatrônica)
  – Informática: Pacote office intermediário; E… (truncated)

  – **Missing/Implied info:**
  – The snippet ends with “E…”, so I shouldn’t invent what comes after.
  – I need to be careful not to fabricate salary, specific benefits, exact years of experience beyond what’s implied, etc.
  – I can use general, standard descriptions of the role’s responsibilities that are typical for a “Analista da Qualidade Pl” specialized in “Equipamentos da Qualidade” in the manufacturing/industrial context, but framed as general/standard, not as confirmed requirements unless implied.

  3. **Determine the Structure (HTML only, `

  ` and `

  /
  • `):**
    – I need to create a coherent, flowing description using paragraphs and lists.
    – No headings (`

    `-`

    `), no markdown (`**`, `*`, etc., though the constraint says “sem markdown”, I’ll just avoid markdown syntax entirely, use plain text within HTML tags).
    – The structure should be natural for a job ad: introduction/overview, responsibilities, requirements, benefits/conditions (but only what’s implied or standard, no fabrication), and maybe a closing.
    – Wait, constraint 5: “Tamanho alvo: aproximadamente 700 palavras.” That’s quite long for just HTML tags, but doable with thorough descriptions.
    – Constraint 2: “Você PODE usar linguagem geral e padrão do setor, apropriada ao cargo… desde que apresente isso de forma natural e não trate suposições como fatos confirmados.” So I can describe typical duties of such a role in general terms, but must clarify they’re standard/expected, not explicitly stated in the snippet.
    – Constraint 1: “NÃO invente fatos específicos que não estejam implícitos…” So no salary, no specific benefits not mentioned, no fake certifications, no invented experience years beyond “experiência de 90 dias” which is a probationary period mentioned in the contract.

    Let’s map what’s safely expandable:
    – Company: Ardagh Group (can mention it’s a global player in packaging, but cautiously, or just state the company name and location as given)
    – Location: Alagoinhas, Bahia
    – Contract: CLT, indeterminado, with 90-day experience period (probation)
    – Schedule: Administrative
    – Area: Quality
    – Manager: Quality Manager
    – Vacancies: 1
    – Requirements:
    – Complete Higher Education ( preferably Engineering, Administration, related fields)
    – Complete Technical Course ( Electronics, automation, instrumentation, mechatronics)
    – Intermediate Office package (Office suite)
    – Truncated part: “Informática: Pacote office intermediário; E…” -> I should stop before inventing the rest. I can mention “Pacote Office intermediário” as stated, and maybe general computer skills typical for the role, but carefully. Or I can just list what’s there and not add more IT specs.

    Actually, re-reading constraint 1: “NÃO invente fatos específicos que não estejam implícitos no trecho fornecido ou nos campos dados — sem valores de salário fabricados além do que foi informado, sem certificações falsas, sem benefícios inventados, sem exigências de anos de experiência inventadas.”
    The snippet says “Prazo do Contrato: CLT / Indeterminado (Com experiência de 90 dias)” – this likely means a 90-day probationary period. I can reference that.
    It also says “Pré-Requisitos: Ensino Superior Completo (Desejável em Engenharia em Geral, Administração ou cursos correlatos); Curso Técnico Completo (Eletrônica, automação, instrumentação ou mecatrônica); Informática: Pacote office intermediário; E…”
    I should not invent what “E…” contains. I’ll just list what’s explicitly there, and perhaps add a generic note about “Conhecimentos em informática básicos” but that might be inventing. Better to stick strictly to what’s given, and use general industry language for responsibilities that is framed as “typical duties for this role” but not as requirements. Wait, constraint 2 says: “Você PODE usar linguagem geral e padrão do setor, apropriado ao cargo (ex.: responsabilidades típicas de um ‘Operador de Empilhadeira’), desde que apresente isso de forma natural e não trate suposições como fatos confirmados.” So I can describe typical responsibilities, but I must frame them as general/standard, not as confirmed requirements from the snippet. I need to be careful with wording: use “geralmente responsáveis por” or “inclui atividades como” rather than “você irá”.

    Actually, the task is to expand the snippet into a complete description. A job ad typically has: overview, responsibilities, requirements, benefits/conditions. I need to generate ~700 words of HTML using only

    and

    /
    • . I must not use headings. So I’ll weave everything into paragraphs and lists without heading tags.

      Plan for HTML structure:
      – Use `

      ` for blocks of text.
      – Use `

      • ` for lists of requirements, responsibilities, etc.
        – No `

        `-`

        `, no markdown.
        – Keep it in Brazilian Portuguese.
        – Aim for ~700 words. That’s substantial. I’ll need to be descriptive but within the constraints.

        Let outline the content sections (as text within paragraphs/lists, no headings):
        1. Introduction: Job title, company, location, contract type, schedule, area, manager, vacancies.
        2. Responsibilities: Describe typical quality analyst duties specialized in equipment, using general industry language, framed as “atividades comuns” or “responsabilidades inerentes”, not explicitly from snippet but appropriate. I’ll be careful to say “entre as atividades esperadas” or “inclui” but actually, to stay safe, I should perhaps describe them as “atividades inerentes ao cargo de Analista da Qualidade com foco em equipamentos”, but framed generally. Wait, constraint 2 allows “linguagem geral e padrão do setor… desde que apresente isso de forma natural e não trate suposições como fatos confirmados.” So I can write something like “O profissional nesta posição costuma acompanhar o desempenho de equipamentos críticos, participar de auditorias de qualidade, registrar dados de produção, colaborar na definição de padrões de qualidade, entre outras funções típicas da área.” That’s general, not a fact from the snippet, but appropriate language.
        3. Requirements: List what’s explicitly given: Ensino Superior Completo (preferencialmente Engenharia, Administração, cursos correlatos), Curso Técnico Completo (Eletrônica, automação, instrumentação, mecatrônica), Informática Pacote Office intermediário. I’ll list these as `

        ` items. I won’t add “anos de experiência” since it’s not in the snippet, and constraint 1 forbids inventing that. The snippet only mentions “experiência de 90 dias” in the contract context, which is a probation period, not a requirement of years.
        4. Conditions/Benefits: Only what’s implied or standard but not fabricated. The snippet has “CLT / Indeterminado (Com experiência de 90 dias)” and “Escala: Administrativa”. I can mention the contract type, probation period, administrative schedule. I won’t invent health insurance, transport, etc., unless implied. I can safely mention “benefícios compatíveis com CLT” but that might be too generic/invented. Better to stick to what’s given: CLT, indeterminado, 90-day experience period, administrative scale. I’ll describe those as given.
        5. Closing/Application: Generic, but I need to be careful not to invent processes. I can say “Interessados

        • Empresa: Ardagh Group
        • Localização: Alagoinhas, Bahia
        • Categoria da Vaga: Unknown
        • Tags da Vaga: Alagoinhas