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:**
– HTML only, using `

` and `

/
• ` only
  – No headings, no markdown
  – No invented specific facts (salary, certifications, benefits, experience years unless implied)
  – Can use general sector-appropriate language naturally
  – Must be truthful, professional, legible
  – Portuguese (Brazil), no unnecessary anglicisms
  – Target ~700 words
  – Output ONLY the HTML, no title, no intro, no code blocks

  2. **Analyze the Input Data:**
  – **Job Title:** Analista de Sac Jr – Feira de Santana/ba
  – **Company:** PIZZATTOLOG TRANSPORTADORA DE CARGAS RODOVIARIAS
  – **Location:** Feira de Santana, Bahia
  – **Truncated Responsibilities (from aggregator):**
  – Recebimento e lançamneto de solicitação de carga;
  – Mapa de Carregamento;
  – Atendimento aos fornecedores externos/internos;
  – Agendametos(geral);
  – Controle de Diárias;
  – Reuniões com Clientes;
  – Correções de MultCte;
  – Identificar e resolver problemas dos clientes, como reclamações, devoluções e questões técnicas, e encaminhar e acompanhar problemas mais complexos para os departamentos apropriados.
  – Manter registros detalhados e precisos de todas as interações com os clien… (truncated)

  3. **Determine What’s Implied vs. What Can Be Generalized:**
  – I must NOT invent salary, specific years of experience, false certifications, or made-up benefits.
  – I CAN use standard, general descriptions of these responsibilities as they typically exist for a “Analista de SAC Jr” in a transport/logistics company, as long as I don’t present assumptions as confirmed facts.
  – The company is “PIZZATTOLOG TRANSPORTADORA DE CARGAS RODOVIARIAS” – I should respect this name, maybe mention the sector (road transport/logistics) but keep it general.
  – Location: Feira de Santana, BA – can mention the location context.
  – Junior level (“Jr”) – I can mention it’s an entry-level/junior position, but without inventing specific years. I can use general language like “experiência inicial” or “atuando na área” but carefully. Actually, rule 1 says: “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.” So I should NOT invent years of experience. I can say “posição júnior” or “iniciante” but maybe better to just describe the role naturally without specifying exact experience years unless implied by the title. I’ll avoid stating “2 anos de experiência” or similar. I’ll just say “atuação na área” or keep it open.
  – The responsibilities listed are clear. I can expand each into a natural paragraph or list item, using general sector language, but I must not invent new responsibilities that aren’t hinted at.

  – Let’s look at the responsibilities:
  1. Recebimento e lançamento de solicitação de carga
  2. Mapa de Carregamento
  3. Atendimento aos fornecedores externos/internos
  4. Agendamentos (geral)
  5. Controle de Diárias
  6. Reuniões com Clientes
  7. Correções de MCTe (likely “Conhecimento de Transporte Eletrônico”, but I shouldn’t expand acronyms incorrectly; I can say “documentação de carga” or keep it as “correções de MCTe” if it’s in the text, but I’ll generalize to “documentação e compliance de transporte” if needed, but better to keep close to the text)
  8. Identificar e resolver problemas dos clientes (reclamações, devoluções, questões técnicas), encaminhar problemas complexos
  9. Manter registros detalhados e precisos de interações com clientes (truncated)

  – I need to expand these into a full job description, approximately 700 words, in HTML only, using `

  ` and `

  /
  • `. No headings. So the entire output will be a series of paragraphs and lists.

    – Structure plan (in my head, but output must be just HTML, no comments):
    – I’ll start with a paragraph introducing the company and location, based on the given data.
    – Then a paragraph on the role purpose.
    – Then a list of responsibilities, each as `

  • ` inside a `
    `, but wait, the rule says “use only

    and

    /
    • “. It doesn’t say I can’t have multiple `
      `s, but typically I can have a `
      ` with `
      • `s. However, to reach ~700 words, I need substantial text. Each `
      • ` can contain a paragraph of text. I can also have standalone `

        `s for introductory/closing text.
        – Actually, the rule: “use only

        and

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

          ` blocks and `

          • ` blocks. I should not use `
            

            `. I can use `

            ` and `

            • `. I need to be careful about nesting. I’ll make each responsibility a `
            • ` with text inside. I can also have `

              ` for introductory and concluding text.
              – To hit ~700 words, I need each `

            • ` to be quite long, maybe 60-80 words each, times maybe 10-12 items, plus intro/outro paragraphs. That should work.

              – Let’s outline the content carefully, staying true to the truncated text, not inventing facts, using general sector-appropriate language.

              – Intro paragraph: Something about PIZZATTOLOG TRANSPORTADORA DE CARGAS RODOVIARIAS, located in Feira de Santana, BA, seeking an Analyst for SAC Jr. Mention the logistics/transport sector context generally, but not invent specifics.

              – Responsibilities expansion (each as `

            • `):
              1. Recebimento e lançamento de solicitação de carga: Describe the process of receiving and logging cargo requests, ensuring data accuracy, supporting the operational flow. Keep it general.
              2. Mapa de Carregamento: Coordinating loading maps, aligning vehicles, cargo types, destinations. General description.
              3. Atendimento aos fornecedores externos/internos: Acting as liaison, communicating requirements, clarifying doubts, maintaining professional rapport.
              4. Agendamentos (geral): Scheduling pickups, deliveries, meetings, optimizing routing and timelines.
              5. Controle de Diárias: Managing per diem allowances, tracking expenses, ensuring compliance with company policy.
              6. Reuniões com Clientes: Participating in client meetings, presenting updates, gathering feedback, aligning expectations.
              7. Correções de MultCte: Handling electronic transport knowledge corrections, ensuring legal/regulatory compliance, resolving discrepancies.
              8. Identificar e resolver problemas dos clientes: Addressing complaints, returns, technical issues; escalating complex cases to appropriate departments; following up.
              9. Manter registros detalhados e precisos de todas as interações com os clientes: Documentation, CRM or internal systems, accurate logging for audit and service quality.

              – I’ll make sure each point is a `

            • ` with a `

              ` inside? Wait, the rule says “use only

              and

              /
              • “. It doesn’t explicitly forbid nesting `

                ` inside `

              • `, but to be safe, I can have `
              • ` containing text directly, or `

                ` inside `

              • `. Usually, HTML allows `

                ` inside `

              • `. I’ll just put the text directly inside `
              • `, and if I need separation, I can use line breaks or just run-on sentences. But to reach word count, I’ll make each `
              • ` a paragraph-length text. I can also have multiple `

                ` outside the list. The structure will be: intro `

                `, then `

                • …`, etc., then maybe a closing `

                  `. But the rule says “use only

                  and

                  /
                  • “, which probably means I can use those tags, not that I can’t have text outside them, but the output should be clean HTML consisting of those tags. I’ll structure it as a series of `

                    ` and `

                    • ` blocks.

                      – Let’s count words aim: ~700 words. I’ll aim for about 8-9 responsibilities as `

                    • `, each ~70-80 words, plus intro and closing ~50-60 words each. That’s roughly 8*75 = 600 + 110 = 710. Good.

                      – I need to ensure I don’t invent specific years, salaries, certifications. I’ll avoid phrases like “exigência de 6 meses” or “salário de R$ X”. I’ll just

                      • Empresa: PIZZATTOLOG TRANSPORTADORA DE CARGAS RODOVIARIAS
                      • Localização: Feira de Santana, Bahia
                      • Categoria da Vaga: Unknown
                      • Tags da Vaga: Feira de Santana