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

` and `

/
• `. No headings, no markdown, no code blocks, no title/intro/outro text outside the HTML.
  – **Constraints:**
  – Do NOT invent specific facts not implied in the snippet or given fields.
  – Can use general/standard industry language appropriate to the role, but treat assumptions as natural descriptions, not confirmed facts.
  – Keep text truthful, professional, legible.
  – Write entirely in Brazilian Portuguese, natural, clear, no unnecessary anglicisms.
  – Target size: ~700 words.
  – **Input Data:**
  – Job Title: Técnico de Análises Clínicas
  – Location: Feira de Santana, Bahia
  – Snippet: “Atuar com coleta de amostras de sangue nos pacientes; Realizar exames imunohematológicos (testes pré transfusionais); Instalar os hemocomponentes; Acompanhar transfusão de sangue e possíveis reações adversas.”

  2. **Deconstruct the Snippet & Expand Responsibly:**
  – The snippet lists 4 bullet-point-like duties:
  1. Coleta de amostras de sangue
  2. Exames imunohematológicos (testes pré transfusionais)
  3. Instalar hemocomponentes
  4. Acompanhar transfusão de sangue e reações adversas
  – I need to expand these into a full job description, but I must NOT invent specific requirements (years of experience, specific certifications, exact salary, etc.) that aren’t implied or given.
  – I CAN use general, standard language for a “Técnico de Análises Clínicas” role, focusing on responsibilities, skills, qualities, working conditions, etc., but keeping it generic and truthful to the profession.
  – I need to reach ~700 words. That’s quite long for a job ad snippet expansion, but doable by adding standard sections: overview, responsibilities, requirements (general), skills/attributes, working conditions, how to apply (generic), etc. But wait – the output should be *only* the HTML description. I can structure it with paragraphs and lists.
  – I must be careful not to invent specific “requirements” like “3 anos de experiência” unless implied. The snippet doesn’t mention experience level, so I should use general terms like “experiência prévia”, “conhecimentos”, etc., but keep it vague/standard.
  – Actually, re-reading 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’t say “exigência de 2 anos de experiência” if it’s not in the snippet or given fields. I also can’t invent salary, benefits, specific certifications. I *can* use general industry-standard language that’s not fact-specific.
  – 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.” This gives me leeway to describe typical duties of a Clinical Lab Technician in general terms, as long as I don’t present them as the only truth or invented facts.
  – Constraint 5: Target ~700 words. That’s the total HTML content length.
  – Constraint 6: Output *only* the HTML, no title, no intro, no code block markers. Just the HTML content.

  3. **Drafting – Strategy:**
  – I’ll create an HTML structure with `

  ` paragraphs and `

  • ` lists.
    – I’ll organize it logically: a brief introduction/overview, then responsibilities (expanding the snippet), then general requirements/skills (standard, not invented specifics), then about the location/company context (but carefully, without inventing), and maybe a closing note on application (generic).
    – I need to hit ~700 words. That’s about 4-5 substantial paragraphs + a list or two. I’ll need to be descriptive but stay within the bounds of not inventing facts.
    – Let’s outline the HTML content:
    – `

    `: Overview of the role, importance in healthcare, location.
    – `

    • `: Expanded responsibilities (derived from snippet, generalized).
      – `

      `: About the workplace/environment.
      – `

      • `: General profile/skills (technical, behavioral, standard for the role).
        – `

        `: How to apply or next steps (generic).
        – I’ll make sure every statement is either directly from the snippet, obviously general/standard, or clearly marked as “typical” or “common” without presenting as absolute fact from the snippet. But since the prompt says “não trate suposições como fatos confirmados”, I need to be careful. I’ll use phrases like “entre outras”, “atividades inerentes”, “entre as responsabilidades”, which softens it.
        – Actually, re-reading: “Você PODE usar linguagem geral e padrão do setor… desde que apresente isso de forma natural e não trate suposições como fatos confirmados.” So I can say “Entre as atividades típicas de um técnico de análises clínicas, destaca-se a coleta de amostras…” – that’s general sector language, not invented fact.
        – I’ll avoid “3 anos de experiência”, “R$ 2.500,00”, “VR”, “Vale-refeição”, etc.

        Let’s start drafting content in Portuguese, then format as HTML.

        Word count target: ~700 words. I’ll aim for rich but concise text. Each paragraph ~80-120 words. Maybe 5-6 paragraphs + list items.

        Draft thoughts (mental):
        – Paragraph 1: Introdução sobre a importância do técnico de análises clínicas no contexto de saúde, localização Feira de Santana, Bahia. Mention the role supports diagnosis and patient safety.
        – Ul li: Expand the 4 points from snippet, adding standard context. E.g., “Realizar a coleta de amostras de sangue…” -> I can elaborate on proper identification, hygiene, biosafety, etc., using general language.
        – Ul li: “Realizar exames imunohematológicos…” -> talk about compatibility testing, blood group determination, etc., standard procedures.
        – Ul li: “Instalar os hemocomponentes…” -> transfusion setup, verification, administration.
        – Ul li: “Acompanhar transfusão…” -> monitoring, reaction protocols.
        – Paragraph: Perfil profissional – formação em técnico em análises clínicas ou curso relevante, registro no conselho, conhecimento em hemoterapia, atenção aos detalhes, comunicação, trabalho em equipe.
        – Paragraph: Condições de trabalho – ambiente hospitalar ou laboratório, horários, equipe multidisciplinar.
        – Paragraph: Como candidatar – encaminhar currículo, etc., but generic.

        I need to make sure I don’t invent specific requirements. I’ll keep it to “formação na área”, “conhecimentos em hemoterapia”, “experiência na área” (but without specifying years). Actually, “experiência na área” is general and not a specific invented fact if not quantified. But to be safe, I’ll say “experiência prática” or “atividade na área” without numbers.

        Let’s actually count words mentally as I go, or just write freely and then adjust. Target 700 words is quite long for HTML lists/paragraphs. I’ll need to expand significantly on each point, using professional, descriptive language.

        Let’s structure the HTML:

        “`html

        …overview…

        • …expanded responsibility 1…
        • …expanded responsibility 2…
        • …expanded responsibility 3…
        • …expanded responsibility 4…

        …profile…

        • …skill 1…
        • …skill 2…
        • …skill 3…

        …closing…

        “`

        Wait, the prompt says “use only

        and

        /
        • , without headings, without markdown”. It doesn’t forbid multiple

          and

          /
          • blocks. It just says “use only

            and

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

              and

              • . I just can’t use
                

                –

                , no markdown syntax (like **, #, etc.), no code blocks.

                I’ll generate the HTML carefully.

                Now, let’s draft the content in Portuguese, aiming for ~700 words total in the HTML body.

                I’ll start writing, keeping track of word count approximately.

                Draft:

                O técnico de análises clínicas desempenha papel fundamental no sistema de saúde, atuando diretamente no atendimento ao paciente e na geração de resultados confiáveis para diagnóstico e tratamento. Na

                • Empresa: Vagas de Emprego Bahia
                • Localização: Feira de Santana, Bahia
                • Categoria da Vaga: Unknown
                • Tags da Vaga: Feira de Santana