Auxiliar Administrativo

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, no other tags.
  – Do NOT invent specific facts not implied in the snippet or provided fields.
  – Can use general/standard sector language appropriate to the role, but treat suppositions as natural descriptions, not confirmed facts.
  – Keep text truthful, professional, legible.
  – Write entirely in Brazilian Portuguese, natural and clear, no unnecessary anglicisms.
  – Target size: ~700 words.
  – Output ONLY the HTML description, no title, no introduction, no code block markers.

  2. **Analyze the Input Data:**
  – **Cargo:** Auxiliar Administrativo
  – **Empresa:** R2T Telecomunicações
  – **Localização:** Salvador, Bahia
  – **Trecho original (truncado):**
  – “Empresa de Telecomunicações admite Auxiliar Administrativo (PCD) em Salvador.”
  – “Principais Responsabilidades: Controle de documentos. Acompanhamento de baixa de material em sistema e controle das baixas. Alimentação de planilhas de recebimento e saída de material em sistema. Conferência e controle de notas fiscais.”
  – “_Vaga destinada para PCD._”
  – “Benefícios oferecidos: – Vale Alimentação – Vale Transporte – Assistência Médica – Assistência Odontológica – Gympass”
  – “Salário: – 1.500,0…” (truncated, so I must NOT invent a full salary; I can only mention what’s given or use general terms if needed, but rule 1 says NOT invent specific facts beyond what’s informed. The salary is truncated at “1.500,0…”, so I should not invent the full amount. I’ll handle this carefully.)

  3. **Identify What I Can & Cannot Do:**
  – **Can do:** Use standard descriptions of “Auxiliar Administrativo” responsibilities that are generic and aligned with the listed tasks, but frame them as typical duties, not as confirmed facts from the company beyond what’s stated. Use general language appropriate to the role.
  – **Cannot do:** Invent a specific salary amount beyond “1.500,0…” or make up benefits not listed. The snippet lists specific benefits, so I can those. I should not invent additional benefits. I should not invent years of experience, certifications, etc.
  – **Salary:** The snippet says “- 1.500,0…” which is clearly truncated. I must not complete it or invent a full value. I can either omit it, mention it’s according to company policy, or use a very general phrase, but must not fabricate. I’ll likely just not include a specific amount, or perhaps mention “a combinar” or similar, but carefully. Actually, the rule says “sem valores de salário fabricados além do que foi informado”. Since only “1.500,0…” is given, I should not invent the rest. I’ll either omit the specific number or phrase it very cautiously, but given the word count target and the need to be professional, I might just not include a salary line, or mention “salário a combinar” if appropriate, but I need to check if that’s inventing. Better to just not include a fabricated number. I’ll see how to integrate it without inventing.
  – **PCD flag:** The snippet mentions “_Vaga destinada para PCD._” I can include this as a fact from the snippet.
  – **Company:** R2T Telecomunicações
  – **Location:** Salvador, Bahia

  – **Responsibilities listed:** Controle de documentos, Acompanhamento de baixa de material em sistema e controle das baixas, Alimentação de planilhas de recebimento e saída de material em sistema, Conferência e controle de notas fiscais. I can expand these into a natural-sounding list of typical administrative assistant duties in a telecom/commerce context, but I must not say “The company does X” if it’s not in the text. I can say “Entre as responsabilidades, o profissional irá…” or use general phrasing that aligns with the listed items, without claiming they are exhaustive or officially confirmed beyond the snippet. Actually, the prompt 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 describe typical duties of an Administrative Assistant in general, as long as I don’t present them as confirmed facts from this specific vacancy beyond what’s listed. I’ll stick close to the listed items but phrase them naturally.

  – **Benefits:** Listed: Vale Alimentação, Vale Transporte, Assistência Médica, Assistência Odontológica, Gympass. I can these as bullet points.

  – **Word count target:** ~700 words. That’s quite long for an HTML snippet with only `

  ` and `

  /
  • `. I need to generate a lot of text while staying truthful and not inventing. I’ll need to elaborate on the role, company context, requirements, environment, etc., using general knowledge of the sector and standard admin assistant tasks, but always framing it as general/standard, not specific to the company beyond the given data. I need to be careful not to cross the line into inventing. The prompt allows “linguagem geral e padrão do setor” appropriado ao cargo. So I can describe what an Auxiliar Administrativo typically does in a telecom company, referencing the listed duties as examples, but not as the only things. I’ll make sure to attribute the specific listed duties to the vacancy, and expand others in a general way, perhaps noting “Além das atividades específicas listadas, o profissional pode…” but cautiously. Actually, better to keep the expansion focused on general administrative tasks that are standard, and intersperse the listed ones.

    – **HTML constraints:** Only `

    ` and `

    /
    • `. No headings. So I’ll structure it as paragraphs and lists. I need to produce exactly the HTML, no title, no intro message, no code block markers. The output should be just the HTML string.

      Let me plan the structure:
      – A paragraph introducing the company and location, using the given data.
      – A paragraph or section on the role, mentioning it’s for PCD, referencing the truncated salary carefully.
      – A list of responsibilities: I’ll use `

      • ` for the listed ones, and maybe add a few general ones framed as “atividades comuns a essa função”, but I need to ensure I don’t invent facts. I can say “Entre as atividades, o profissional pode atuar com:” and then list the given ones, plus maybe one or two very generic ones that are almost unavoidable for an admin assistant, but I’ll try to keep them implied or very general. Actually, the prompt says “NÃO invente fatos específicos que não estejam implícitos no trecho fornecido ou nos campos dados”. So I should not add responsibilities that aren’t hinted at or general. I can stick strictly to the listed responsibilities, perhaps expanding each into a short sentence that stays true to the description. But to reach ~700 words, I’ll need a lot of text. I can add general context about the telecom sector, the importance of administrative support, etc., as long as it’s not specific invented facts. I can talk about the role’s contribution, the environment, etc., using very general language.
        – Benefits section: `
        • ` the listed benefits.
          – Maybe a paragraph on requirements/general profile, but without inventing years of experience. I can say “Experiência na área administrativa” generally, but not specify years. The prompt says “sem exigências de anos de experiência inventadas”. So I can mention “experiência na área” generically, or leave it vague.
          – I need to hit ~700 words. That’s a lot of HTML paragraphs and list items. I’ll need to be expansive but careful.

          Let me re-read the constraints carefully:
          “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.”
          “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.”
          “3) Mantenha o texto verdadeiro, profissional e legível — pensando em uma pessoa real decidindo se deve se candidatar.”
          “4) Escreva inteiramente em português do Brasil, natural e claro, sem anglicismos desnecessários.”
          “5) Tamanho alvo: aproximadamente 700 palavras.”
          “6) 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).”

          Key: “aproximadamente 700 palavras” in HTML with only

          and

          /
          • . That means the combined text of all

            and

            • Empresa: R2T Telecomunicações
            • Localização: Salvador, Bahia
            • Categoria da Vaga: Unknown
            • Tags da Vaga: Salvador