Short answer
Choose the category by the work to be delivered: automation, agent workflows, RAG, product implementation, Dify/Coze bot building, Cursor development, or AI implementation consulting.
- Decide if this page applies to: Employers who know the business problem but not the right AI Builder role.
- Check first: The category matches the core workflow rather than a keyword.
- Avoid this mistake: Choosing a category from a tool name alone.
Use this page for
Make the next action smaller
Use this page to decide whether to browse, post, rewrite the brief, or check rules instead of collecting more background.
Start
Decision context
Decision criteria
The category matches the core workflow rather than a keyword.
Next action
View category guides
Decision context
Start from the workflow: moving data between systems suggests automation, knowledge retrieval suggests RAG, multi-step tool use suggests agents, and product UI work suggests AI product or Cursor development.
Evidence to inspect
Use category pages and case studies to compare tool stacks, deliverables, maintenance needs, and what the Builder personally owned.
Boundary and next step
A category narrows the search but does not replace case-study review. Many strong Builders span two categories, so evaluate evidence against the main workflow.
What you still need to confirm yourself
- Confirm budget, timeline, contract terms, and legal or compliance needs outside the Resource page.
- Interview the Builder and discuss how they would handle data access, quality checks, maintenance, and handoff.
- Make the final hiring decision yourself; platform evidence is a starting point, not a substitute for judgment.
Decision criteria
Common mistakes
- Choosing a category from a tool name alone.
- Combining automation, RAG, agent, and product work without deciding what matters first.