I have been getting comments on my articles asking me to write for them. Not from a cold outreach I sent, not from a resume I submitted, just from people reading the series and reaching out. That is a feedback loop working exactly the way it should. Today I want to break down why feedback loops matter more than most people think, and what Web3 interviews actually look like when you finally get in the room.
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.
This series started as a personal learning challenge on Day 1 and by Day 53 it has turned into a writing portfolio that landed me a freelance role at Bitquery, a contract technical writing role at Tether, and multiple inbound writing offers. None of that came from applying. All of it came from feedback loops compounding over time.
What a Feedback Loop Actually Is
A feedback loop is any system where output becomes input. You publish something, someone reacts, that reaction changes what you publish next, and the cycle tightens over time. In community building and content creation, feedback loops are the difference between growing in the dark and growing with direction.
Most creators treat feedback as validation. "Did people like it?" That is the wrong question. The right question is "what did people do after reading it?" A comment asking "can you write for us?" is stronger feedback than 100 likes. A DM saying "I tried this and it did not work" teaches you more than 50 bookmarks.
The three feedback signals that actually matter in Web3 content are replies with follow-up questions (people want more depth), inbound writing or collaboration offers (people trust your knowledge), and topic requests (people want you to cover something specific). All three have shown up in this series across Medium, Future, and X. That is the feedback loop doing its job.
How to Build a Feedback Loop Into Your Content
Most people publish and wait. A feedback loop requires one more step: you have to make it easy for people to respond with something useful.
At the end of every article in this series there is a question or a forward-looking statement like "tomorrow we cover X". That is not just a CTA. It is a feedback collector. People who engage with that line are telling you exactly what they want next. The Web3ForHumans Telegram community functions as a live feedback channel where every article generates discussion that directly shapes the next one.
For community builders the same principle applies offline. The Ludhiana Baithak format from Day 52 ends with "what do you want next time" as a formal part of the agenda. That single question closes the loop between what you planned and what the room actually needed.
The Think Tank and What It Taught Me About Real Feedback
In January 2026 I was part of Tim K's Think Tank experiment, a competitive MVP-building program that was oversubscribed even with minimal promotion. Of 14 participants only 4 submitted attempts and 2 showed the required time commitment. I was one of them.
The experiment was designed to build something real in a compressed timeframe with peer accountability as the feedback mechanism. What it taught me is that most people confuse "I understand this" with "I can build this". The gap between comprehension and execution is where real feedback lives. Shipping something half-broken teaches you more than reading ten articles about the topic.
That same principle showed up in my Tether's contract writer interview. They did not ask me theory questions. They asked me to build a functioning MVP using Holepunch technology and Hypertele. The interview was the feedback loop: your ability to execute under ambiguity is the signal they were reading.
What Web3 Interviews Actually Look Like
Web3 hiring is different from traditional tech hiring in three specific ways. First, your public work is your CV. Before any interview, the hiring team has already read your GitHub, your articles, your tweets, and your community presence. By the time I got to the Tether interview my writing was already doing the talking.
Second, Web3 interviews test execution not just knowledge. The Tether interview was a build challenge. The Bitquery freelance engagement started with a real brief on a real topic, not a test. Both required me to produce something working, not just explain how it works.
Third, the interview is often a conversation between builders. Web3 teams are small and cross-functional. They want to know if you can think out loud, admit what you do not know, and figure things out in real time. The worst thing you can do in a Web3 interview is pretend to know something you do not. The best thing you can do is show exactly how you would find out.
What Gets You the Interview in the First Place
The writing offers I have received as comments on this series are a direct result of one thing: specificity. Articles that cover one topic deeply and honestly attract people who need exactly that expertise. The Bitquery freelance pieces on prediction market APIs and DEX router slippage landed because the series showed I could explain complex on-chain concepts in plain language. That is not luck. That is a feedback loop that ran for 50+ days and produced a legible signal.
The practical steps if you are targeting a Web3 role right now are straightforward. Pick one vertical (DevRel, technical writing, smart contract development, community) and publish 10 articles in that vertical. Reply to every comment. DM three people per week whose work you genuinely find interesting. Build one thing publicly even if it is small. By the time you apply anywhere, your work will have already introduced you.
How to Prepare for a Web3 Interview Specifically
For DevRel and community roles the most common questions are about your approach to onboarding new developers, how you handle negative community feedback publicly, what metrics you use to measure community health, and how you would explain a complex protocol concept to a complete beginner. Every one of those questions is answered by the work you do publicly before the interview.
For technical writing roles like the ones I have landed, the ask is almost always a live brief. Have 2 to 3 published samples that show range: one conceptual explainer, one tutorial with code, and one opinion piece. Those three formats cover everything a Web3 technical writing team needs to evaluate.
For developer roles, the Tether approach is becoming more common: build something real using the protocol's own stack. The best preparation is to spend a weekend building with the technology of the company you are applying to and documenting what you built, what broke, and what you learned.
Tomorrow: Building a Public Portfolio and Ghostwriting for Founders
Day 54 covers how to turn everything you have built publicly into a portfolio that gets you hired, and what ghostwriting for Web3 founders looks like as a freelance opportunity. If you are considering writing as a Web3 income stream, that one is directly relevant.
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
- Day 51 - DevRel and community building foundations
- Day 52 - Hackathons, events, and Ludhiana Baithak announcement
- Bitquery - Where freelance writing led from this series
- Tim K on X - Think Tank experiment and MVP building
- Holepunch - P2P technology used in Tether interview build
- Web3ForHumans Telegram - Live feedback channel for this series
- Full 60-day series on Future - Complete archive
Top comments (0)