Get Hired

Build proof before you send applications.

A practical guide for positioning, proof-of-work, portfolio packaging, outreach, trial tasks, interviews, compensation review, and scam checks.

Section 1

CV / ATS

Maintain two CV versions when useful: an ATS-safe version for portals and a more visual version for direct networking or portfolio review.

Template Structure
  • Headline: Target role + strongest proof
  • Proof links: 2-4 role-relevant artifacts
  • Experience bullets: action + scope + evidence
  • Skills: tools and concepts you can explain

Checklist

Avoid tables, text boxes, and columns for ATS submissions.
Use an ATS-safe version for portals and a separate visual version for networking when useful.
Put target role, proof links, tools, and outcomes near the top.
Use plain section headings such as Experience, Projects, Skills, Education, and Links.

Example

"For a Research Writer application, lead with a protocol memo, source appendix, and writing tools before general interests."

Compare CV formats
Section 2

Profile (Web2)

Make your public profile (LinkedIn/Twitter) answer three questions quickly: what role you want, what evidence proves it, and how someone can contact you.

Bio Template
  • I help [team type] with [role output].
  • Proof: [artifact 1], [artifact 2].
  • Tools: [tool list].
  • Contact: [email or profile link].

Checklist

Rewrite headline around the target role, not just generic terms.
Move proof links above generic bio text.
Use role keywords honestly and accurately.
Pin or feature one strongest artifact at the top of your profile.

Example

"Replace "Web3 enthusiast" with "Community operator: moderation SOP, weekly report template, and crisis-response flow.""

Review glossary terms
Section 3

On-chain Identity

In Web3, your on-chain activity is your truest resume. Curate your wallet history, ENS, and governance participation to reflect your professional focus.

On-chain Setup
  • Primary Wallet: Use a clean wallet for professional interactions.
  • ENS Domain: Acquire a readable .eth name (e.g., yourname.eth).
  • Badges: Collect relevant POAPs or Gitcoin Passports.
  • Governance: Vote on at least 2-3 DAOs related to your field.

Checklist

Separate your "degen/trading" wallet from your "professional/identity" wallet.
Ensure your professional wallet has a positive history (no interaction with sanctioned mixers).
Link your ENS or primary address on your CV/Profile.
Contribute to public goods (e.g., Gitcoin Grants) to show ecosystem alignment.

Example

"A DevRel candidate includes their wallet address showing active deployment of smart contracts on testnets and mainnet."

Explore on-chain identity
Section 4

Portfolio

Choose proof-of-work that matches the role, then package it as a short case study with context, decisions, output, limits, and next steps.

Case Study Flow
  • Context & Task
  • Final Output (put this first visually)
  • Decisions & Trade-offs
  • Assumptions & Limitations
  • Next iteration / Future scope

Checklist

Pick one strictly role-specific project brief.
Show the final output first so reviewers see the result immediately.
Explain decisions and trade-offs clearly.
Name assumptions and limitations to show mature thinking.

Example

"A designer shows the risky approval flow, final screens, missing states, and explains why each warning exists."

Choose a project
Section 5

Applications

Tailor your application to the specific protocol or company. Quality and relevance always beat sheer volume of applications.

Cover Note Structure
  • Hook: Why this protocol specifically?
  • Value: What exact problem can you solve for them?
  • Proof: Link to 1-2 highly relevant portfolio items.
  • Call to Action: Simple availability for a chat.

Checklist

Research the protocol's current roadmap or recent announcements.
Skip generic cover letters; write a 4-5 sentence targeted note.
Include links that do not require permission to view (e.g., public Notion, Figma, GitHub).
Double-check that you are applying for the correct timezone/region requirements.

Example

"Instead of "I am a hard worker", write "I noticed your upcoming V3 launch needs detailed documentation. I wrote a similar guide for Protocol X (link)."

View outreach templates
Section 6

Interviews

Web3 interviews often focus heavily on autonomy, async communication skills, and practical problem-solving over traditional behavioral questions.

STAR Method (Web3)
  • Situation: The decentralized/remote context.
  • Task: The ambiguity you faced.
  • Action: How you aligned the team async.
  • Result: The measurable on-chain or community impact.

Checklist

Prepare your background (lighting, audio) for Google Meet / Zoom.
Have 2-3 specific questions ready about their protocol or tokenomics.
Be ready to share your screen and walk through your portfolio live.
Be honest if you don't know a specific Web3 concept; eagerness to learn is valued.

Example

"When asked about conflict, frame it around resolving a disagreement in a public Discord channel or GitHub PR professionally."

Practice interview questions
Section 7

Compensation

Understand the nuances of getting paid in crypto, including stablecoins, native tokens, vesting schedules, and cliff periods.

Offer Evaluation
  • Base Salary: Typically paid in USDC/USDT or Fiat.
  • Token Grant: Amount, % of supply, or USD equivalent.
  • Vesting: e.g., 4 years total.
  • Cliff: e.g., 1 year before first tokens unlock.

Checklist

Always clarify if the token grant is based on a fixed number of tokens or a fixed USD value at grant time.
Understand the tax implications of receiving crypto in your local jurisdiction.
Verify the liquidity of the token (if it's already trading).
Ask about hardware/stipend budgets for remote work setups.

Example

"A strong offer might be $100k base (USDC) + 0.1% token supply vesting over 4 years with a 1-year cliff."

Learn about tokenomics
Section 8

Safety & Scams

The Web3 hiring space unfortunately has bad actors. Protect your identity, your hardware, and your crypto assets during the interview process.

Red Flag Checklist
  • Asking you to download unverified software (.exe, .scr) for a "test".
  • Requiring you to pay a "training fee" or buy their hardware.
  • Asking you to connect your wallet to a random testnet site they provide.
  • Communication entirely via Telegram without official email confirmation.

Checklist

Never run code or npm installs from a recruiter locally without sandboxing/VM.
Always verify email domains (e.g., @company.com vs @company-jobs.com).
Do not sign transactions with your main wallet for a coding test.
If it sounds too good to be true (e.g., $500/hr for basic data entry), it is a scam.

Example

"A fake recruiter sends a "game testing software". Running it executes a wallet drainer script in the background."

Read security guidelines