Atendente – Lauro de Freitas – Ba – Vaga

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 by the snippet or provided fields.
  – Can use general/sector-appropriate language, but treat assumptions as natural descriptions, not confirmed facts.
  – Keep it truthful, professional, legible.
  – Portuguese (Brazil), no unnecessary anglicisms.
  – Target size: ~700 words.
  – Output ONLY the HTML description, no title, no intro, no code block markers.

  2. **Analyze the Input Data:**
  – **Cargo:** Atendente – Lauro de Freitas – BA – Vaga
  – **Empresa:** Divulga Vagas – Consultoria
  – **Localização:** Lauro de Freitas, Bahia
  – **Trecho original (truncado):**
  – Requisitos: Necessário possuir experiência na área
  – Escolaridade mínima: Não informado
  – Jornada de trabalho: Horário a combinar
  – Benefícios: A combinar

  3. **Identify What’s Allowed & What’s Not:**
  – **Not allowed to invent:** Specific salary, specific certifications, specific benefits beyond “a combinar”, specific years of experience, false requirements.
  – **Allowed to use:** General, standard language appropriate for the role (e.g., “experience in customer service”, “availability for shift scheduling”, etc.), but must be framed naturally and not as confirmed facts if not in the snippet. Actually, re-reading rule 2: “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 attendant duties in a general way, but must be careful not to state them as guaranteed requirements.
  – **Must keep:** The real info from the snippet: experience necessary, schooling not specified, schedule to combine, benefits to combine.
  – **Output format:** HTML only, using `

  ` and `

  /
  • `. No headings (so no `<h1`-`
    

    `), no markdown. Just the description text in HTML paragraphs and lists.

    4. **Determine the Structure of the HTML Output:**
    – I need to create a coherent, ~700 word HTML description using only `

    ` and `

    /
    • `.
      – Since no headings allowed, I’ll structure it as a continuous flow of paragraphs and lists, likely starting with the job title and company info embedded in paragraphs, then requirements, responsibilities, etc.
      – I need to be careful about word count: ~700 words in HTML format with only `

      ` and `

      /
      • ` tags. That’s a lot of text. I’ll need to expand naturally while staying truthful to the snippet.

        Let’s plan the content flow:
        – Paragraph introducing the vacancy: position, company, location.
        – Paragraph about the role’s general nature (attendant), using standard language but noting it’s based on typical duties for such a position in the region/company context, without inventing specifics.
        – List of requirements (from snippet): “Necessário possuir experiência na área” – I can expand this gently: “É esperado que o candidato tenha vivência na área, embora os detalhes exatos não tenham sido especificados.” But wait, rule 1 says NÃO invente fatos específicos. So I should keep it close to what’s there, maybe phrase it as “Entre os requisitos, destaca-se a necessidade de experiência na área” but that’s still adding. Better: stick to the exact text but wrap it in a paragraph, maybe add very general context that’s implied. Actually, I can say “Os requisitos listados incluem a necessidade de experiência na área” – that’s directly from the snippet, no invention.
        – List of schooling: “Não informado” – I can mention it’s not specified, maybe add “A escolaridade mínima não foi informada na divulgação.”
        – Work schedule: “Horário a combinar” – “A jornada de trabalho e o horário serão combinados durante o processo seletivo.”
        – Benefits: “A combinar” – “Os benefícios são a combinar.”
        – Maybe a general paragraph about the company or application process, but carefully. Since it’s “Divulga Vagas – Consultoria”, I can mention it’s a consultancy posting the vacancy, but not invent details.

        Word count target: ~700 words. That’s quite long for just `

        ` and `

        /
        • `. I need to generate substantial text while staying within constraints. I’ll need to be expansive but generic where allowed, and strictly factual where not.

          Let’s outline the HTML structure mentally:
          `

          …intro…

          `
          `

          • …requisito…
          • …escolaridade…
          • …jornada…
          • …beneficios…

          `
          `

          …responsibilities…

          `
          `

          …how to apply…

          `
          And so on, totaling ~700 words.

          Important: No headings. So I can’t use `

          ` or similar. Everything must be in `

          ` or `

          ` inside `

          `/`
          `.

          Let’s think about how to reach ~700 words with only those tags. I’ll write multiple paragraphs and list items. Each paragraph can be long (maybe 80-120 words). List items can also be descriptive. I need to count roughly.

          Let’s draft content carefully, ensuring I don’t invent specific requirements, salaries, certifications, etc. I’ll stick to what’s given and add very general, standard phrasing that’s appropriate but marked as general/implied.

          Constraints check:
          – “NÃO invente fatos específicos que não estejam implícitos” -> I will not mention salary, specific years of experience, specific certifications, exact benefits beyond “a combinar”.
          – “Você PODE usar linguagem geral e padrão do setor” -> I will describe the attendant role in general terms, e.g., “Atender clientes, manter o ambiente organizado, auxiliar em processos internos”, but I’ll frame them as typical possibilities, not as confirmed requirements from the snippet. Actually, I need to be careful: the snippet only says “Necessário possuir experiência na área”. I can expand on what “experiência na área” might entail in general for an attendant role, but I must not present it as a fact from the posting. I’ll use phrases like “Costumam ser esperadas atividades tais como…” but wait, that might be treating suppositions as facts. Better to keep it very close to the snippet, maybe just one paragraph describing the role generally, noting that details are to be confirmed.

          Actually, re-reading rule 2 carefully: “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.” This means I CAN include typical responsibilities, as long as I don’t present them as confirmed facts from the posting. So I can say something like “Para a função de atendente, são esperadas responsabilidades como atendimento ao cliente, organização do local e suporte administrativo, embora os detalhes exatos devam ser confirmados no processo seletivo.” That seems acceptable.

          But rule 1 says NÃO invente fatos específicos… So I won’t say “exige 6 meses de experiência” or “exige curso X”. I’ll keep it generic and vague where not specified.

          Let’s structure the HTML:

          I’ll create a single HTML block with paragraphs and lists. I need to output ONLY the HTML, no title, no intro message, no code block markers. So just raw HTML text.

          I’ll aim for about 700 words. Let’s draft carefully.

          Structure idea:
          – Paragraph 1: Job title, company, location (from given fields).
          – Paragraph 2: Brief about the vacancy, sourced from aggregator.
          – Ul list with requirements, schooling, schedule, benefits (all from snippet, maybe slightly expanded in general terms but clearly marked as per snippet).
          – Paragraph 3: General description of attendant duties (standard sector language, not specific).
          – Ul list or paragraph about application process (generic, not inventing specifics).
          – Maybe another paragraph about the company type (consultancy).

          Need to ensure total word count ~700. I’ll write and then count mentally/approximately.

          Let’s start drafting content in Portuguese, then convert to HTML structure.

          Drafting text (mental or scratchpad):

          “Vaga de Atendente em Lauro de Freitas, Bahia, divulgada pela consultoria Divulga Vagas. A oportunidade está aberta para candidatos que atendam aos critérios básicos descritos na publicação, com detalhes que ainda podem ser aprofundados durante o processo seletivo.”

          Then list:
          – Requisitos: Necessário possuir experiência na área (from snippet)
          – Escolaridade mínima: Não informado
          – Jornada de trabalho: Horário a combinar
          – Benefícios: A combinar

          • Empresa: Divulga Vagas – Consultoria
          • Localização: Lauro de Freitas, Bahia
          • Categoria da Vaga: Unknown
          • Tags da Vaga: Lauro de Freitas