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 given fields.
  – CAN use general industry-standard language appropriate to the role, naturally, without treating assumptions as facts.
  – Keep text truthful, professional, legible.
  – Write entirely in Brazilian Portuguese, natural and clear, no unnecessary anglicisms.
  – Target length: ~700 words.
  – Output ONLY the HTML description, no title, no intro, no code block markers.

  2. **Analyze the Input Data:**
  – **Cargo:** Vendedor Interno – Construção Civil – Salvador
  – **Empresa:** BuscarVagas
  – **Localização:** Salvador, Bahia
  – **Truncated snippet:**
  – Atividades: Vendas internas de materiais especializados de construção civil; Atendimento aos clientes presencialmente; Negociar prazos e condições de pagamento; Demonstrar e explicar detalhadamente a forma correta de utilização de cada produto; Manuseio do sistema de acompanhamento de vendas interno; Auxiliar no pós-vendas, entre outros.
  – Salário: Fixo Comissão VA VT Plano de Saúde
  – Requisitos: Buscamos profissionais que tenham gosto por aprendizagem e que estejam dispostos a aprender de forma…

  3. **Identify What’s Allowed & What’s Not:**
  – *Not allowed:* Invent specific salary amounts, false certifications, fake benefits, made-up years of experience.
  – *Allowed:* General industry-standard language for the role, natural descriptions of typical responsibilities for “Vendedor Interno – Construção Civil”, as long as they’re not presented as confirmed facts beyond the snippet. I need to be careful: I can describe what the role typically involves in that sector, but I must not invent specifics like “3 anos de experiência” or “certificação em segurança do trabalho” unless implied. The snippet says “gosto por aprendizagem” and “dispostos a aprender de forma…” (truncated). I can expand on the learning attitude generally.
  – *Must keep:* The actual given data: role, company, location, activities list (but I can rephrase/expand naturally), salary structure (fixed + commission + VA + VT + health plan – I can mention these categories but not invent values), requirements (attitude toward learning).
  – *HTML constraints:* Only `

  ` and `

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

    `). No markdown. Just plain HTML paragraphs and lists.

    4. **Structure the HTML Output:**
    – I need to output only the description HTML.
    – It should be ~700 words. That’s quite long for just `

    ` and `

    ` tags, but doable by having multiple paragraphs and list items with descriptive text.
    – I need to make sure it reads naturally in Brazilian Portuguese.
    – I’ll organize it logically: activities, requirements, benefits/remuneration, location/company maybe, but without inventing things.

    Let’s plan the content based *only* on the snippet and general knowledge of the role, without inventing:
    – Activities: From the snippet, I can expand each point with general, typical language for “materiais especializados de construção civil”, but keeping it generic and true to the description. E.g., “prospectar clientes”, “apresentar soluções técnicas”, etc., but I must be careful not to say “the job requires X” if it’s not in the snippet. I can say “entre as responsabilidades, destaca-se…” but without headings. Maybe I’ll weave them into paragraphs and lists.
    – Actually, the constraint 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 use standard sector language, but I must not present assumptions as facts. I’ll describe the activities in a general, natural way, using the listed ones as anchors, but not adding new specific tasks that aren’t implied. I can add general phrasing like “participar do ciclo de vendas”, “garantir a satisfação do cliente”, etc., as long as it’s standard and not fabricated.
    – Salary: “Fixo Comissão VA VT Plano de Saúde” – I can mention these components exist, but I won’t invent amounts. I’ll just list the types: “Remuneração composta por salário fixo, comissão, vale-alimentação, vale-transporte e plano de saúde.”
    – Requirements: “Buscamos profissionais que tenham gosto por aprendizagem e que estejam dispostos a aprender de forma…” – I can complete naturally with “com o processo e com as soluções oferecidas”, but keeping it general. I won’t invent specific years or diplomas.
    – Company: “BuscarVagas” – I can mention it’s uma plataforma de conexão entre candidatos e empresas, but I need to be careful. The snippet just says “Empresa: BuscarVagas”. I’ll treat it as the employer/aggregator, maybe mention the location.

    Let’s think about the HTML structure:
    – I’ll use `

    ` for blocks of text.
    – I’ll use `

    `/`
    • ` for lists of activities, requirements, benefits.
      – I need to reach ~700 words. That means I’ll have several paragraphs and list items with substantial text. I’ll make sure each `

    • ` and `

      ` has enough content to contribute to the word count, while remaining professional and relevant.

      Let’s outline the HTML content (mental):
      – Intro paragraph about the role and company/location.
      – Paragraph describing the main purpose.
      – List of activities (using `

      • `). I’ll include the 6 from the snippet, plus maybe one or two general ones that are standard, but I’ll frame them carefully. Actually, I should stick close to the snippet. I can expand each bullet with a sentence or two of general, appropriate language, but not invent facts. E.g., “Vendas internas de materiais especializados de construção civil: responsabilidade por apresentar catálogos, entender necessidades do cliente e propor soluções adequadas ao tipo de obra.” That’s general but true to the snippet.
        – Paragraph or list about requirements: attitude to learn, maybe some soft skills implied (communication, organization), but not inventing years of experience.
        – List/paragraph about benefits/remuneration: fixed, commission, VA, VT, health plan. I’ll list them as given.
        – Closing paragraph about integration and growth (general, standard).

        Word count management: I need ~700 words. That’s a lot. I’ll need to be descriptive but careful. I’ll use multiple paragraphs with several sentences each, and list items with descriptive text. I’ll count roughly as I go.

        Let’s start drafting the HTML in my mind, ensuring I only use `

        ` and `

        `/`
        • `. No `
          

          `, etc. I’ll make sure the output is just the HTML, no explanations, no code fences (but the user said “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 should output just the HTML text, no “`html“` markers. I’ll just write the raw HTML.

          Wait, the user 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).” This means I should not include “`html“` or “`markdown“`. Just the raw HTML content. I’ll output the HTML strings directly.

          Let’s draft the content carefully.

          First, I’ll structure the HTML:

          …text…

          • …
          • …

          …

          …text…

          • …

          …

          …text…

          I need to make sure the total word count is ~700. I’ll aim for substantial text. Let’s plan:

          – Paragraph 1: ~80 words introducing the vacancy.
          – Ul of activities: maybe 6-8 li items, each ~60-70 words -> ~450 words. That’s a lot for li. Maybe I’ll make each li a paragraph? But constraint says use

          /
          • . I can have
          • with multiple sentences.
            – Actually, I can have

            paragraphs and

            • lists. I’ll mix them.
              – To reach 700 words, I need a lot of text. I’ll be very descriptive but generic.

              Let’s reconsider: 700 words in HTML with only

              and

              /
              • is achievable if I write many sentences. I’ll make sure each

                has ~80-100 words, and each

              • has ~50-70 words. With maybe 6-8

                and 6-8

              • , I can hit 700.
                • Empresa: BuscarVagas
                • Localização: Salvador, Bahia
                • Categoria da Vaga: Unknown
                • Tags da Vaga: Salvador