Sobre esta vaga
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 clean (only `
` and `
- `/`
- `, no headings, no markdown)
– **Constraints:**
– Do NOT invent specific facts not implied in the snippet or provided fields
– Can use general/standard industry language appropriate to the role (e.g., “Operador de Empilhadeira” responsibilities), but treat suppositions as natural language, not confirmed facts
– Keep text truthful, professional, legible
– Write entirely in Brazilian Portuguese, natural, clear, no unnecessary anglicisms
– Target size: ~700 words
– Output ONLY the HTML description, no title, no introduction, no code block marking2. **Analyze the Input Data:**
– **Cargo:** Pessoa Técnica de Segurança do Trabalho (Safety Technician)
– **Empresa:** PetroReconcavo S.A.
– **Localização:** Salvador, Bahia
– **Snippet text:**
“Somos a PetroReconcavo, uma empresa produtora de petróleo e gás natural, especializada na operação de campos maduros em bacias terrestres. Trabalhamos para sermos a mais segura, eficiente e lucrativa operadora Independente de Óleo e Gás, e o nosso objetivo é liderar a transformação da Indústria Onshore no Brasil. Acreditamos na diversidade e atuamos para construir um ambiente colaborativo, inclusivo e respeitoso. Nos orgulhamos em impactar positivamente as regiões onde atuamos, e convidamos voc…”3. **Identify What’s Implied vs. What Must Not Be Invented:**
– Implied: Company is in oil & gas, onshore, mature fields, values safety, diversity, inclusivity, impact on regions
– NOT to invent: Specific salary, exact years of experience required (unless generic/standard), fake certifications, made-up benefits, specific technical requirements not hinted at
– CAN use: General responsibilities of a “Pessoa Técnica de Segurança do Trabalho” in oil & gas, standard industry practices, natural phrasing that stays true to the company’s stated values and sector4. **Determine the Structure (HTML only, no headings, just `
` and `
- `/`
- `):**
– Need to expand the company intro, the role, responsibilities (general/standard), requirements (general/standard), and closing
– Must avoid `<h1`-`` tags. The prompt says “use only
and
- /
- , without headings”. So I need to structure the whole thing as paragraphs and lists, possibly nesting lists within paragraphs or using lists for bullet points, but no headings.
– Wait, “without headings” likely means no `` etc., but `
` and `
- `/`
- ` are allowed. I can use `
` for text blocks and `
- `/`
- ` for lists of responsibilities/requirements. I need to make sure there are no heading tags.
– I’ll create a single flowing HTML structure with `` and `
- `/`
- `. Maybe start with a paragraph about the company, then a list about the role, then a list about requirements/benefits (kept general), then a closing paragraph. All in Brazilian Portuguese.
5. **Drafting Content – Mental Refinement (staying within constraints):**
– *Company intro:* From the snippet: PetroReconcavo, oil & gas producer, mature fields on land, safest/efficient/profitable independent operator, leading onshore transformation, values diversity, collaborative/inclusive/respectful, positive regional impact.
– *Role:* Safety Technician. I’ll describe general functions typical for this role in oil & gas, but phrase them as “atividades inerentes” or “responsabilidades”, without claiming specific facts not in the snippet. I’ll keep it generic but appropriate: “auxiliar na implementação de programas de segurança”, “participar de auditorias”, “orientar equipes”, etc. But I must be careful not to invent exact requirements. I’ll use general, standard phrasing that’s true to the role without fabricating.
– *Location:* Salvador, Bahia.
– *Closing:* Invitation to apply, matching the snippet’s “convidamos voc…” -> “convidamos você a fazer parte…”Let’s think about the ~700 words target. That’s quite long for just `
` and `
- `. I need to expand naturally. I’ll write several paragraphs and lists. I need to count roughly. 700 words in Portuguese is about 4000-5000 characters. I’ll aim for substantial but concise content.
Constraints check:
– No invented salary: I won’t mention any.
– No fake certifications: skip.
– No invented benefits: keep general or omit, but I can mention “benefícios compatíveis com o mercado” generically? The rule says “sem benefícios inventados”. So I should either not list specific benefits, or use very generic phrasing that’s not fabricated. Better to avoid listing benefits entirely, or just say “benefícios competitivos” if needed, but that might be considered invented. I’ll stick to what’s implied: the company values safety, diversity, impact. I won’t invent a benefits list.
– No invented experience years: I’ll use general terms like “experiência na área” without specifying years, or keep it vague.
– Language: Brazilian Portuguese, natural, no unnecessary anglicisms.Structure plan:
– ``: Company presentation, from snippet + expansion using general oil/gas sector context, staying true to snippet.
– ``: Role description, general safety technician duties in oil & gas, phrased naturally.
– `- `/`
- `: Maybe list key areas of focus (but without inventing specifics). I can list generic responsibilities that are standard, but phrased as “entre outras atividades inerentes ao cargo”. I need to be careful. The rule says “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 list typical things, but must frame them as general/standard, not as confirmed requirements for this specific vacancy unless implied.
– Actually, to be safe, I’ll avoid `- `/`
- ` for requirements if I’m not sure. But the output format allows and expects `
- `/`
- `. I’ll use them for things that are clearly generic and truly standard, like “participação em treinamentos”, “coleta de dados de segurança”, etc., but phrased carefully.
– Maybe better: Use `` for most text, and `
- `/`
- ` only for very generic, indisputable points like “Atuação em campo onshore” or “Foco em prevenção de acidentes”. But I need to be cautious.
– Let’s re-read: “use onlyand
- /
- , without headings”. It doesn’t say I must use `
- `/`
- `, just that if I use them, they should be those tags. I can structure with just `
` if needed, but the prompt says “expandir… em uma descrição completa e bem organizada, em HTML limpo (use apenas
e
- /
- , sem headings, sem markdown)”. So I should use `
` and `
- `/`
- ` appropriately. I’ll use `
` for paragraphs and `
- `/`
- ` for bullet points where it makes sense, but keep it simple.
Let’s outline the HTML content:
`
…company intro…
`
`…role description…
`
`- …item 1…
- …item 2…
`
`…requirements/general profile…
`
`- …item A…
- …item B…
`
`…closing, location, invitation…
`
Word count target: ~700 words. I’ll need to generate quite a bit. Let’s aim for ~6-8 paragraphs of ~80-100 words each, plus some list items. That should reach ~700.
Important: No headings. So no `
`, `
`, etc. All text in `
` or `
- `.
Let’s start drafting content in Portuguese, keeping it professional, true to the snippet, no invented facts.
Draft content (mental):
Paragraph 1: Company context. “A PetroReconcavo S.A. é uma empresa destacada no setor de petróleo e gás natural no Brasil, com atuação focada na operação de campos maduros em bacias terrestres. A organização tem como missão ser a operadora independente mais segura, eficiente e lucrativa do segmento onshore, conduzindo a transformação da indústria no país. Com uma cultura que valoriza a diversidade, a colaboração e o respeito mútuo, a empresa busca impactar positivamente as comunidades onde está presente, alinhando desempenho operacional com responsabilidade social e ambiental.”
Paragraph 2: Role introduction. “A vaga de Pessoa Técnica de Segurança do Trabalho destina-se a reforçar a equipe de segurança da empresa, atuando diretamente na preven
- ` for bullet points where it makes sense, but keep it simple.
- ` appropriately. I’ll use `
- , sem headings, sem markdown)”. So I should use `
- `, just that if I use them, they should be those tags. I can structure with just `
- , without headings”. It doesn’t say I must use `
- ` only for very generic, indisputable points like “Atuação em campo onshore” or “Foco em prevenção de acidentes”. But I need to be cautious.
- `. I’ll use them for things that are clearly generic and truly standard, like “participação em treinamentos”, “coleta de dados de segurança”, etc., but phrased carefully.
- ` for requirements if I’m not sure. But the output format allows and expects `
- `: Maybe list key areas of focus (but without inventing specifics). I can list generic responsibilities that are standard, but phrased as “entre outras atividades inerentes ao cargo”. I need to be careful. The rule says “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 list typical things, but must frame them as general/standard, not as confirmed requirements for this specific vacancy unless implied.
- `. Maybe start with a paragraph about the company, then a list about the role, then a list about requirements/benefits (kept general), then a closing paragraph. All in Brazilian Portuguese.
- ` for lists of responsibilities/requirements. I need to make sure there are no heading tags.
- ` are allowed. I can use `
- , without headings”. So I need to structure the whole thing as paragraphs and lists, possibly nesting lists within paragraphs or using lists for bullet points, but no headings.
- `):**
Candidatar-se
Processo seletivo conduzido pelo empregador
