Coordenador De Operações Logísticas – Recrutamento Aberto

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:**
– Only use `

` and `

/
• ` tags (no headings, no markdown)
  – Do NOT invent specific facts not implied in the snippet or provided fields
  – CAN use general/standard sector language appropriate to the role, naturally, without treating assumptions as confirmed 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:**
  – **Job Title:** Coordenador De Operações Logísticas – Recrutamento Aberto
  – **Location:** Vitória da Conquista, Bahia
  – **Truncated Snippet:**
  – ATRIBUIÇÕES: Responsável por Coordenar as atividades de um centro logístico, assegurando o bom funcionamento do turno de sua responsabilidade, entregando as metas acordadas e realizando os devidos reports.
  – REQUISITOS: Desejável Ensino Superior Completo (ou em fase de conclusão) em Logística ou Engenharia de Processos. Experiência sólida em Gestão de pessoas e processos. Experiência com Lead Time e KPIs. Excel intermediário > avançado.
  – JORNADA: Jornada período tarde/noite, escala 6×1.
  – BENEFÍCIOS: T… (truncated, only “T…” shown)

  3. **Identify What I Can & Cannot Do:**
  – *Cannot invent:* Specific salary, specific benefits beyond what’s hinted (only “T…” which I should not expand falsely), exact years of experience not specified, false certifications, made-up requirements.
  – *Can do:* Use standard, professional language describing typical responsibilities of a Logistics Operations Coordinator, frame them generally based on the snippet, keep it truthful, use the exact data provided (title, location, requirements snippets, schedule, partial benefits).
  – *Must follow:* Only `

  ` and `

  /
  • `, no headings, no markdown, pure HTML, ~700 words in Portuguese BR, natural.

    4. **Structure the HTML Output:**
    – I need to build a coherent description using only `

    ` and `

    • ` tags.
      – I’ll organize it logically: job overview, responsibilities (generalized but grounded in the snippet), requirements (same), schedule/benefits (careful with the “T…” – I should not invent the rest, maybe mention it’s partial or use “entre outros” style but without inventing). Actually, constraint 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 for benefits, I only know “T…” which is truncated. I should not guess the full benefits. I could mention “benefícios compatíveis com o cargo” but that might be too vague/general. Better to only include what’s explicitly given, or very generally allude without inventing. The snippet says “BENEFÍCIOS: T…” – I’ll just put a `

    • ` that says something like “Benefícios a serem definidos durante o processo seletivo” or simply omit benefits beyond what’s known. But the task says to expand to ~700 words. I need to be careful.
      – Let re-read 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.”
      – So I cannot invent benefits. I can only state what’s in the snippet. The snippet only shows “T…”. I could write “Benefícios: informações não fornecidas completamente” but that might not fit well. Maybe I can structure the benefits section by saying “Pacote de benefícios a ser detalhado na etapa de recrutamento” but that’s borderline. Safer: only mention what’s certain, or use very generic phrasing that doesn’t specify actual benefits. Actually, I could omit the benefits list or put a placeholder that’s not factual. But the word count target is ~700 words. I’ll need to expand on the role, responsibilities, requirements using general professional language that’s implied, without inventing specifics.

      – Let’s plan the HTML structure:
      – A paragraph introducing the company/vaga (general, not invented)
      – Responsibilities section using `

      • ` – I’ll list responsibilities derived from the snippet, but phrased generally/standardly for a Logistics Operations Coordinator, without adding fake details. E.g., “Coordenação de operações logísticas”, “Gestão de turnos”, “Entrega de metas”, “Relatórios”. These are directly from the snippet, so it’s safe.
        – Requirements section using `
        • ` – using the exact given requirements, but phrased naturally. “Ensino Superior Completo em Logística ou Engenharia de Processos (ou em fase de conclusão)” – exact. “Experiência sólida em Gestão de pessoas e processos” – exact. “Experiência com Lead Time e KPIs” – exact. “Excel intermediário a avançado” – exact.
          – Schedule section: “Jornada período tarde/noite, escala 6×1” – exact.
          – Benefits: Only “T…” – I’ll handle this carefully. Maybe I’ll write a `

        • ` that says “Benefícios a serem compatíveis com o cargo e negociados durante o processo seletivo” – that’s generic and not inventing specific values. Or I could omit the benefit details and just say “Pacote de benefícios a ser confirmado”. I think the safest is to include a generic statement without inventing.
          – Location: “Vitória da Conquista, Bahia” – exact.

          – Word count target: ~700 words. That’s quite a lot for just `

          ` and `

          • `. I need to expand descriptively but within the constraints. I can write extended paragraphs explaining the role’s context, the importance of the functions, the profile sought, using general industry knowledge but attributing it to the role without claiming it’s specifically from the snippet beyond what’s stated. I must ensure I don’t invent facts. I can talk about “typical responsibilities of a logistics operations coordinator” as general sector language, as allowed by constraint 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.” Wait, the example gives ‘Operador de Empilhadeira’ but the cargo is Coordenador De Operações Logísticas. I’ll use general language appropriate to a Logistics Operations Coordinator, but keep it grounded and not claim specific facts not in the snippet.

            – Let’s outline the HTML content in Portuguese, aiming for ~700 words, using only `

            ` and `

            • `. I’ll need to be meticulous about tag usage. No `
              

              `, no `

              `, no markdown. Just `

              ` and `

              • `. I can have multiple `

                ` and `

                • ` elements.

                  – Let’s draft the content mentally, then convert to HTML structure.

                  – *Drafting content (Portuguese):*
                  Paragraph 1: Introduction to the vacancy, company context (generic), location.
                  Then responsibilities: I’ll use a `

                  • ` list, but each `
                  • ` can be long. Or I can have `

                    ` describing, then `

                    • `. The constraint says “use only

                      and

                      /
                      • “, so I can mix them. I’ll probably use `

                        ` for introductory text, and `

                        • ` for lists of requirements/benefits/responsibilities, but I can also describe in `

                          ` using general language.

                          – Let’s plan the structure:

                          …intro…

                          …about the role…

                          • …responsibility 1…
                          • …responsibility 2…
                          • …responsibility 3…

                          …requirements…

                          • …requirement 1…
                          • …requirement 2…
                          • …requirement 3…

                          …schedule…

                          • …schedule detail…

                          …benefits…

                          • …benefit note…

                          …location…

                          – But I need ~700 words. That’s a lot of `

                        • ` items with substantial text, plus `

                          ` paragraphs. I’ll make each `

                        • ` and `

                          `

                          • Localização: Vitória da Conquista, Bahia
                          • Categoria da Vaga: Unknown
                          • Tags da Vaga: Vitória da Conquista