Describe a role in plain English. You get assessment topics back from
the catalogue, and anything missing is flagged for the team.
Describe the role the way you would to a colleague —
"hiring a senior data engineer, needs Python, Spark and dbt".
You don't need to list skills one per line; a sentence works.
Each conversation is locked to the role you start it
with. That keeps the topics for one role together, so you can come
back later and find them. Asking about a different role shows a
prompt to start a new conversation — your current one is never
overwritten.
The closest topic we carry isn't close enough to be a
confident answer. Treat it as a suggestion rather than a match — and
it's already been logged so the team can review the gap.
That's expected and useful. Anything we don't carry is
recorded along with how often it's asked for, which is how the
catalogue decides what to add next. You don't need to report it.
Yes — pick it from Recent in the left sidebar.
Each one keeps its full history and the role it's filed under.
Name specific technologies rather than categories —
"PostgreSQL" beats "databases". Include seniority
if it matters; it shapes which topics are suggested.