Identifying and Recruiting Exceptional Blockchain Developers

Web3 is extremely volatile, and very new, which makes the task of finding great talent, let alone developers, increasingly difficult.

But, if you’re serious about building a successful project, whether that be an ICO/NFT Mint to raise funds or a new concept that revolutionizes the space, choosing the right developers will be the difference between months of bug fixes & frustration or actually taking your project to market. So, if you’re a Web3 founder who understands the importance of quality development, keep reading, if not, no worries, usually you have to be burned by bad devs at least once to realize it, we know you’ll come back.

Now, the days of hiring some random Pakistani freelancer or posting a job post on LinkedIn and hiring the first dev that seems to have a good CV are over. You need something thorough, something bulletproof. This resource will serve as a comprehensive guide outlining a clear roadmap to identifying top-tier talent. We call it the Web3 Dev Checklist, refined after years of interviewing hundreds of candidates to be a part of our team. (FYI: Only a few made the cut)

By the end of this, you will know:

-The basic guidelines for working with a developer

-How to evaluate & vet a developer

-How to properly communicate the project vision to a developer

-How to ensure you are protected when working with a developer

Basic Screening

a. Timezone and Language

Alright, when it comes to the basics, you want to be practical, keep it as simple as possible. Picture this: you've got this stellar project idea, but to build it, you need to get on calls, put together documentation, and create visuals to portray your vision to the developers so they can turn your idea into reality. Now, it’s already difficult to explain what is in your head to a tech guy, but what if they don’t even speak the same language; or what’s worse - they speak it at an acceptable level so you think they understand you but in reality, they go ahead and develop something completely different. Constant back & forth, it’s exhausting, a recipe for a headache, right? Keep it simple.

b. Reputation

Now, let’s get into the good stuff, to start – reputation. Think of it as your candidate's report card. We're talking about checking out online forums, social platforms, and client reviews to ensure your chosen talent not only meets but exceeds the gold standard in reliability and industry standing. And make sure to be thorough, follow up with their past clients to get their honest feedback.

‍

Experience Evaluation

a. Technical Mastery

Now, into the nitty-gritty. Of course, you will want to know all about their past projects but don’t just stop there. Dig DEEP. Go through each project, one by one, and ask the following questions:

-What was your exact role within this project, what were you in charge of?

-What are some of the unique aspects / features that you built and walk me through how you went about structuring it on a technical level?

-What was the most challenging part of this project? Why?

You’ll not only find out if they actually had a significant contribution and are who they say they are, but you’ll also learn about their problem-solving skills when facing a roadblock.

Because, in the end, It's not just about technical skills; it's about finding someone who takes pride in their work, who is honest & committed, and who can dance through the complex challenges with finesse.

Planning, Designing, & Defining SOW + Architecture 

a. Documentation

If after 1 call you’re developer just wants to start coding away and wants to charge hourly as he goes, RUN. The worst thing that can help to your project is to start building and then a few weeks down the road, development hits an obstacle. This could be that the chain you are working on isn’t suited for your idea, regulatory requirements prohibit you from structuring the project in this way, smart contract logic isn’t possible with the current design, etc. Now, you could’ve known this from the beginning, and mapped out a plan for development to adjust. But, not laying the foundation properly & rushing to start development will in most cases actually double your timeline!

So, if your developer or agency does not have a process in place, you now right there and then, they are not serious. They might be cheaper, but if you’ve been around this space long enough, you’ll realize that that is the most expensive route in the long term.

 (Link to resource explaining our documentation process)

Development Process

a. Timelines and Communication 

The backbone of a project’s success is the clarity doing the development process. You want to make sure your developer is always informing you of estimated timelines for every single milestone. It will prevent you from constantly chasing him for updates and will ensure efficient communication.

Now, to add to that, the timelines that are set must be realistic, and there must be crystal-clear updates on those days. A written (we prefer video) explanation of the progress made, what is remaining, what the next steps are, and when the next update is expected to be provided.

‍

b. Tech 

You’ve evaluated their experience beforehand, and you know that is on point. But, there are 2 very often  overlooked aspects of building a Dapp that you should keep in mind and make sure they are capable of before starting.

1. Wallet integration. Surprisingly, most developers only know how to use metamask, but this only contains a fraction of the users in Web3. We must be able to include Wallet Connect, Rainbow Wallet, Ledger, OKX wallet, and many others.
2. Web3 is known to be a world where the UX is horrible. A traditional Web2 user wouldn’t even know where to start, how to create a wallet, how to connect it, how to execute a transaction, let alone understand your completely new project. You want a developer who prioritizes user experience (UX) principles within decentralized applications. Someone who crafts a product that's not just functional but intuitive to use and removes friction.

Security

a. Testing & QA Mastery

You are going to want to get a full understanding of your candidate’s testing & QA process. First, you want to ensure that they comprehensively create unit tests for both the DApp and smart contract. They also deploy all of the components to a live test network where you can replicate all of the functionalities of the project in a test environment. Here there should be a review process for every aspect, including various use cases, user flows, and interactions, from A-Z. 

If I had to pick one thing my developer was proficient at, it would be this, so make sure to thoroughly vet their testing & QA process.

We personally like to take it one step further and film loom videos showing the clients how they can go in and test themselves. It not only gives the client that extra peace of mind (trust me, you want that), but also they usually have a better understanding of the vision for the project and therefore can point out issues the developers might have never seen. 

(Link to resource explaining our testing process)

b. Launch Preparedness

Ready for the big day? Everything has been built out and you are ready to launch, but remember, it isn’t finished until it’s finished, don’t celebrate yet.

Launch day is the most stressful time for any Web3 startup. Last minute changes, delays, complaints from users, and so much more that you can’t even plan for. So, to ensure a smooth and secure launch for your Web3 project, your developer or agency must be available during this period.

And to take it one step further, they must have a prep doc with all of the different components that need to be put in place to launch so that nothing is forgotten, and they must have a contingency plan in place in case any issues do come up.

 (Link to resource explaining our launch prep process)

c. Account & Wallet Management

You never know what could happen with your developer or agency, they could get in a car crash, decide they no longer want to work for you, win the lottery & disappear, or in the worst case, restrict access to all of the accounts and wallets unless you pay them.

It seems intuitive, but most founders don’t create the accounts or wallets related to their tech, and this is a huge mistake. Here is a list to help you think through it:

-Github account & repository (where all of the code is stored)

-Domain provider (GoDaddy, Namecheap, Google domains)

-Hosting (Vercel, AWS, Cloudflare)

-Smart contract owner wallet

-Treasury wallet

etc.

‍

Conclusion

Your journey in building a Web3 startup demands more than just random freelancers with a few good reviews– it demands a meticulous process. In this crazy space, the Web3 Dev Checklist is not just a list of questions but a personalized guide; it's your litmus test for genuine expertise, crafted to bring out responses only an adept blockchain developer can provide.

There are 2 groups: those who understand the importance of quality development, and those that still have to be burned by bad devs at least once to realize it. The choice is yours.

‍

If you want to see if we are a good fit and learn how we would breakdown & tackle your project, book a free discovery call below.