Here’s a thinking process:

1. **Analyze the Request:**
– Role: Professional job ad writer in Brazilian Portuguese
– Input: Truncated job snippet for “Atendente De Vendas – Recrutamento Aberto”
– Output: Complete job description in clean HTML (only `

` and `

`/`
• `, no headings, no markdown)
  – Constraints:
  – Don’t invent specific facts not implied in the snippet or given fields
  – Can use general/sector-appropriate language naturally, but don’t treat assumptions as confirmed facts
  – Keep it truthful, professional, legible
  – Portuguese from Brazil, no unnecessary anglicisms
  – Target ~700 words
  – Output ONLY the HTML, no title, no intro, no code block markers

  2. **Analyze the Input Data:**
  – Cargo: Atendente De Vendas – Recrutamento Aberto
  – Localização: Salvador, Bahia
  – Salário: R$12,540 – R$12,540 / year (note: this seems like a yearly amount, but the truncated benefits say R$ 1.045,00 – there’s a discrepancy. I must not invent or resolve this beyond what’s given. I’ll note the salary as stated, but carefully. Actually, the snippet says “Salário: R$12,540 – R$12,540 / year” and then “Benefícios: Salário: R$ 1.045,00”. This is contradictory/confusing. I need to handle this carefully. The rule says: “NÃO invente fatos específicos que não estejam implícitos… sem valores de salário fabricados além do que foi informado”. I should not harmonize or “fix” the salary. I’ll refer to what’s given, but since it’s contradictory, I’ll likely just mention the salary range as stated in the cargo field, or the benefits salary. Actually, the cargo field says “R$12,540 – R$12,540 / year”, benefits say “Salário: R$ 1.045,00”. This is likely a data error in the source. I must not invent a consistent salary. I’ll treat them as separate data points but avoid creating a coherent salary structure that wasn’t there. I’ll probably just mention the salary as per the cargo description, or the benefits amount, but carefully. Let’s re-read: “Salário: R$12,540 – R$12,540 / year” is under “Dados da vaga”. “Benefícios: Salário: R$ 1.045,00” is in the truncated text. I think the safest is to mention the salary range as given in the official data field, and the benefits as VT, VR, etc. I’ll avoid stating a monthly salary that contradicts the yearly one. I’ll just say “Remuneração compatível com o mercado” or just reference the given range without harmonizing. Actually, the rule says “sem valores de salário fabricados além do que foi informado”. So I can include the salary info, but I must not change or “fix” it. I’ll include it as is, maybe phrase it carefully. Let’s look at the truncated text again: “BENEFÍCIOS: Salário: R$ 1.045,00 Benefícios: VT VR”. This suggests the salary in benefits is 1045. The cargo field says 12540/year. 12540 / 12 = 1045. So it’s the same amount, just expressed differently (monthly vs yearly). I should not point this out as a discovery, just naturally mention the remuneration. I’ll use the yearly figure as primary, or just say “R$ 1.045,00 mensais” or “R$ 12.540,00 anuais” – but I need to be careful not to invent. Since both are in the input, I can reference the amount. I’ll just say “Remuneração de R$ 1.045,00 (compatível com o informado)” or just list the benefits as VT, VR, and mention the salary as per the data. Actually, to stay safe and follow the rules, I’ll include the salary range as given in the “Dados da vaga” field, and the benefits as VT and VR, without creating a combined narrative that implies I resolved the discrepancy. I’ll just say “Salário: R$ 12.540,00 / ano” or “Benefícios incluem VT e VR”. I need to be natural but not factualize beyond what’s there.

  – Atribuições: “Responsável pela abertura e fechamento de caixa, atendimento ao cliente, ee demais atividades pertinentes a função.” (ee likely means “e outras” – other tasks)
  – Requisitos: “Ensino Médio Completo Necessário possuir experiência em vendas Desejável ter conhecimento e habilidade com Informática básica Desejável ter conhecimento em sistema de vendas”
  – Jornada: “Horário a combinar”
  – Benefícios: “Salário: R$ 1.045,00 Benefícios: VT VR” (and maybe more, but truncated)
  – Note: “Vaga aberta e verificada pelo portal Buscar Vagas em parceria com o site Divulg…”

  I need to expand this into a full job description, ~700 words, using only `

  ` and `

  `/`
  • `, no headings, no markdown. So the HTML should be a single block or sequence of paragraphs and lists. No `
    

    `, `

    `, etc. The prompt says: “use only

    and

    /
    • , without headings, without markdown”. So I can have `

      ` tags and `

      • ` lists, but no headings. I need to structure it naturally with paragraphs and lists.

        Let’s plan the structure:
        – Opening paragraph about the company/role (but I must not invent company name or specifics not given. I can use generic professional language.)
        – Responsibilities section as a list
        – Requirements section as a list
        – Work schedule/arrangement
        – Benefits
        – Additional info (location, etc.)

        I need to be careful not to invent. I can use standard phrasing for “Atendente de Vendas” responsibilities, but framed as general/standard, not as confirmed facts from the snippet. The rule says: “Você PODE usar linguagem geral e padrão do setor, apropriada 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 duties of a sales attendant, but phrase it carefully, e.g., “Entre as atividades, o profissional pode estar envolvido em…” or “As responsabilidades incluem…” but without claiming it’s exactly what the snippet says, or I can integrate the snippet’s exact words but expand naturally.

        Actually, the safest is to interleave the given data with general sector language, ensuring I don’t invent years of experience, specific certifications, etc. The snippet says “Necessário possuir experiência em vendas” – I should not invent a specific number of years. I’ll just say “experiência em vendas” as given, maybe phrase it as “experiência na área” without specifying duration.

        Let’s outline the HTML content in Portuguese, ~700 words. I need to count words mentally or aim for length. I’ll write extended paragraphs and lists.

        Structure plan:

        … introductory paragraph about the opportunity …

        • … responsibility 1 …
        • … responsibility 2 …

        … maybe 5-7 li items

        … requirements paragraph …

        • … requirement 1 …
        • … requirement 2 …

        …

        … schedule …

        • … benefit 1 …
        • … benefit 2 …

        …

        … location and additional info …

        I need to ensure ~700 words. That’s quite long for just HTML tags, but doable with descriptive paragraphs. I’ll aim for maybe 6-8 paragraphs of ~80-100 words each, plus lists. Total ~700.

        Let’s draft carefully in Portuguese, keeping it professional, natural, no headings.

        Important: Output ONLY the HTML, no title, no introduction text outside HTML, no markdown formatting like “`html. The prompt says: “Produza SOMENTE o HTML da descrição, nada além disso (sem título, sem introdução, sem marcação de bloco de código).” So I will output just the HTML content, starting directly with `

        ` or whatever.

        Let’s draft the content. I need to integrate the given data:
        – Cargo: Atendente De Vendas – Recrutamento Aberto
        – Localização: Salvador, Bahia
        – Salário: R$12,540 – R$12,540 / year (I’ll use the yearly figure, or the monthly 1045, but I’ll reference the amount as given. Since both appear, I’ll say “Remuneração

        • Empresa: Vagas de Emprego Bahia
        • Localização: Salvador, Bahia
        • Salário: R,540 – R,540 / year
        • Categoria da Vaga: Unknown
        • Tags da Vaga: Salvador