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, using only `
` and `
- /
- `. No headings, no markdown, no extra text.
– **Rules:**
– Don’t invent specific facts not implied in the snippet or provided fields.
– Can use general/sector-appropriate language for the role (e.g., “Operador de Empilhadeira” duties), but present as natural, not as 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 markers.2. **Analyze the Input Data:**
– **Cargo:** Coordenador de Produção
– **Empresa:** ALIANCA R H CONSULTORIA EMPRESARIAL LTDA
– **Localização:** Salvador, Bahia
– **Salário:** R$32,133 – R$32,133 / year (note: this is annual, which is very high for Bahia/Brazil, but I must stick to what’s given; however, rule 1 says “without salary values fabricated beyond what was informed”. The snippet says “2677,82” weekly/monthly? The annual is given as R$32,133. I need to be careful. The snippet says “Salário: 2677,82” and the data field says “R$32,133 – R$32,133 / year”. These don’t match. 2677.82 * 12 = ~32,133.84. So likely the weekly or monthly salary is 2677.82, and annual is 32,133. I should probably reference the annual figure as given, or use the snippet’s number cautiously. Rule 1: “without salary values fabricated beyond what was informed”. I have two salary figures. I should probably just use the annual one as given in the structured data, or mention the monthly/weekly from the snippet if implied. But I need to be consistent. Let’s look: snippet says “Salário: 2677,82”. Data says “R$32,133 – R$32,133 / year”. I think the annual is the official one. I’ll use the annual figure, and maybe mention it’s a competitive annual compensation, but without inventing details. Actually, rule 1 says “without salary values fabricated beyond what was informed”. I have both. I’ll stick to the annual R$32.133 as given in the data field, and not invent monthly/weekly unless implied. But the snippet has 2677.82. I could mention “compatível com salário anual de R$32.133” or just focus on the role. To be safe, I’ll reference the salary as informed: R$32.133 per year, and not make up monthly amounts. I can say “remuneração anual de R$ 32.133” as given.
– **Localização:** Salvador, Bahia
– **Salário field:** R$32,133 – R$32,133 / year– **Snippet details:**
– Local de trabalho: Aeroporto de Salvador/Ba
– Salário: 2677,82 (likely weekly or monthly, but data says annual 32133)
– Escala: 6×1 – Horário: 08h as 16:20h
– Vale transporte
– Refeição no local
– Atividades: Coordenar e controlar a realização dos processos sob sua responsabilidade, assegurando a maximização da produtividade e cumprimento das normas de qualidade e a satisfação do cliente; Coordenar as atividades da equipe de funcionários a fim de cumprir com os requisitos do processo e cliente; Organizar turnos e designar ativ…3. **Determine the Approach:**
– I need to expand this into a full job description.
– Must not invent specific facts. So I can’t say “requires 5 years experience” unless implied. The snippet says “Organizar turnos e designar ativ…” – truncated. I can generalize responsibly: “Organizar turnos e designar atividades” is fine as a general duty of a Production Coordinator.
– I can use standard sector language for “Coordenador de Produção” in Brazil, but keep it general and not presented as confirmed requirements beyond what’s there.
– Must be ~700 words in HTML, using only `` and `
- /
- `. No headings. So I’ll write paragraphs and lists.
– Language: Portuguese do Brasil, natural, clear.
– Output ONLY HTML, no title, no intro, no code block markers. Just the HTML content.Let’s plan the HTML structure:
– I’ll use `` for paragraphs of description.
– `- ` for lists of responsibilities, benefits, requirements (if I can infer reasonably without inventing).
– I need to be careful about “requirements”. The snippet doesn’t list explicit requirements like education or experience. I can use general, standard language that’s typical for the role, but framed as “entre outras” or “entre as principais”, and not as absolute facts. Rule 2: “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’ll phrase things like “Entre as responsabilidades, espera-se…” or “O profissional deverá…” but carefully. Actually, I should probably avoid listing “requirements” that aren’t in the snippet, or if I do, make them very generic and clearly implied. Better to focus on responsibilities and benefits as given, and use general phrasing.Let’s extract what’s solid:
– Company: ALIANÇA R H CONSULTORIA EMPRESARIAL LTDA
– Location: Salvador, Bahia (specifically Aeroporto de Salvador/Ba)
– Work scale: 6×1, 08h to 16:20h
– Benefits: Vale transporte, refeição no local
– Salary: R$32.133 / year (annual) – I’ll use this. The snippet says 2677.82 which likely weekly/monthly, but I’ll stick to the annual figure as given in the data field, and maybe mention “remuneração compatível com o mercado” or just state the annual figure. To avoid conflict, I’ll state “Remuneração anual de R$ 32.133,00” as given. I won’t break it down monthly/weekly unless the snippet implies it, but I can just say “according to the offered terms”.
– Responsibilities from snippet: Coordenar e controlar processos, maximizar produtividade, cumprir normas de qualidade, satisfazer cliente; Coordenar atividades da equipe; Organizar turnos e designar atividades.I need to expand to ~700 words. That’s quite long for a job ad HTML with only
and
- /
- . I need to generate substantial but reasonable text. I’ll write multiple paragraphs describing the company, the role, responsibilities (expanded generally but grounded in the snippet), benefits, profile/expectations (general), and application info. I must ensure I don’t invent specific certifications, exact years of experience, etc. I can say “experiência na área” generally, or “conhecimentos em…” but carefully.
Let’s outline the HTML content (mental):
– Paragraph introducing the company and location.
– Paragraph about the role.
– List of responsibilities (using- ), each phrased generally, derived from snippet.
– List of benefits (vale transporte, refeição no local, scale/hours).
– Maybe a general profile section, but kept vague.
– Closing paragraph about application.Word count target: ~700 words. In HTML with
and
- , I need to generate a lot of text. I’ll aim for depth but staying truthful.
Important: No headings. So no
,
, etc. Only
and
- /
- . I can have multiple
and one
- block.
Let’s start drafting text in Portuguese, keeping it professional.
I need to ensure I don’t invent salary details beyond what’s given. The data says “R$32,133 – R$32,133 / year”. I’ll write: “A empresa oferece remuneração anual de R$ 32.133,00, conforme informado.” I won’t specify monthly/weekly. The snippet says 2677.82, which is likely the weekly or monthly amount (2677.82 * 12 = 32133.84, so if weekly, *52 = 139,255, too high; if monthly, *12 = 32,133.84, matches). So probably
- block.
- . I can have multiple
- , I need to generate a lot of text. I’ll aim for depth but staying truthful.
- ), each phrased generally, derived from snippet.
- . I need to generate substantial but reasonable text. I’ll write multiple paragraphs describing the company, the role, responsibilities (expanded generally but grounded in the snippet), benefits, profile/expectations (general), and application info. I must ensure I don’t invent specific certifications, exact years of experience, etc. I can say “experiência na área” generally, or “conhecimentos em…” but carefully.
- ` for lists of responsibilities, benefits, requirements (if I can infer reasonably without inventing).
- `. No headings. So I’ll write paragraphs and lists.
Candidatar-se
Processo seletivo conduzido pelo empregador