33 Bitcoin jobs: remote work and role mix.

Download the snapshot data ↓

Engineering leads this collection; adjacent specialties matter.

We assigned 19 roles to Engineering, 6 to QA & Security, 5 to Infrastructure and 3 to Design. The latter three groups account for 14 roles (42.4%). These are our exclusive editorial categories; individual jobs can span more than one discipline.

What a candidate can do with this: choose evidence that matches the work. A UI prototype can help explain design decisions; an operations role may need a clear incident investigation or reliability example. A security role requires relevant security evidence. The counts do not show how many applicants are competing, which discipline is easiest to enter or which one pays more.

Remote is a starting filter, not an eligibility decision.

Four selected roles were labeled hybrid. Two did not explicitly specify their work arrangement in the reviewed board information. We kept those two unknown instead of treating them as office-based or remote.

Three examples show why the detail matters:

• Regional scope: Strike's Trust Designer was listed for the Americas and Europe.
• Working-hours overlap: Coinkite's Sr. Designer asks for overlap with Toronto business hours; country eligibility still needs confirmation.
• Travel: Blockstream's Forward Deployed Engineer is labeled remote for its New York / US opening, but calls for regular customer travel across North America.

Before applying, record your country, feasible working hours and travel availability beside the employer's current requirements. If the posting leaves a country question open, ask the employer through its normal application process. A distributed team or optional relocation benefit is not proof that every country is eligible.

Three employer groups account for more than half of these records.

Lightning Labs contributes eight selected listings, Blockstream six and Galoy four: 18 of 33 (54.5%). That concentration is a feature of our selection. It is not a measure of these employers' market share, hiring budgets, growth or total open jobs.

Use the wider company directory to broaden a shortlist. Inclusion there does not mean a company has a verified opening. A full-time vacancy also does not establish that the employer wants freelance proposals.

Turn one listing into a concrete evidence plan.

Here is an original practice example for an infrastructure candidate. Choose a local test environment and describe an invoice-status callback arriving twice. Build or explain repeat handling, show the observed result, record a failed dependency and state the limitations. This is a portfolio exercise, not an employer's interview question or evidence that the employer uses this architecture.

A designer could instead document how a wallet distinguishes a payment request, an unpaid invoice and a confirmed payment. Explain the user task and show the design decisions. Use the portfolio guide or Lightning project guide to scope an example you can honestly discuss.

How we assembled and counted the snapshot.

1. Selection: we froze the 33 specific full-time builder roles in Bitcoin CV after its 14 September review. The selection favors Bitcoin engineering, design and related work, with a remote-first focus.
2. Source evidence: each role appeared on an employer career page or its linked hiring board at review. Public Ashby/Greenhouse board records and employer pages supported the checks. General applications, filled archive roles and entries whose employment type was unverified were excluded.
3. Unit: one selected listing with a unique source URL. Employer groups combine brands where the site's directory does so, such as Trezor and Invity under SatoshiLabs. Selected source URLs are unique; the data is not a count of individual headcount positions.
4. Classification: one primary specialty per listing. Work-arrangement labels and eligibility notes are separate fields. Missing information remains unknown.
5. Calculation: each percentage is its category count divided by 33, multiplied by 100 and rounded to one decimal place. Rounded shares may not total exactly 100%.
6. Time: the review date is when we checked the source, not when an employer first posted the job. This page and its download remain a historical snapshot; consult the current collection and each employer before applying.

Limits: this is neither a census nor a random sample. It cannot establish hiring trends, total Bitcoin employment, salary levels, applicant demand, successful hires or worldwide remote availability. Do not compare future snapshots as growth rates unless the selection method and coverage are comparable.

Editorial responsibility: Bitcoin CV compiled the dataset and this analysis with AI assistance. The report provides calculations and source links so readers can examine the evidence. Suggested projects are editorial examples, not claims of first-hand implementation. Employers control their listings; the site is independent and no partnership is implied.

The 33 records behind the analysis.

Every role below was reviewed on 14 September 2026. Links lead to the employer's source, which may now differ from this snapshot. The JSON download includes the same records, dates, categories and selection limits.

Cite or reproduce this snapshot.

Suggested attribution: Bitcoin CV, 33 Bitcoin jobs: remote work and role mix, published 14 September 2026, sources reviewed 14 September 2026. Link to this report and retain the sample-size and selection caveats when reusing a statistic.

To reproduce the tables, count the download's roles records by specialty, work_arrangement or company, then divide each count by 33. The included metrics are derived values, not a separate source of evidence.