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 provided fields
  – Can use general/sector-appropriate language, but treat suppositions as natural, not confirmed facts
  – Keep text truthful, professional, legible
  – Write entirely in Brazilian Portuguese, natural, 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:**
  – **Job Title:** Analista de Planejamento Financeiro – Fp&A
  – **Company:** PetroReconcavo S.A.
  – **Location:** Salvador, Bahia
  – **Snippet:**
  “Estamos em busca de um(a) Analista de Planejamento Financeiro III. Se você é uma Pessoa entusiasta, resiliente, austera, integra e trabalha com segurança, respeito e confiança nas pessoas, estamos te esperando para transformar recursos em valor e sonhos em realidade! Essa vaga tem como prioridade Pessoas com Deficiência, Negras, LGBTQIA e Mulheres. Se você faz parte de um desses grupos, venha fazer parte de uma Petroreconcavo mais diversa, plural e inclusiva. Venha fazer parte desse time que só…”

  3. **Identify What’s Given vs. What Can Be Inferred/Generalized:**
  – **Given:**
  – Title: Analista de Planejamento Financeiro III (Senior level implied by “III”)
  – Company: PetroReconcavo S.A.
  – Location: Salvador, Bahia
  – Core values: enthusiasm, resilience, austerity, integrity, security, respect, trust in people
  – Mission: transform resources into value, dreams into reality
  – Diversity priority: People with disabilities, Black people, LGBTQIA+, women
  – Partial sentence: “time that só…” (incomplete, should not invent what comes after)
  – **Not given/Can’t invent:**
  – Specific salary
  – Specific certifications
  – Exact years of experience (can use general “experience in the field” but not invent a number)
  – Specific benefits beyond what’s implied or standard without inventing
  – Exact reporting structure
  – Complete job description beyond the snippet’s intent

  – **What I can reasonably generalize (without inventing facts):**
  – Typical responsibilities of a “Analista de Planejamento Financeiro III” / Fp&A Analyst in the oil/gas sector (but keep it general, not presented as absolute fact)
  – Standard requirements for such a role (education, analytical skills, software proficiency – but keep it generic and plausible without claiming it’s from the snippet)
  – The company’s stated values and diversity focus must be preserved exactly
  – The incomplete ending “time that só…” should be handled carefully – maybe end with “time that makes a difference” or similar, but must not invent. Actually, the constraint says “NÃO invente fatos específicos que não estejam implícitos”. The snippet ends abruptly. I should either stop naturally or complete it in a very generic, plausible way that doesn’t invent company-specific details. But the prompt says “sem certificações falsas, sem benefícios inventados, sem exigências de anos de experiência inventadas.” I need to be careful. I’ll keep the description focused on what’s given and use very standard, generic phrasing that any Fp&A analyst role might have, without claiming it’s from this specific ad beyond the snippet.

  – **HTML Structure:** Only `

  ` and `

  /
  • `. No headings (`
    

    –

    `), no markdown. I need to output just the HTML, approximately 700 words. I’ll need to write quite a few paragraphs and list items.

    – **Language:** Brazilian Portuguese, natural, professional.

    Let me outline the HTML content strategy:
    – Use multiple `

    ` paragraphs
    – Use `

    • ` for lists of responsibilities/requirements/benefits (but keep them generic/plausible)
      – Avoid `

      `, `

      `, etc.
      – Target ~700 words in total HTML text content

      Important: I must not invent salary, specific years, certifications, or exact benefits. I can mention “benefits compatible with market standards” but carefully, or stick to what’s implied. Actually, the constraint says “sem benefícios inventados”. So I should either omit benefits or only mention what’s in the snippet (diversity priority, values). I’ll focus on the role description, company values, and diversity focus, using generic but appropriate language for an Fp&A analyst in oil & gas, without inventing specifics.

      Let me 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.”
      This means I can mention experience generally, but not “5+ years”. I can mention software skills generally, but not specific ones if not implied. The snippet doesn’t mention any software, education, or specific tasks beyond “planning financial”. I’ll keep it very safe.

      Actually, I can infer that an “Analista de Planejamento Financeiro III” involves financial planning, analysis, maybe budgeting, forecasting, resource allocation, etc. These are standard for the role. I’ll describe them in general, impersonal terms, as “responsabilities typical of the role” but framed as general sector language, not as confirmed facts from the ad.

      Wait, 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.” So I can use standard sector language, but must not present suppositions as confirmed facts. I’ll make sure to use qualifiers or just state them as general descriptions, not “The job requires…” but rather “The role typically involves…” or I’ll structure it as part of the description without claiming it’s explicitly stated.

      Actually, to be safest, I’ll focus on what’s explicitly in the snippet and expand around it using very generic, plausible language that doesn’t cross into “invented facts”. I’ll avoid listing specific tasks unless I’m sure. But the target is 700 words, so I need to expand quite a bit. I’ll focus on:
      – Company intro (PetroReconcavo, location)
      – The role’s purpose/values (from snippet)
      – Diversity and inclusion emphasis (explicitly stated)
      – General context of Fp&A in the oil & gas sector (but very broadly, not company-specific)
      – Invitation to apply, focusing on the groups prioritized

      I need to be careful not to invent “PetroReconcavo” specifics beyond what’s given. I know PetroReconcavo is an oil & gas company, but I shouldn’t invent company facts. I’ll stick to the snippet.

      Let me draft the HTML content mentally, aiming for ~700 words of text within `

      ` and `

      • ` tags.

        Structure plan:
        – Paragraph introducing the opportunity, company, location
        – Paragraph on the role’s mission/values from snippet
        – Ul/li list of general aspects of the role (planning, analysis, collaboration) – kept very generic
        – Ul/li list of desired profile traits (from snippet: enthusiast, resilient, austere, integrative, security, respect, trust)
        – Paragraph on diversity priority (exact text from snippet can be included/paraphrased carefully)
        – Ul/li list of why join PetroReconcavo (generic, based on snippet: transform resources into value, diverse/plural/inclusive environment)
        – Maybe a final paragraph inviting application

        But I must ensure total words ~700. That’s a lot for just `

        ` and `

        • `. I’ll need to write extensively. Let me count: ~700 words total HTML text. I’ll write maybe 6-7 paragraphs of ~80-100 words each, plus several list items with ~50-70 words each. I need to be meticulous.

          Actually, re-reading: “Tamanho alvo: aproximadamente 700 palavras.” This likely means the visible text content should be around 700 words. I’ll aim for that.

          Constraints check:
          – Only `

          ` and `

          /
          • `: I’ll make sure no `<h1`-`
            

            `, no `

            `, no `
            ` necessarily (though `
            ` might be allowed but I’ll avoid to be safe, use paragraphs and lists only)
            – No markdown, no code block markers in output
            – Only output the HTML

            Let me start drafting. I’ll write the HTML in one go, ensuring word count and constraints.

            I need to count words carefully. Let me plan the text:

            Paragraph 1: Introduce the vacancy, company, location. ~80 words.
            Paragraph 2: Role purpose, transforming resources into value. ~80 words.

            • Empresa: PetroReconcavo S.A.
            • Localização: Salvador, Bahia
            • Categoria da Vaga: Unknown
            • Tags da Vaga: Salvador