KRAFTJobs
Get Hired

From understanding Web3 to your first role.

A practical journey you can follow at your own pace. KRAFT provides educational guidance and structure. It does not guarantee employment, and finishing the journey is not a promise of a job.

Choose your starting path

Everyone runs the same journey, but the emphasis differs by where you start. Pick the path closest to you.

No previous experience

New to Web3 with no prior related work.

  1. Build a clearly-labeled simulated proof-of-work project.
  2. Get real experience through volunteer or contributor work.
  3. Turn the work into a portfolio case study.
  4. Apply to entry-level roles that match your evidence.

Volunteering and contributor work are a common beginner path, not a requirement. A clearly-labeled simulated project still counts as evidence.

Transferable Web2 skill

You already have a professional skill from non-Web3 work.

  1. Translate your existing skill into a Web3 context.
  2. Build one Web3-specific proof artifact.
  3. Send targeted applications that lead with the skill you already have.

Lead with the skill you already have and add one Web3-specific artifact, rather than restarting from zero.

Existing Web3 experience

You have some Web3 experience and want to specialize or move up.

  1. Improve the evidence behind your existing work.
  2. Show measurable outcomes and clear ownership.
  3. Apply to a more specialized or senior role.

Replace activity claims with outcomes and ownership, and target depth over breadth.

The 13-stage journey

