Skip to main content
Talent Portal helps company teams find builders whose visible skills, ecosystems, experience, projects, and intentions fit a role. Use it to build a better shortlist, then inspect each proof page before making contact. Talent Portal requires the Company plan, and you have to be an owner or admin of that company and be acting as it. On any other account the portal answers with an upgrade message instead of results, and the refusal is enforced by the API rather than only hidden in the interface.

​
Search the graph

  1. Open Company Hub → Talent Portal.
  2. Narrow the list with the toolbar: Ecosystem, Role, Skills, Intent, and Location, plus the Verified, Open to Work, Verified Experience, Recommended, and Has Projects toggles.
  3. Open the Skill map on a promising row to see the evidence behind a builder’s skills.
  4. Open the profile itself and check the underlying experience, projects, dates, recommendations, and connected accounts before you reach out.
The portal searches every builder on Dapping, not only your team or your followers. Only an ecosystem you choose narrows it; there is no implicit company scope. Ecosystem Tracker is the company-scoped surface.

​
What free accounts can still use

Search, location, skills, roles, intents, tags, sort, and minimum Karma stay free on the public builders feed. The six proof and ecosystem filters above, and the skill map, are the Company-plan part. Billing is handled by our team rather than a checkout, so a plan change starts with a conversation.

​
Use match context responsibly

Visible match reasons reflect the profile and search context available to Dapping. A missing match may only mean the builder has not added that detail. A strong match does not prove eligibility, availability, identity, or hiring fit. For a protocol engineer, combine the relevant ecosystem and skills with inspectable projects. For DevRel, look for ecosystem work, events, recommendations, and clear communication. For a grant or hackathon program, check shipped work and current intentions instead of treating one score or badge as a decision. Contact builders from their profile with a specific reason, company context, the role or collaboration goal, the expected commitment, and an official next step. Avoid mass messages, and never ask for wallet secrets or a transfer.

​
Continue on Dapping

Open your company workspace

Open Talent Portal from your company workspace to filter builders by skill, ecosystem, and availability.

Use Company Activity to track work and follow up

Use the company timeline to understand changes, assign follow-up, and keep public work current.

Use dApp Radar to scout and evaluate projects

Use visible project segments and evidence to build a focused scouting list for partnerships, DevRel, or BD.

Discover builders and understand open-to-work signals

Find builders and understand the availability signals they choose to show.
Last modified on August 8, 2026