Crypto Job Interview Questions: What Companies Actually Ask

Crypto interviews are different from traditional tech interviews. Yes, you'll still get data structures and system design questions. But you'll also face questions about on-chain mechanics, protocol design, tokenomics, and — perhaps most importantly — whether you actually use crypto.

This guide covers the real questions crypto companies ask across technical and non-technical roles, based on candidate experiences and hiring manager feedback from companies posting on GMI Jobs.

How Crypto Interviews Differ from Traditional Tech

1. Domain knowledge is tested directly. Unlike a traditional tech interview where you might never discuss the company's product, crypto interviews often start with "walk me through how this protocol works." If you're interviewing at a DeFi protocol, you're expected to have used it.

2. On-chain activity matters. Some companies ask for your wallet address. Not to check your balance — to see if you've actually interacted with DeFi protocols, minted NFTs, participated in governance, or bridged assets across chains. Having an active on-chain presence signals genuine interest.

3. Take-home projects are more common than whiteboard coding. Many crypto companies prefer seeing how you work over watching you solve algorithm puzzles under pressure. Take-home projects might include writing a simple smart contract, building a frontend that interacts with an existing protocol, or analyzing on-chain data.

4. Culture fit goes deeper. Crypto teams are small, often remote, and operate in a high-stakes environment. Culture fit questions probe your alignment with decentralization values, comfort with ambiguity, and ability to work asynchronously.

---

Technical Interview Questions by Role

Smart Contract / Solidity Developer

Fundamental questions:

• What is the difference between `memory`, `storage`, and `calldata` in Solidity?
• Explain the reentrancy vulnerability. How does a reentrancy guard work? Can you still have reentrancy with a guard in place?
• What's the difference between `delegatecall` and `call`? When would you use each?
• How do proxy contracts work? What are the tradeoffs between transparent proxies and UUPS?
• Walk through the ERC-20 standard. What functions does it require? What events?
• What happens when a contract runs out of gas mid-execution?

Intermediate questions:

• How would you design an upgradeable contract system? What are the storage collision risks?
• Explain the difference between Hardhat and Foundry. When would you choose one over the other?
• What's the Checks-Effects-Interactions pattern and why does it matter?
• How would you optimize this contract for gas? (Given a sample contract with obvious inefficiencies)
• What is a flash loan? How would you protect a protocol against flash loan attacks?
• Explain how an AMM (Automated Market Maker) works at the contract level.

Senior-level questions:

• Design a lending protocol's liquidation mechanism. What edge cases would you handle?
• How does MEV affect your contract design? What mitigation strategies exist?
• Walk through how you'd conduct a security review of this contract. (Given a contract with subtle vulnerabilities)
• Explain EIP-4844 and how it affects L2 costs and contract design.
• How would you implement a time-weighted average price (TWAP) oracle?

Frontend / Full-Stack Web3 Developer

• How does a wallet connection flow work? Walk through what happens when a user clicks "Connect Wallet."
• What's the difference between ethers.js and viem? What are the tradeoffs?
• How do you handle transaction confirmation UX? What states does a user need to see?
• Explain how you'd build a frontend that reads from and writes to a smart contract.
• How do you handle chain switching and multi-chain support in a DApp?
• What's the difference between reading from an RPC node vs. an indexer like The Graph?
• How do you handle wallet signature requests for authentication (Sign-In with Ethereum)?

Backend / Infrastructure

• How do you design an indexing system for on-chain events?
• Explain the difference between a full node, archive node, and light client.
• How would you handle RPC rate limiting and reliability for a production DApp?
• What strategies exist for handling chain reorganizations in your backend?
• How do you monitor smart contract events in real-time?

Data / Analytics

• Write a Dune query that finds the top 10 wallets by volume on Uniswap V3 in the last 30 days.
• How would you track a token's velocity across multiple DEXs?
• Explain how you'd build a dashboard tracking protocol revenue and TVL across chains.
• What's the difference between DEX aggregator volume and direct DEX volume?

---

Culture and Behavioral Questions

These questions appear across all crypto roles and are often weighted more heavily than in traditional tech:

Crypto Alignment

• "What's in your wallet?" — Not literally asking for balances, but probing whether you use crypto personally. Have an answer ready about protocols you use, tokens you hold (keep it general), or governance you participate in.

