Skip to main content

RoleSage analysis feels generic

Symptom

RoleSage gives advice or summaries that feel too broad, repeat the job description, or miss what matters about the role.

Likely causes

  • The role description is too short or too generic.
  • Company, team, or role context is missing.
  • The role combines several different jobs.
  • Important constraints are implied but not written down.

Fix steps

  1. Add or update the role description with the work, outcomes, must-have skills, and constraints.
  2. Review the company and team context prompts used for the opening.
  3. Add role-specific context for what strong, acceptable, and weak evidence looks like.
  4. Save the context and regenerate the relevant analysis where the page offers that action.
  5. Review the skills, salary, and experience expectations before relying on match results.

What to include

Useful context is specific and observable:

  • "This team ships customer-facing Blazor features weekly."
  • "Azure experience matters more than generic cloud experience."
  • "The role requires mentoring two junior engineers."
  • "Commercial payroll domain experience is useful but not required."

Avoid vague instructions such as "find a great culture fit" unless you explain what that means for this role.

Related article

See Context prompts for hirer analysis for where this context is managed.