Short answer
Apply when the job workflow matches your evidence, then reference the case studies, tools, constraints, and collaboration style that make your fit clear.
- Decide if this page applies to: Builders choosing which AI jobs deserve an application.
- Check first: The workflow matches at least one credible case.
- Avoid this mistake: Applying only because the title says AI.
Use this page for
Turn ability into screenable proof
The point is not to list everything. Make it clear what you owned, what you can deliver, and which evidence needs protection.
Start
Decision context
Decision criteria
The workflow matches at least one credible case.
Next action
Browse jobs
Decision context
Use the job workflow as the filter. A strong application connects your case evidence to the employer's RAG, automation, agent, product, or implementation need.
Evidence to inspect
Mention the closest case, tools used, what you owned, what you would clarify, and any limits around data access or maintenance.
Boundary and next step
If the post is vague or risky, pause and clarify or report. Do not share private materials before the hiring context is credible.
What you still need to confirm yourself
- Confirm whether the role scope, budget, timeline, and communication expectations fit you.
- Decide what client names, screenshots, files, or personal details should stay private.
- Use interviews or written follow-up to clarify responsibility, contract terms, and data access before starting work.
Check current rules before acting
Use these links to confirm what the platform currently supports. Then decide whether to browse, post, contact, or adjust evidence.
Decision criteria
Common mistakes
- Applying only because the title says AI.
- Sending full private materials before trust context is clear.