Engenheiro de software

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, using only `

` and `

/
• `. No headings, no markdown, no extra text.
  – **Constraints:**
  – Don’t invent specific facts not implied in the snippet or given 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, clear, no unnecessary anglicisms.
  – Target size: ~700 words.
  – Output ONLY the HTML description, no title, no intro, no code block marking.

  2. **Analyze the Input Data:**
  – **Cargo:** Engenheiro de software
  – **Empresa:** Innovação Consultoria
  – **Localização:** Ilhéus, Bahia
  – **Trecho original (truncado):**
  – “Atuará nas atividades internas e demais funções pertinentes ao cargo.”
  – “Necessário conhecimento na área de atuação.”
  – “Formação Acadêmica: Não informado”
  – “Salário: A combinar”
  – “Cargo: Engenheiro de software” (duplicate)
  – “Empresa: Innovação Consultoria” (duplicate)
  – “Atividades de consultoria em gestão empresarial, exceto consultoria técnica específica.”
  – “Ramo: Recursos Humanos/ Recrutamento e seleção (BG)”

  Wait, let me re-read the “Trecho original (truncado) do agregador de vagas” carefully:
  – “Atuará nas atividades internas e demais funções pertinentes ao cargo.”
  – “Necessário conhecimento na área de atuação.”
  – “Formação Acadêmica: Não informado”
  – “Salário: A combinar”
  – Then it repeats: “Cargo: Engenheiro de software Empresa: Innovação Consultoria”
  – “Atividades de consultoria em gestão empresarial, exceto consultoria técnica específica.”
  – “Ramo: Recursos Humanos/ Recrutamento e seleção (BG)”

  There’s some inconsistency/confusion in the snippet. It mixes software engineering with “consultoria em gestão empresarial” and “Ramo: Recursos Humanos/ Recrutamento e seleção”. The company is “Innovação Consultoria”. The location is “Ilhéus, Bahia”.

  I need to expand this into a job description for a “Engenheiro de software” at “Innovação Consultoria” in “Ilhéus, Bahia”, but I must NOT invent facts not implied. I can use general standard language for the role, but I must be careful not to say things like “requires 5 years experience” if not implied, or invent salary, certifications, etc.

  Let’s extract what’s implied/fact:
  – Role: Engenheiro de software
  – Company: Innovação Consultoria
  – Location: Ilhéus, Bahia
  – General duty: “Atuará nas atividades internas e demais funções pertinentes ao cargo” -> will perform software engineering tasks, internal activities, etc.
  – Requirement: “Necessário conhecimento na área de atuação” -> knowledge in the field/area of expertise
  – Education: “Não informado” -> not specified, so I shouldn’t state a specific degree, but can mention “formação na área” generally without specifying level, or keep it vague as per the snippet.
  – Salary: “A combinar” -> salary to be combined, don’t invent a number.
  – Additional text: “Atividades de consultoria em gestão empresarial, exceto consultoria técnica específica.” -> This seems odd for a software engineer, but it’s in the snippet. The company is a consultancy. Maybe the role involves some consulting aspects, but not technical-specific consulting. I should weave this in naturally but not overstate. Maybe the engineer will participate in business consulting related to software solutions, but excluding deep technical consulting? I need to be careful.
  – “Ramo: Recursos Humanos/ Recrutamento e seleção (BG)” -> This seems like the industry/segment of the aggregator or the company’s division. The company is “Innovação Consultoria”, and this might be their HR/recruitment segment. But the role is Software Engineer. I should probably mention the company operates in consultancy/HR tech or similar, but not invent. I can refer to the company’s area of operation as given, but keep it general.

  Actually, looking at the snippet again, it might be that the job aggregator mixed multiple fields. But my job is to expand it into a coherent job ad, following the rules. I must not invent facts. I can use “standard sector language” appropriate to the cargo. For a software engineer, that means typical responsibilities: development, testing, collaboration, etc., but I must frame them as general, not invented specifics.

  Let’s list what I can safely include:
  – Job title: Engenheiro de software
  – Company: Innovação Consultoria
  – Location: Ilhéus, Bahia
  – Core responsibility: “Atuará nas atividades internas e demais funções pertinentes ao cargo” -> I can describe this as performing software development tasks, participating in projects, collaborating with teams, etc., using generic phrasing.
  – Requirement: “Necessário conhecimento na área de atuação” -> knowledge in software engineering/related field.
  – Education: Not specified -> I can mention “formação na área” generally, but avoid specifying degree type or years. I’ll keep it vague: “Formação na área de tecnologia da informação ou relacionada” – wait, the rule says “NÃO invente fatos específicos que não estejam implícitos”. The snippet says “Formação Acadêmica: Não informado”. So I should NOT state a specific formation. I should either omit it or say “Não especificada” or keep it very general without claiming a degree. To be safe, I’ll refer to “formação na área” but without committing to a specific level, or just say “experiência ou formação na área” – but “experiência” isn’t specified either. The snippet only says “Necessário conhecimento na área de atuação”. I’ll stick to that: “Conhecimento na área de atuação”. I won’t add “ensino superior” etc.
  – Salary: “A combinar” -> I’ll mention “Remuneração a combinar” at the end, as per snippet.
  – “Atividades de consultoria em gestão empresarial, exceto consultoria técnica específica.” -> This is tricky. The role is Software Engineer, but the company does business management consulting, excluding technical consulting. I can frame it as: the engineer will support consultancy projects, possibly involving software solutions for business management, but the role focuses on software development/engineering, not direct technical consulting. I’ll phrase it carefully: “Participação em projetos de consultoria em gestão empresarial, com foco no desenvolvimento de soluções de software, sem execução de consultoria técnica específica.” But I must ensure I’m not inventing that the role *will* do this if it’s not implied. The snippet lists it as part of the vagal context, maybe as company info. I’ll treat it as part of the company’s activity that the role supports, but keep it generic and natural.
  – “Ramo: Recursos Humanos/ Recrutamento e seleção (BG)” -> This might mean the company’s segment is HR/recruitment. But the role is Software Engineer. Maybe it’s an HR tech company. I’ll refer to the company’s atuação em consultoria/recrutamento, but keep it vague. Actually, I might just say the empresa atua em consultoria, sem entrar em detalhes de ramo que não são do cargo, or I can mention “Atuação em consultoria” generally.

  Wait, the rules say: “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 for a Software Engineer, I can use standard responsibilities like “desenvolvimento de software”, “testes”, “colaboração em equipe”, etc., but I must not present them as confirmed facts about this specific job if they aren’t in the snippet. I can say “entre as atividades, o profissional poderá atuar no desenvolvimento e na manutenção de sistemas…” but carefully, as if it’s typical, not guaranteed. Actually, the rule says “não trate suposições como fatos confirmados”. So I should phrase them as possibilities or general descriptions, not as “the job requires you to do X”. I’ll use language like “Atividades podem incluir…” or “O profissional deverá…” but without overcommitting. Hmm, but a job ad typically lists responsibilities. The rule allows “linguagem geral e padrão do setor”, so I think it’s okay to describe typical software engineer duties, as long as I don’t invent specifics like “5 years” or specific tools not mentioned. I’ll keep it broad and generic.

  Let’s 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,

  • Empresa: Innovação Consultoria
  • Localização: Ilhéus, Bahia
  • Categoria da Vaga: Unknown
  • Tags da Vaga: Ilhéus