Find Bitcoin work that fits you.

Start with the work you can help a team do. Bitcoin employers need more than protocol engineers: product design, firmware, quality assurance, infrastructure and payment integration all appear in our selected job collection. The best starting point is a role whose daily problems you can explain.

1. Choose a lane and a proof point.

Pick one primary direction for the next round of applications. Keep a second direction only when your existing work supports it. Use the table to decide what to show, rather than collecting every tool name on a job board.

2. Build a shortlist you can actually research.

Choose five to eight teams from the company directory. For each, write one sentence about the product, one about a problem you could help solve, and one link that supports your understanding. Look at the team's own careers page before investing time in an application.

A product team can belong in your research list without having a vacancy. Keep named openings, general applications and potential freelance collaborators in separate rows of your tracker. A full-time opening does not establish that a company wants a contractor.

3. Check fit before polishing the application.

• Location: which countries are eligible, and is relocation or local employment required?
• Overlap: what hours must you share with the team, including seasonal clock changes?
• Engagement: employee, ongoing contractor or a project with a defined handover?
• Scope: individual contributor or management; new features or operations; product or protocol?
• Requirements: which skills are essential, and which are listed as preferences?

“Remote” answers only part of the location question. For example, Coinkite's designer listing asks for Toronto business-hours overlap. Record the employer's actual wording and any unresolved country question. The source was checked on 13 September 2026; it may change.

4. Turn the job description into an evidence map.

Make three columns: what the team needs, what you have done, and the link or example that supports it. If a requirement has no evidence, label it as a gap. Decide whether to apply with an honest learning plan or strengthen one example first.

The Bitrefill Lightning Developer listing, checked on 13 September 2026, combines backend development with Lightning operations. A payment demo alone may not establish experience operating a production service. Explain exactly what your project tested and what you have not yet done.

5. Write an application a teammate could use.

Open with the role and a concrete reason the team's work interests you. Follow with two relevant examples, your personal contribution and direct links. Close with your location, time zone and availability where requested. Match the employer's submission process.

A compact structure is: “I am applying for [role]. In [project], I was responsible for [specific contribution]. The result and tests are documented at [link]. I am based in [country/time zone], with [actual overlap].” Replace every placeholder with facts; omit claims you cannot support.

If you use AI to help draft, check the final text against your actual experience and follow the employer's stated policy. Be ready to explain every project you submit. Your application should sound like your own account of the work.

6. Run a manageable two-week search cycle.

1. Days 1–2: choose a lane, shortlist teams and check each employer page.
2. Days 3–5: improve one portfolio example and prepare two focused applications.
3. Week two: submit where there is a fit, prepare for conversations, and record responses and open questions.
4. Review: decide whether the next improvement is your targeting, evidence or explanation. A small sample of replies is not proof about the entire market.

This schedule is a suggested routine, not a hiring forecast. Keep the employer URL and last-checked date beside each role. Before following up, use any timing or contact instructions the employer provides.

Prefer project work?

Describe one outcome you can deliver: an integration, a wallet UX review or a test plan. Use the project brief to define inputs, milestones, acceptance and exclusions. Bitcoin CV's marketplace is still being developed; there are no seller bookings or project payments on the site yet.

Next, prepare a clear technical or design conversation.

All guides → · Explore jobs →