A quick honest note before today's article. Days 53 to 54 had a longer gap than planned. A close friend got married, life happened, and then a wrist injury made typing genuinely difficult for almost two weeks. During that same period I landed a paid writing gig, a research and testing opportunity, and got into conversations with a wealth management and investment platform about managing their content infrastructure. Sometimes stepping away from the keyboard produces more results than staying at it. That is its own kind of feedback loop.
If you want to keep up with this 60-day Web3 journey, you can follow me on X, on Medium, on Future, and you can join the Web3ForHumans Telegram community.
What a Public Portfolio Actually Is
Most people think a portfolio is a PDF with links. In Web3 it is not. A public portfolio is everything you have shipped, written, built, or contributed to that someone else can verify without asking you. It is your GitHub commits, your published articles, your Telegram community, your Twitter replies, and your documented projects. The Notion page, the Medium series, the Bitquery bylines, and the Tether FAQ are all portfolio. None of them started as portfolio. They started as work.
Looking at my own journey the portfolio built itself in layers. The Huawei Dev Community work came first: testing APIs, writing integration guides, and supporting campus hackathon registrations. Those articles got picked up by Dev Genius and Towards Dev on Medium, which was the first external validation that the writing was clear and useful. That signal led to the Tether contract, which led to the Bitquery freelance pieces, which led to inbound offers in comments on this series. Each layer made the next one easier to land.
The Portfolio Nobody Tells You to Build
There is a portfolio most people ignore completely: the thinking portfolio. Not just what you built but how you thought about it publicly. The 60-day series is a thinking portfolio. Every article shows how I approached a concept, what confused me, what clicked, and what I want to build next. A hiring team reading Day 1 to Day 54 knows more about how I think than any resume could communicate.
The Peardoc project from the Holepunch's tech stack is a good example. A decentralized document editor built on Holepunch's P2P networking with real-time collaboration, secure peer invitations via unique keys, and no central server. That one project shows technical curiosity, execution under a brief, and comfort with cutting-edge Web3 infrastructure. It is more interesting than a list of skills on a resume.
The Stoa fellowship, the Toastmasters work, the event organization experience from college: all of these are portfolio. They show range. Web3 roles, especially DevRel and community, value range. A person who can write technical docs, run a college event with 7,000 footfall, facilitate a room, and build a P2P app is a very different hire from someone who only codes.
How to Build Your Portfolio From Zero Right Now
The fastest way to build a Web3 portfolio from zero is to pick one protocol you find genuinely interesting, spend one weekend building or writing something with it, and publish that work publicly with honest documentation of what worked and what did not.
The documentation is the differentiator. Most builders ship and move on. The ones who document what broke, what they tried, and what they learned create a paper trail of thinking that hiring teams and collaborators can actually evaluate. My Tether interview brief was essentially this: use Holepunch technology, build something real, show your thinking. The output was Peardoc.
For writers the equivalent is: pick one underexplained topic in your target vertical, write the clearest explanation of it you can find, and publish it somewhere with a byline. Then do it again. Ten focused articles on one vertical over two months will outperform a hundred generic posts every single time.
Ghostwriting for Web3 Founders: What It Actually Looks Like
Ghostwriting in Web3 is one of the most underrated income streams for technical writers and community builders. Founders at early-stage protocols are building full time and have no bandwidth to write the threads, blog posts, and documentation their community needs. They know what they want to say but cannot find the time or the words to say it clearly.
The ghostwriter's job is to capture the founder's voice, translate their technical thinking into accessible language, and produce content consistently enough that the founder's presence feels real even when they are heads down building. Good Web3 ghostwriting pays well because it requires a rare combination: technical understanding, writing skill, and the ability to sound like someone else.
Getting started is simpler than most people think. If you have been writing publicly in a specific vertical (DeFi, DePIN, identity, tooling) for a few months you already have a sample set that shows your voice and your range. The pitch to a founder is straightforward: "I follow your project, I understand what you are building, here are two sample posts I wrote in your voice, would you want to try one month of working together?"
The Portfolio Checklist for Web3 Roles
If you are targeting a DevRel, community, or technical writing role in Web3 right now, here is the honest minimum that gets you taken seriously:
Two to three published technical articles with a byline on a real publication (Medium, Dev.to, a protocol blog). One live project you can demo even if it is small. One community you contribute to actively whether as a member, moderator, or creator. One example of explaining something complex in plain language to a non-technical audience. And a public profile (Twitter, LinkedIn, or a portfolio page) that connects all of the above so a hiring manager can see the full picture in under two minutes.
Everything on that list can be built in 60 days. This series is proof of that.
Tomorrow: Open Source Contributions and Networking in Web3
Day 55 covers how to contribute to open source Web3 projects without being a senior developer, and how networking in Web3 actually works in 2026, which is very different from sending LinkedIn connection requests.
If you want to follow along as I keep learning, building, and occasionally changing my mind about Web3, you can find the rest of this 60-day journey on X, on Medium, on Future, and you can join the Web3ForHumans Telegram community to discuss these topics in plain language.
Resources
- My Portfolio - Full work history including Tether, Huawei, Peardoc and more
- Day 53 - Feedback loops and Web3 interview prep
- Bitquery freelance pieces - Real bylines from this series
- Keet FAQ by Tether - Contract technical writing output
- Web3ForHumans Telegram - Community that doubled as portfolio signal
- Full 60-day series on Future - The thinking portfolio in full
Top comments (0)