From Computer Repair to Crypto: What a Non-Traditional Path Actually Looks Like
I've fixed printers. I've set up Active Directory domains for school districts. I've done helpdesk tickets, network troubleshooting, desktop imaging, and the kind of IT work where success means nobody notices you exist.
Then I ended up running community for a cryptocurrency protocol, managing a $16.5M fundraise announcement strategy, and building AI systems with 3 million vectors.
The path between those two points is weirder than any LinkedIn narrative would suggest. Here's what actually happened, without the retroactive story-smoothing.
The IT Years Were Not Wasted
I spent years doing hands-on IT work. Public school systems. Healthcare environments. Small businesses that called you when their email stopped working. The pay was modest. The prestige was zero. Nobody at a dinner party wants to hear about DHCP configuration.
But here's what that work actually taught me:
Systems thinking. When a school district's entire email system goes down, you don't start with the most interesting problem — you start with the most likely cause and work outward. DNS first. Then authentication. Then the server. Then the application. This diagnostic framework transfers perfectly to debugging community problems, growth stalls, and operational failures in any context.
User empathy at scale. When a teacher can't print before a parent-teacher conference, the technical problem is secondary. The human problem is primary. I learned to communicate with non-technical people about technical failures in a way that reduced panic and built trust. This is exactly what community management is: translating complex systems into human outcomes.
Infrastructure awareness. I built and maintained the invisible systems that let organizations function. Networks, servers, backup systems, security policies. When I later built community infrastructure for a crypto protocol — Discord bots, governance frameworks, content pipelines, analytics dashboards — I was applying the same "build it once, make it reliable, make it invisible" philosophy.
The skills transferred. The context just changed.
How I Got Into Crypto
It wasn't a planned career transition. I didn't take a course or attend a bootcamp or read a "How to Break Into Web3" thread.
I got interested in the technology. Specifically, I got interested in what happens when you give communities actual ownership of the platforms they participate in. The governance experiments in DAOs, the token-incentive models, the idea that community participation could be measurable and valuable — that was genuinely new and interesting to me.
I started hanging out in Discord servers. Not for career advancement — because I found the conversations interesting. I asked questions. I answered other people's questions when I could. I started recognizing the same names across different communities. I built a reputation for being helpful, technically literate, and not a shill.
Someone eventually said: "You should come to ETHDenver." So I went.
The Conference Changed Everything
My first ETHDenver was 2022. I didn't know anyone. I didn't have a project to pitch. I was just some guy from Alabama who was interested in crypto governance.
Three things happened:
I discovered that crypto people are approachable. The industry is small enough that you can talk to founders, protocol leads, and well-known builders at side events. They're not behind PR teams. They're at a dinner table for eight.
I found out that my weird combination of skills was valuable. Technical literacy + community instincts + operational experience isn't common in crypto. Most people in the space are either deeply technical (engineers) or deeply social (community/marketing). The overlap of both was surprisingly rare.
I made connections that would determine the next three years of my career. Six relationships from one conference became ongoing professional collaborations. Two of them led directly to paid opportunities within six months.
I kept going back. ETHDenver again. Devcon Bangkok. Token2049 Singapore. Each conference built on the last one. By year three, I walked in knowing a meaningful percentage of the room.
The Community Role
My first real crypto role was Head of Community for a BTC-fi protocol. Here's how I got it: someone I'd met at a conference, whose content I'd engaged with for months, whose connections I'd made introductions for — they brought me in.
Not a job application. Not a cold email. A warm introduction from someone who'd watched me operate for a year.
The role itself was everything I'd been doing informally, but at scale. I built the community from zero to 50,000+ members across Discord, Telegram, and Twitter. I managed the content strategy, the governance discussions, the AMA schedule, the ambassador program. I coordinated the communication strategy around a $16.5M fundraise.
The IT background mattered more than I expected. When the Discord bot broke at 2 AM before a major announcement, I could fix it myself. When the analytics pipeline needed debugging, I didn't have to wait for engineering. When community members had technical questions about the protocol, I could answer them credibly because I'd spent years translating technical concepts for non-technical audiences.
What I'd Tell Someone Starting Now
Don't try to "break into" crypto. Be useful in the places where crypto people already are. Contribute to governance discussions. Help with documentation. Answer questions in Discord. The industry is small and people remember who's helpful.
Your previous experience is an asset, not a liability. Whatever you did before crypto — IT, healthcare, teaching, food service, construction — you learned things that the average crypto person hasn't. Systems thinking, operational resilience, customer empathy, physical-world logistics. These are rare in an industry full of people who've only ever worked in tech.
Go to one conference. Just one. Budget for it. Prepare for it. Follow up after it. The ROI of one well-executed conference trip is higher than six months of online networking. The relationships you build in person have a different quality than anything you can build on Twitter.
Build something. It doesn't have to be code. A community guide, a governance analysis, a curated resource collection, a weekly newsletter — anything that demonstrates you can create value, not just consume information. My AI project (a domain-specific knowledge system with 3M+ vectors) wasn't built to get me a job. It was built because I was interested. But it became the most powerful portfolio piece I have.
The path will look weird in retrospect. From IT support to conference networking to community management to AI development is not a linear career trajectory. It makes no sense on a resume. But each step built capabilities that the next step required. The synthesis is the value.
The Uncomfortable Truth
The hardest part of a non-traditional path isn't the skills gap. The skills transfer better than you'd expect. The hardest part is the credibility gap.
When you're competing against people with CS degrees and five years at Google for a role at a crypto protocol, your resume reads differently. You have to be better at the actual work — demonstrating value through contribution, not through credentials. You have to build a public track record that speaks louder than your education section.
This is exhausting. It's also the reason non-traditional hires tend to be relentlessly useful once they're in the door. They know what it took to get there. They don't take it for granted.
If you're in IT support or helpdesk or some other "unsexy" technical role, wondering if you could transition into something more interesting — you probably can. The skills you have are more transferable than you think. The path just won't look like anyone else's.
That's fine. The interesting paths never do.
Nathan Hamlett spent five years in IT support before transitioning to crypto community management and AI development. More at nathanhamlett.com.
Top comments (0)