Supervisor(A) De Customer Success (Saas)

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)
  – Do NOT invent specific facts not implied in the snippet or given fields
  – CAN use general sector-appropriate language, but treat assumptions as natural, 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 markers

  2. **Analyze the Input Data:**
  – **Position:** Supervisor(A) De Customer Success (Saas)
  – **Location:** Salvador, Bahia
  – **Snippet:** “Supervisor(A) De Customer Success (Saas) – Buscamos uma pessoa para assumir a supervisão da squad que cuida do nosso produto Saas, ajudando na estruturação de playbooks, processos e métricas da área, pensando na escala, no desenvolvimento do time e no crescimento da companhia. Responsabilidades e atribuições:- Mapear processos, encontrar possíveis gargalos e documentar playbooks das áreas- Fazer o acompanhamento do time de 4 pessoas, identificando pontos de atenção, melhoria e potencial na equi…”

  The snippet is cut off at “na equi…”. I need to be careful not to invent what comes after. I can only use what’s implied or explicitly stated.

  Explicit/Implied from snippet:
  – Role: Supervisor de Customer Success em SaaS
  – Responsibility 1: Map processes, find bottlenecks, document playbooks in the areas
  – Responsibility 2: Follow up on a 4-person team, identifying attention points, improvements, and potential in the team (cut off)
  – Context: Structuring playbooks, processes, metrics for scaling, team development, company growth
  – Location: Salvador, Bahia

  I must not invent:
  – Specific salary
  – False certifications
  – Invented benefits
  – Invented years of experience
  – The rest of the truncated sentence (e.g., “equipe”, “equipamentos”, etc.)

  I can use general, standard sector language that is appropriate but frame it as typical responsibilities, without claiming they are confirmed facts beyond what’s given. I need to be natural and professional.

  3. **Determine the Structure (HTML only,

  and

  /
  • ):**
    – I need to write a coherent job description in Portuguese.
    – Use paragraphs for narrative text.
    – Use unordered lists for responsibilities/requirements.
    – No headings (h1-h6), no markdown (no **, #, etc.).
    – Must be ~700 words in total HTML content.

    Let’s plan the content:
    – Opening paragraph: Present the company, the role, the context (SaaS, supervision, scaling).
    – Section on responsibilities: Use

    • items. I’ll list what’s explicitly stated and expand slightly with general, standard CS supervisor responsibilities, but carefully worded so they’re not presented as absolute facts from the snippet, but as typical duties. I’ll make sure to stay close to the snippet: “Mapear processos, encontrar possíveis gargalos e documentar playbooks das áreas” and “Fazer o acompanhamento do time de 4 pessoas, identificando pontos de atenção, melhoria e potencial na equi…” I’ll complete the thought naturally but without inventing specifics. Actually, rule 1 says: “NÃO invente fatos específicos que não estejam implícitos no trecho fornecido ou nos campos dados”. So I should not complete the truncated sentence with made-up content. I can rephrase it generally or leave it as is, but I need to fill ~700 words. I need to be very careful.

      Let’s re-read rule 1 carefully: “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.”
      Rule 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.”
      Rule 3: “Mantenha o texto verdadeiro, profissional e legível — pensando em uma pessoa real decidindo se deve se candidatar.”
      Rule 4: Portuguese BR, natural, clear.
      Rule 5: ~700 words.
      Rule 6: Output ONLY the HTML, no title, no intro, no code block markers.

      So I can use general sector language, but I must not treat assumptions as confirmed facts. I need to blend the explicit snippet with general, appropriate descriptions, but always make it clear they are typical/expected, not extracted from the snippet beyond what’s there.

      Actually, I think the way to handle the truncated part is to either stop before it or generalize very safely. But I need ~700 words. That’s a lot for a job ad expansion from a tiny snippet, while respecting the no-invention rule.

      Let’s think: The snippet has maybe 30-40 words. Expanding to 700 words while strictly not inventing specific facts is extremely challenging. I need to generate a lot of content that is generic but appropriate, and make sure every specific claim either comes from the snippet or is a very general, non-specific statement that doesn’t violate the rule.

      Key: I can describe the role, the company context, the industry (SaaS Customer Success), the location, the general nature of the responsibilities without inventing numbers, names, specific certifications, etc. I can use phrases like “entre outras”, “entre as atribuições esperadas”, but I need to be careful.

      Actually, rule 2 says I CAN use general sector language appropriate to the cargo, as long as I don’t treat suppositions as confirmed facts. So I can write things like “Entre as responsabilidades comuns a essa função em empresas de SaaS, destaca-se a…” but wait, that might be treating suppositions as facts. Better: I’ll structure it as a natural job description, using the explicit points as anchors, and filling the rest with very generic, plausible but not invented specifics. For example: “O profissional atuará na gestão de uma equipe multidisciplinar, colaborando com o alinhamento de estratégias e o aprimoramento de processos internos.” This is generic but not invented from the snippet.

      Let’s outline the HTML content:
      – I’ll start with a paragraph introducing the vacancy, using the given cargo and location.
      – Then a paragraph about the company/industry context (SaaS, Customer Success), very generically.
      – Then a

      • list of responsibilities. I’ll include the two explicit ones from the snippet, and add a few more that are very generic and phrased carefully. I’ll make sure not to say “4 people” if I’m not sure, but the snippet says “time de 4 pessoas”. I can reference that: “acompanhamento de uma equipe de aproximadamente 4 pessoas” – that’s directly from the snippet, so it’s okay. I’ll be exact about what’s in the snippet.
        – Then a
        • list of requirements/qualifications. Again, I’ll use very generic language, maybe referencing “experiência em Customer Success ou áreas correlatas” but without inventing years. Rule 1 says “sem exigências de anos de experiência inventadas”. So I can say “experiência prévia na área” but not “5 anos”. I’ll avoid specific numbers.
          – Maybe another paragraph about the goals: scaling, team development, company growth (all from snippet).

          I need to reach ~700 words. That’s a lot of HTML paragraphs and list items. I’ll need to be very descriptive but generic.

          Let’s calculate: 700 words in HTML with

          and

          /
          • . Each

            can be ~50-80 words.

          • items ~30-40 words. I can generate many paragraphs and lists.

            Critical: I must not invent. So I’ll stick to what’s given or extremely general. I’ll avoid “salary”, “benefits”, “specific certifications”, “exact years”. I’ll use phrases like “atividades inerentes à função”, “experiências que agregam”, etc.

            Let’s start drafting mentally, then write the HTML.

            Structure:

            …opening…

            • …responsibility 1 from snippet…
            • …responsibility 2 from snippet…
            • …general CS supervisor duty #3…
            • …general CS supervisor duty #4…

            …more about the role…

            • …requirement 1…
            • …requirement 2…
            • …requirement 3…

            …location, goals…

            • …maybe some “diferenciais” but generic…

            Wait, I need to ensure I don’t

            • Localização: Salvador, Bahia
            • Categoria da Vaga: Outras vagas
            • Tags da Vaga: Salvador