Why pre-screen web3 strategists before the portfolio review
The interface problems in this space are unusual and unforgiving. A user must install a wallet, safeguard a phrase that cannot be recovered, hold a second asset to pay fees, and sign transactions that cannot be reversed. Most people stop at the first step. Strategists worth hiring know their drop-off points by stage. A short screen asks where users actually gave up.
What actually matters when screening Web3 Experience Strategist candidates
- 01
Portfolio
Review shipped web3 work: wallet connect flows, NFT mint journeys, DAO governance dashboards or DeFi onboarding. Ask for live dApp links, user counts and drop-off rates at signing steps.
- 02
Craft and rationale
Test reasoning behind gas fee disclosure, seed phrase custody choices, transaction signing copy and progressive disclosure for non-crypto users. Probe why they chose custodial versus self-custody patterns.
- 03
Feedback and iteration
Ask how they responded to Discord feedback, testnet user sessions, token holder complaints or analytics from Dune dashboards, and what they changed after launch.
- 04
Working with the brief
Probe collaboration with smart contract engineers and token economists: how they scoped experience strategy against protocol constraints, audit timelines and treasury or roadmap limits.
Pre-screening questions to ask Web3 Experience Strategist candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Reached real users
3 questions01Can you share examples of projects you have led and what the outcomes were?
Listen forProducts that reached users beyond the existing community, with retention rather than launch numbers.
Success measured by launch activity, or user numbers that collapsed after an incentive ended.
02Can you describe your experience designing or delivering token-based products?
Listen forProducts with a use beyond speculation, and honesty about what happened to activity over time.
Projects justified entirely by trading activity, or long-term usage never examined.
03Do you have experience with decentralised organisations and their governance?
Listen forReal participation with an honest account of low turnout and concentration of voting power.
Governance described as functioning well, or voter concentration not acknowledged.
Technically grounded
3 questions04Can you explain how decentralised applications differ from conventional ones?
Listen forThe practical differences understood, including confirmation latency, cost per action and irreversibility.
Differences described ideologically, or transaction cost and confirmation time not mentioned.
05Could you share your experience working with smart contracts?
Listen forEnough understanding to know what a contract can change after deployment and what it cannot.
Contracts treated as ordinary backends, or upgradeability assumed to be always available.
06What experience do you have working directly with contract and application developers?
Listen forDesign constraints negotiated with developers, with a proposal changed because of a technical limit.
Designs handed over as requirements, or technical objections treated as obstacles.
Onboarding designed
3 questions07Can you describe designing interfaces for decentralised applications?
Listen forWallet connection, transaction signing and failure states all designed for people unfamiliar with them.
Interfaces that assume wallet familiarity, or failed transactions with no explanation to the user.
08How would you explain these technologies to a client with no technical background?
Listen forExplanation in terms of what changes for the user, without jargon or ideological framing.
Explanations built on terminology, or benefits asserted that the technology does not deliver.
09What strategies do you use to make these concepts accessible to a general audience?
Listen forComplexity hidden where possible, with the parts users genuinely must understand taught carefully.
Education treated as the answer to bad onboarding, or complexity presented as unavoidable.
Risk communicated
3 questions10How do you approach risk when building strategy in this space?
Listen forIrreversibility, key loss and contract risk designed against, with warnings placed where they matter.
Risk handled by terms and conditions, or irreversibility treated as a feature to communicate.
11What challenges have you encountered in this space, and how did you handle them?
Listen forReal difficulties such as user losses, failed transactions or a market collapse, handled honestly.
Challenges described as regulatory hostility, or user losses not treated as a product problem.
12Do you have experience prototyping these solutions before committing to build?
Listen forPrototypes tested with people outside the community, with the results changing the direction.
Testing done only with existing users, or prototypes used to validate rather than investigate.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Portfolio
35%5Shows named live products with wallet activation numbers, seed phrase onboarding flows and measurable reductions in transaction abandonment.
Craft and rationale
25%5Explains each flow decision against user trust, irreversibility of on-chain actions and specific wallet constraints like MetaMask or Rainbow.
Feedback and iteration
25%5Cites concrete revisions driven by community feedback or on-chain data, including flows they abandoned when metrics contradicted their assumptions.
Working with the brief
15%5Translates protocol and contract limitations into a clear experience strategy, negotiating scope with founders and engineers without vague crypto jargon.
Install a wallet, guard an unrecoverable phrase, hold a second asset for fees. A one-way video screen asks where users stopped.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for this role take?
Fifteen minutes across eight to ten questions, answered async, alongside a portfolio. Enough to establish shipped products, test technical grounding, and check onboarding and risk thinking.
How technical does this role need to be?
Enough to know what a transaction actually does and what a contract can and cannot change afterwards. Without that, the strategy will promise things the technology does not support.
Evaluating answers
What is the strongest signal when screening this role?
Knowing where users dropped out. Strategists who shipped to real users measured the funnel by stage. Anyone describing an engaged community has worked with people already comfortable with this.
What should worry me in an answer?
Treating irreversibility as a feature to explain rather than a design problem to mitigate. Users lose money to that, and a strategist who has not designed against it will let it happen.
Go deeper on this role
Sanat has been hiring since 2012 and watching the recruitment industry change up close ever since, and turned that screening process into Hirevire's video screening platform. LinkedIn