Each stage has an objective, what to do, the output to produce, a common mistake to avoid, and a clear signal that you are ready for the next stage.

  1. Stage 1 of 13

    Understand how Web3 teams work

    Build an accurate mental model of how Web3 teams operate before choosing a role.

    What to do

    • Learn wallets, transactions, and safety basics.
    • See how protocols, DAOs, and companies are structured and ship work.
    • Notice how contributor, contractor, freelance, and full-time work differ.

    Expected output

    A short written summary of how a Web3 team ships work and where roles sit.

    Common mistake: Chasing a title or token price before understanding the actual work.
    Done when: You can explain what different Web3 teams do and how work gets shipped.
    Learn the basics

  2. Stage 2 of 13

    Choose one realistic target role

    Pick a single role that matches your interests, current evidence, and the work you want to do.

    What to do

    • Compare roles by the actual work, not the title.
    • Read the scope and boundary notes on the role guide.
    • Use the Skill Check if several paths look plausible.

    Expected output

    One target role with a note on why it fits and what it does not cover.

    Common mistake: Keeping every option open instead of committing to one target.
    Done when: You can name one role and describe its scope and boundaries.
    Browse the role directory

  3. Stage 3 of 13

    Learn the minimum foundations for that role

    Learn only the prerequisites the target role actually needs next.

    What to do

    • Open the role guide's skills and prerequisite knowledge.
    • Use role-linked learning resources.
    • Skip material you can already prove.

    Expected output

    Notes or small exercises covering the role's prerequisite knowledge.

    Common mistake: Collecting courses and certificates instead of building toward the role's evidence.
    Done when: You can complete a scoped task in the role's area with review.
    Find role-linked learning

  4. Stage 4 of 13

    Study the actual outputs expected from the role

    Understand the deliverables and quality signals the role is judged on.

    What to do

    • Read the role's deliverables, success signals, and proof standards.
    • Find real examples of the artifact the role produces.
    • Note what a strong version looks like versus weak evidence.

    Expected output

    A clear list of the artifacts you will need to produce.

    Common mistake: Confusing activity with the deliverables reviewers actually inspect.
    Done when: You know what a strong version of the role's main artifact looks like.
    See the role guide

  5. Stage 5 of 13

    Build a simulated proof-of-work project

    Produce one role-relevant artifact using a realistic, clearly simulated scenario.

    What to do

    • Pick the role's portfolio brief.
    • Work from public sources and label the work as simulated.
    • Follow the brief's rubric and name your assumptions.

    Expected output

    One completed, clearly-labeled simulated project matching the role's deliverables.

    Common mistake: Presenting simulated work as real client or protocol experience.
    Done when: Your artifact meets the brief's rubric and names its assumptions.
    Open a portfolio brief

  6. Stage 6 of 13

    Get experience through contribution

    Gain real experience through volunteering, contributing, freelance work, internships, or self-initiated projects.

    What to do

    • Find contributor, bounty, or small freelance opportunities.
    • Keep scope, ownership, and payment terms clear before starting.
    • Document what you personally did.

    Expected output

    At least one piece of real, attributable work with clear ownership.

    Common mistake: Treating volunteering as mandatory, or accepting unpaid production disguised as a trial.
    Done when: You have real work you can describe honestly, kept distinct from simulated projects.
    Find contributor sources

  7. Stage 7 of 13

    Turn the work into a clear portfolio case study

    Package your strongest work as a case study that shows decisions, not just output.

    What to do

    • Use context, task, decisions, constraints, output, and limitations.
    • Distinguish simulated work from real contributor or professional work.
    • Redact private user, company, security, or compensation data.

    Expected output

    One case study a reviewer can evaluate in a few minutes.

    Common mistake: Showing the artifact with no context, ownership, or limitations.
    Done when: A reviewer can understand what you owned and why it matters.
    Package a case study

  8. Stage 8 of 13

    Improve profile, CV, and role positioning

    Make your profile, CV, and positioning answer the target role quickly.

    What to do

    • Use an ATS-safe CV for portals and a visual version for networking.
    • Lead with the target role and your strongest proof.
    • Keep creative work in a portfolio, not buried in the CV.

    Expected output

    A role-targeted CV and profile that lead with evidence.

    Common mistake: Generic “Web3 enthusiast” positioning with no proof near the top.
    Done when: Someone can tell your target role and evidence within seconds.
    Open the profile playbook

  9. Stage 9 of 13

    Build a target list of projects and teams

    Assemble a focused list of teams whose work and scope match your evidence.

    What to do

    • Use job boards and ecosystem directories to discover teams.
    • Verify each opening on the company's official domain.
    • Note why each team fits your target role and level.

    Expected output

    A short, qualified list of teams and roles worth pursuing.

    Common mistake: Mass-listing companies with no fit check or verification.
    Done when: Each target has a clear reason and a verified official source.
    Discover teams and boards

  10. Stage 10 of 13

    Use targeted outreach and relevant applications

    Apply and reach out selectively where level, work type, and proof match.

    What to do

    • Tailor the opening, evidence, and questions to the role.
    • Contact a relevant person with one clear reason and one proof link.
    • Avoid mass DMs and rewriting your whole identity per listing.

    Expected output

    Tailored applications and outreach tied to specific roles.

    Common mistake: Spraying generic messages or applications with no relevance.
    Done when: Your applications reference the role and attach relevant proof.
    Review application guidance

  11. Stage 11 of 13

    Prepare for interviews and trial tasks

    Practice role-specific questions and confirm trial-task scope before starting.

    What to do

    • Practice the target role's interview questions with real examples.
    • Prepare to show trade-offs, limitations, and what you owned.
    • Confirm trial scope, time, ownership, and payment before you begin.

    Expected output

    Prepared answers built from real work and clear trial-task boundaries.

    Common mistake: Memorizing scripts, or accepting an unbounded unpaid trial.
    Done when: You can answer role questions with evidence and have clarified any trial scope.
    Practice interviews

  12. Stage 12 of 13

    Review the offer, scope, payment terms, and safety risks

    Evaluate an offer by separating cash, tokens, scope, and risk before deciding.

    What to do

    • Separate cash, token, vesting, and employment type.
    • Confirm the payment schedule and contractor-versus-employee terms.
    • Verify domains and never share a seed phrase or pay to apply.

    Expected output

    A clear breakdown of the offer's real terms and any risks.

    Common mistake: Treating token or bonus value as guaranteed salary, or skipping safety checks.
    Done when: You understand exactly what you are agreeing to and confirmed it is safe.
    Read safety and offer notes

  13. Stage 13 of 13

    Onboard into the first role and document the work

    Start well by learning the team's systems and documenting your work from day one.

    What to do

    • Learn the team's tools, norms, and decision rights.
    • Keep a running record of what you own and ship.
    • Turn early work into future evidence and references.

    Expected output

    A working rhythm and a running record of your contributions.

    Common mistake: Not documenting decisions, which makes future evidence and reviews harder.
    Done when: You are shipping scoped work and can show what you did.
    Revisit your role guide

