Skip to main content
Talent Portal filters on evidence rather than self-description: the Verified Experience toggle reads roles a named company confirmed, not roles someone typed. Inspect each proof page before making contact. The proof filters, the skill map, and job-to-candidate matching are for owners and admins of a company, acting as that company. Select one your hub’s plan does not cover and you get a prompt in place of results. Availability depends on your company’s plan. See pricing.

​
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, Has projects, Recommended by peers, Attested event role, and Publishes writing 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 stays open to everyone

Search, location, skills, roles, intents, tags, sort, and minimum Karma are open to everyone on the public builders feed. The proof and ecosystem toggles above, and the skill map, are the part that depends on your company’s plan.

​
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, and a strong match does not prove eligibility 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

Review company engagement and published-listing performance, then follow up from the source.

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 September 21, 2026