• "What's your thesis on [DeFi / NFTs / L2s / Bitcoin]?" — Crypto companies want people with opinions. Having a thoughtful, nuanced view — even a contrarian one — is better than having no view at all.

• "Which crypto project do you admire and why?" — Tests whether you follow the ecosystem and can articulate why specific design decisions matter. Avoid generic answers like "Bitcoin because it's decentralized." Go specific.

• "What are the biggest problems in crypto right now?" — Tests critical thinking. Good answers reference real issues: UX complexity, MEV extraction, regulatory uncertainty, oracle reliability, L2 fragmentation.

Work Style and Values

• "How do you feel about working in a fast-moving, ambiguous environment?" — Crypto moves faster than traditional tech. Companies want to know you won't freeze when requirements change weekly.

• "Tell me about a time you had to make a decision with incomplete information." — Directly relevant to crypto product development where the design space is novel.

• "How do you stay current with crypto developments?" — Follow-up: name specific sources, researchers, or communities you're part of.

• "What's your view on decentralization vs. product velocity?" — Tests whether you understand the core tension in Web3 product development.

• "Describe a time you disagreed with a technical decision. How did you handle it?" — Small crypto teams need people who can disagree constructively.

Remote Work

• "How do you structure your day working remotely?" — 90%+ of crypto jobs are remote. Companies want evidence you can be productive without oversight.

• "How do you handle async communication across time zones?" — Many crypto teams span 8+ time zones. Over-communication is valued.

---

Take-Home Projects: What to Expect

Common take-home assignments in crypto interviews:

For smart contract developers:

• Build a simple token vesting contract with tests (4–6 hours expected)
• Audit a provided contract and write a findings report (2–4 hours)
• Implement a mini DEX or lending mechanism (6–8 hours)

For frontend developers:

• Build a DApp that connects a wallet, reads contract state, and submits a transaction (4–6 hours)
• Create a dashboard displaying on-chain data from The Graph or an API (3–5 hours)

For non-technical roles:

• Write a governance proposal for a hypothetical DAO decision (2–3 hours)
• Create a go-to-market plan for a protocol launch (3–4 hours)
• Analyze a token's market structure and write a brief (2–4 hours)

Tips for take-home projects:

• Spend the first 30 minutes reading the requirements carefully. Missing a requirement is the #1 reason candidates fail.
• Write tests. Even if tests aren't explicitly required, they signal professionalism.
• Document your design decisions in a README. Explain what tradeoffs you made and why.
• Don't over-engineer. Companies want to see clean, working code — not an over-abstracted framework.

Interview Preparation Checklist

Before the interview:

• Use the company's product. If it's a DeFi protocol, make a small trade or deposit. If it's an NFT platform, browse and understand the UX.
• Read the company's documentation, governance proposals (if applicable), and recent blog posts.
• Review your on-chain activity. Some interviewers will look at your ENS or linked addresses.
• Prepare 2–3 questions about the team's engineering practices, security posture, or product roadmap.

Day of the interview:

• Have MetaMask (or your preferred wallet) ready if it's a live technical session.
• Be prepared to share your screen and walk through code, contracts, or dashboards.
• If asked about salary expectations, come prepared with data. Our crypto salary guide and Solidity developer salary breakdown provide current ranges.

After the interview:

• Send a brief follow-up with any additional context on discussion topics.
• If you did a take-home, submit on time and include a clean README.

Common Mistakes That Cost Candidates the Offer

• Not using the product. This is the most common disqualifier. If you can't explain how the protocol works from personal experience, you're at a massive disadvantage.

• Generic answers about "believing in decentralization." Every candidate says this. Show specific knowledge instead — mention a governance vote you followed, a protocol mechanism you find elegant, or a design decision you disagree with.

• Ignoring security in technical answers. Every smart contract answer should consider attack vectors. If an interviewer asks you to design a contract and you don't mention security considerations, that's a red flag.

• Not asking questions. Crypto companies expect candidates to be evaluating them as much as the reverse. Ask about treasury runway, token distribution, security audit history, or engineering team structure.

• Overstating experience. The crypto community is small. Claims are verifiable on-chain. Be honest about your experience level.

Ready to put your preparation to work? Browse open roles on GMI Jobs and find the right crypto role to interview for. For salary benchmarking, check our crypto engineer salary guide.