Application playbook

Reference guidance for the application stages - profile, CV, outreach, trials, interviews, compensation, and safety.

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.

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

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.

Profile

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

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

Checklist

  • Rewrite headline around the target role
  • Move proof links above generic bio text
  • Use role keywords honestly
  • Pin or feature one strongest artifact

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.

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

Checklist

  • Pick one role-specific project brief
  • Show the final output first
  • Explain decisions and trade-offs
  • Name assumptions and limitations

Applications

Apply selectively to roles where level, work type, timezone, compensation model, and proof requirements match your current evidence.

Example: Skip senior protocol economist roles if your current proof is entry-level community work.

Checklist

  • Check role level
  • Check timezone and employment type
  • Verify company domain
  • Attach the most relevant proof link

Outreach

Write targeted outreach that references a real reason for contacting the team and includes one relevant proof link.

Example: I saw your wallet onboarding issue in support channels; here is a small UX audit of the flow.

Checklist

  • Reference real work or context
  • Attach one proof link
  • Ask a specific question
  • Keep the message short

Trials

Trial tasks can be useful, but scope, expected time, ownership, payment, and evaluation criteria should be clear before you begin.

Example: A two-hour written analysis is reasonable; a full unpaid campaign plan may not be.

Checklist

  • Confirm scope
  • Confirm expected time
  • Confirm ownership and usage rights
  • Confirm evaluation criteria

Interviews

Prepare examples from real work. Good answers usually explain the situation, decision, execution, result, and lesson.

Example: For crisis handling, describe what you verified before answering the community and what you escalated.

Checklist

  • Pick three work examples
  • Name decisions and trade-offs
  • Prepare follow-up details
  • Practice aloud

Compensation

Separate cash, token grants, vesting, contractor terms, payment schedule, equipment, timezone expectations, and reliability.

Example: A $90k package with locked tokens is not the same as $90k cash.

Checklist

  • Separate cash and token value
  • Ask vesting and lockup terms
  • Check payment schedule
  • Clarify contractor versus employee terms

Safety

Verify domains, team identities, contracts, files, and wallet-related requests before sharing information or starting work.

Example: If a recruiter asks you to install unknown software before an offer, stop and verify through official channels.

Checklist

  • Never share a seed phrase or private key
  • Never pay to apply
  • Verify official domains and socials
  • Avoid unknown downloads and wallet approvals

Templates

Keep reusable templates for CV bullets, outreach, trial-scope checks, interview stories, and compensation questions.

Example: Trial-scope question: What is the expected time box, who reviews it, and how will the work be used?

Checklist

  • Save a CV bullet pattern
  • Save one outreach pattern
  • Save trial-task questions
  • Save compensation questions

Job safety baseline

Never share a seed phrase, private key, wallet approval, payment, or unknown download to apply for a role. Verify domains and people through official channels.

Read the full safety and disclaimer notes

Where this journey connects

Role directoryStages 2–4 start here: choose a target role and study its work, outputs, and boundaries.Portfolio briefsStage 5 builds a simulated proof-of-work project matched to your target role.Interview PrepStage 11 practices role-specific questions with real examples before interviews.Job BoardsStages 6 and 9 use boards to find contributor work and build a verified target list.