Home / Guides
A practical portfolio guide

Build a Bitcoin CV that shows your work.

Make it easy for a team to understand what you can build, how you think and where you can contribute.

By Bitcoin CV · Published 12 September 2026 · 6 minute read

A useful Bitcoin CV combines a short professional summary with evidence of contribution. Developers can show code, tests and technical decisions. Designers can show research, interaction flows and the tradeoffs behind a usable product. You do not need a long list of Bitcoin job titles to make your work legible.

What belongs in a Bitcoin CV?

Lead with the kind of work you want, your strongest relevant skills and two or three examples. State your time zone, availability and preferred engagement. Keep private contact details in the version you send directly to an employer.

Write a concrete introduction.

Use a sentence that says what you do and what you have built. For example: “Backend developer working in Go, with a Lightning payment demo and experience testing webhook failure cases.” This is an illustrative format, not a claim about a real candidate.

Explain your contribution.

For each project, name the problem, your role, the decisions you made and the result you can substantiate. Link to a repository, merged pull request, live demo or case study. Distinguish your own work from the rest of the team’s work.

Make one example easy to inspect.

A small project with setup instructions, a clear test path and documented limitations can be easier to assess than a large unfinished repository. Explain the environment you tested and which parts remain experimental.

State practical fit.

Include your working time zone, hours of overlap, languages and whether you want employment, contract work or a fixed project. For remote jobs, check the employer’s country and office requirements before applying.

For developers: make the evidence reproducible.

Include a short README, installation steps, tests and a clear account of your implementation choices. If your work handles payments, describe how you tested failures, retries and recovery. Keep real credentials and customer data out of public examples.

Open-source contributions can include tests, documentation and reproducible bug reports as well as feature code. Chaincode Labs describes contribution as a route into its work, while BitBox invites applicants to share GitHub and side projects. These are examples of employers’ stated interests, not universal hiring requirements.

For designers: show how the experience improved.

A strong case study explains the user’s task, the confusing or risky moment, the alternatives considered and what changed after feedback. Show the before and after flow. Clearly label assumptions, prototype tests and production results so readers can distinguish them.

A wallet case study might examine first payment, fee selection, backup education or recovery messaging. Work through relevant patterns in the Bitcoin Design Guide. A Figma link can help, but your written explanation should still stand on its own.

A simple project entry

Project: [name and link]
Problem: [who needed what]
My contribution: [specific code, design or research]
Decisions: [one meaningful tradeoff]
Evidence: [test, demo, merged contribution or measured result]
Limits: [what is not finished or not proven]

What should stay private?

Publish a portfolio deliberately. Avoid exposing a home address, identity documents, private repositories, customer records or wallet secrets. A public profile can use a professional display name; a hiring process may require other details later. Get permission before sharing client work.

Start with a one-page structure.

Download an editable Markdown template for a professional summary, project evidence, skills and availability.

Download CV template ↓

This downloads a text template. Bitcoin CV does not collect or upload your CV.

Before you send it

Ready to look for a team? Browse the researched job collection or build your next portfolio project.