CV Proof Check: Full-stack blockchain developer profile — what signal does this CV give to recruiters?

Shubhada Pande

@ShubhadaJP

Published: Jun 20, 2026

Updated: Jun 30, 2026

We are starting a CV Proof Check discussion with the candidate’s permission.

I am not using the candidate’s name in the title. The LinkedIn profile has been shared by the candidate:

Saurabh Pandey 468189148

Please read this like a recruiter, founder, tech lead, or hiring manager would read it.

The profile is of an early-career full-stack blockchain developer.

The CV mentions Solidity, DeFi, staking, trading systems, Next.js, NestJS, Go, Docker, AWS, Redis, PostgreSQL, Hardhat, Ethers.js, OpenZeppelin, automated trading systems, and Bittensor subnet mining.

The project section includes:

a blockchain trading platform using Go, gRPC, Ethereum integration, wallet operations, order execution, and on-chain trading contracts
an SROI / social impact platform with staking, reward distribution, DAO treasury, EIP-712 signatures, NestJS backend, and AWS deployment
a decentralized arbitrage bot using Solidity, Node.js, DEX price scanning, flash loans, gas estimation, and revert logic
Bittensor subnet mining work with Linux servers, Docker, Python, FastAPI, PM2, GPU/CPU optimisation, and subnet operations

This is not a weak profile.

But when I read it from a hiring angle, I get one question:

What role does this CV clearly point to?

Is this person coming across as:

full-stack blockchain developer
blockchain backend developer
Solidity developer
trading systems developer
Web3 infra / AI + blockchain developer
or too many things at once?

And what would you need to see before trusting the project claims?

For example:

GitHub repo
deployed contract link
transaction hash
demo video
short architecture note
README
screenshot
clearer “my role in this project” line
separation between company work, freelance work, and personal projects

I am asking this from a proof-based hiring angle.

When a Web3 CV has many strong terms in one place — Solidity, DeFi, staking, arbitrage bot, Go backend, NestJS, AWS, Bittensor — does it create confidence?

Or does it create doubt unless the proof is placed more clearly?

If you were screening this profile, what signal would you take from it in the first 30 seconds?

Like 2 Replies 6

Replies

Welcome, guest

Join ArtofBlockchain to reply, ask questions, and participate in conversations.

ArtofBlockchain powered by Jatra Community Platform

Shubhada Pande

@ShubhadaJP • Jun 21, 2026
My first reading: the projects should not be removed.

There is useful material here.

But I would want the project section to separate three things more clearly:
1. company or production work
2. freelance / client work
3. personal or experimental projects
That alone would make the CV easier to trust.

For example, “decentralized arbitrage bot” can mean many things.

It can mean a learning project.

It can mean a testnet experiment.

It can mean a serious trading system.

It can mean the candidate only worked on one backend module.

So I would not judge only by the project name. I would look for the proof around it:

What exactly was built?

Was it deployed?

Was there a contract address?

Was there a README?

Was the candidate responsible for smart contracts, backend, deployment, or only integration?

For Web3 hiring, I feel the issue is not always skill. Many times the issue is that the CV does not help the reader separate real ownership from broad project wording.

0
Jay Tranberg

@zippy-dog • Jun 21, 2026

My first impression is full-stack software engineer with blockchain experience, rather than a clearly defined blockchain specialist. The breadth is impressive, but in the first 30 seconds I want to understand what the candidate truly owns. One flagship project with architecture, GitHub, deployed contracts, screenshots, or a concise case study would build confidence much faster than another list of technologies. I've learned this lesson myself. I started my career in Solidity and later expanded into AI, IoT, SaaS, and data platforms. Looking back, I realized that breadth alone doesn't communicate value—proof does. That's why I'm currently rebuilding my own portfolio around engineering case studies instead of technology lists. I think proof tells a much stronger story than keywords.

1

Shubhada Pande

@ShubhadaJP • Jun 22, 2026

Jay, this is a very useful reading of the CV.

The line that stayed with me is: “full-stack software engineer with blockchain experience.”

That is probably what many hiring people also feel when a CV has Solidity, backend, trading, Bittensor, AWS, and many project names together.

The work may be real, but the reader still needs one clear example to understand the depth.

So maybe in this CV, instead of adding more skills, one project should be explained properly. Something simple:

what was the project, what part did he handle, where was blockchain actually used, and what can someone see or verify?

That would make the profile much easier to read.

Thanks for adding this. It helped me see the CV from a builder’s side, not only from my founder/community side.

0
Shubhada Pande

@ShubhadaJP • Jun 23, 2026

Taking Jay’s point forward, what should one good Web3 project case study include?

For a full-stack blockchain developer profile, would you trust the CV more if one project showed GitHub, contract link, screenshots, architecture note, short README, deployment notes, or “what I handled” section?

I am starting to feel one clear project may be stronger than five project names.

0
Shubhada Pande

@ShubhadaJP • Jun 25, 2026

Adding one useful perspective that came from the LinkedIn discussion around this CV teardown.

One reviewer described the issue as: the candidate may be doing a lot, but the CV may still be signalling too little.

That line stayed with me because it captures the core problem well.

A full-stack blockchain developer profile can mention smart contracts, frontend, backend, GitHub, deployments, and integrations. But if the reader still cannot quickly understand what was actually built, what was shipped, what was owned, and what proof exists, the CV becomes harder to evaluate.

So maybe the question is not only:

“Does this candidate have enough skills?”

It is also:

“Is the CV helping a hiring team understand the candidate’s strongest proof fast enough?”

Credit to Davey Keuvelaar for this framing in the LinkedIn discussion.

0
Shubhada Pande

@ShubhadaJP • Jun 30, 2026

One more point came up on LinkedIn after this teardown, and I think it fits this discussion.

A developer asked a very real question: if someone is targeting Web3 developer roles, how should they show AI apps, full-stack Web2 work, and a strong academic/scientific background without confusing the reader?

I think many Web2-to-Web3 candidates face this.

The problem is usually not lack of skills. The problem is that the CV gives equal weight to everything. So the reader sees Web3, AI apps, full-stack development, security interest, DeFi interest, academic background — but does not immediately know what the candidate wants to be hired for.

If the target is Web3 developer, then the CV has to make that obvious first. Solidity, DeFi work, smart contract security learning, protocol understanding, GitHub proof, and shipped Web3 work should come before everything else.

AI apps and full-stack Web2 work should still be there, but they should support the Web3 story. They can show that the person can build complete products, understand users, work across frontend/backend, and ship beyond small contract exercises.

So maybe the question is not only “what more should I add to my CV?”

A better question may be: what should the reader notice first, and what should only support that first signal?

0