Blockchain Developer mock interview questions
19 questions a Blockchain Developer panel actually asks, with what each one tests and what a strong answer contains, then practice any of them live. Smart contract security and design round for blockchain developer interviews.
Answer one real Blockchain Developer question now
A question a Blockchain Developer panel actually asks, answered out loud, scored on what you said and how you said it. Under two minutes, and nothing to sign up for.
“Here is a withdraw function that sends ETH to the caller and then sets their balance to zero. What is wrong with it and how do you fix it?”
We never store the audio. Your answer is deleted within 24 hours unless you save the result.
- Adaptive follow-ups, not a fixed question list
- Rubric scorecard with evidence from your answers
- Voice or text, with delivery coaching on voice sessions
Thinking past the interview? Carmen can help with your whole Blockchain Developer career: a switch, a raise, or what comes next.
19 blockchain developer mock interview questions
The questions a Blockchain Developer panel actually asks, with what each one is testing and what a strong answer contains. Click any question to run it in a live session: your AI interviewer will cover it and score how you answer.
- 1.
Here is a withdraw function that sends ETH to the caller and then sets their balance to zero. What is wrong with it and how do you fix it?
Why they ask it: Reentrancy is the canonical smart contract vulnerability. Interviewers expect it recognised instantly and fixed properly.
A strong answer: The external call hands control to the caller, whose fallback can call withdraw again before the balance is zeroed. Fix with checks-effects-interactions by updating state before the call, add a reentrancy guard, and note that cross-function and read-only reentrancy can still bite if other functions rely on the same state. Checking the return value of the low-level call is part of a complete answer.
- 2.
How would you design an upgradeable contract, and what can go wrong with proxies?
Why they ask it: Upgradeability is a common production pattern with sharp edges.
A strong answer: A proxy that delegatecalls to an implementation, using a transparent or UUPS pattern. Risks include storage layout collisions when new variables are inserted rather than appended, uninitialised implementation contracts that anyone can initialise, constructors that do not run in proxy context, and centralisation of upgrade power, mitigated with a timelock or multisig. Mentioning tooling that checks storage layout between versions is strong.
- 3.
A lending protocol reads a token price from a single decentralised exchange pool. How could an attacker exploit that?
Why they ask it: Oracle manipulation, often funded by flash loans, is a major real-world attack class.
A strong answer: An attacker can borrow a large amount within one transaction, move the pool price, borrow against inflated collateral or liquidate others, then repay. Mitigations include time-weighted average prices, decentralised oracle networks with multiple sources, sanity bounds and circuit breakers, and not using spot prices from thin pools for critical decisions.
- 4.
Users complain a function costs too much gas. Where do you look?
Why they ask it: Gas optimisation shows understanding of how the EVM charges for work.
A strong answer: Storage reads and writes are the dominant cost, so cache storage values in memory, pack variables into fewer slots, avoid unbounded loops over storage, use calldata for read-only external parameters, emit events instead of storing data that is only needed off-chain, and use custom errors. A strong answer also warns against optimisations that hurt readability or safety for small gains.
- 5.
Your indexer shows transactions that later disappear from the chain. What is happening and how should the backend handle it?
Why they ask it: Tests understanding of finality and chain reorganisations, which matters for any off-chain system.
A strong answer: A reorganisation replaced recent blocks, so transactions in them were dropped or reordered. The backend should wait for a confirmation depth or the chain's finality signal before treating events as final, track block hashes to detect reorgs, roll back derived state when they occur, and show pending states in the UI.
- 6.
How do you test a contract before deploying to mainnet?
Why they ask it: Testing discipline matters more here than almost anywhere because deployed code is hard or impossible to change.
A strong answer: Unit tests for every function and revert path, fuzz tests and invariant tests for properties that must always hold, forked mainnet tests against real integrations, static analysis tools, a testnet deployment, an external audit for anything holding value, and a bug bounty after launch.
- 7.
Tell me about a time you found or responded to a vulnerability in code that was already deployed.
Why they ask it: Behavioural, tied to the defining pressure of the role: mistakes can be immediately and irreversibly exploited.
A strong answer: How the issue was found, how severity was assessed, the response options available such as pausing or upgrading, how disclosure was handled without tipping off attackers, and the process change afterwards.
How the Blockchain Developer interview runs
Most blockchain developer roles are smart contract roles on EVM chains, so interviews focus on Solidity, security and gas. Expect a recruiter screen, a technical round on contract vulnerabilities and chain mechanics, and a practical exercise such as writing or auditing a small contract with tests. Later rounds often cover protocol design, upgradeability, and how you would handle an exploit in production.
What the panel scores
Security
Whether you write and review contracts with an attacker's mindset.
- Recognises reentrancy, oracle and access control flaws
- Applies checks-effects-interactions
- Considers economic attacks, not just code bugs
EVM and chain knowledge
Whether you understand how contracts execute and settle.
- Knows gas cost drivers
- Understands finality and reorgs
- Understands delegatecall and storage layout
Design
Whether protocols are safe to operate and evolve.
- Plans upgradeability deliberately
- Limits admin power with timelocks or multisigs
- Includes emergency controls
Testing rigour
Whether code is proven before it holds value.
- Uses fuzz and invariant testing
- Tests against forked real state
- Plans audits and bounties
Common questions in every interview
These come up in almost every Blockchain Developer interview regardless of the company or the round.
- 8.
Tell me about yourself.
Why they ask it: Opens the interview and sets the frame. The interviewer is checking whether you can select what matters for this job rather than narrate your whole history.
A strong answer: A 60-90 second arc: where you are now, one or two proof points that match the posting, and why this role is the logical next step. Present, past, then future.
- 9.
Why do you want this role?
Why they ask it: Tests whether you read the job description or mass-applied. Weak answers are about what the candidate gets; strong answers connect to the work itself.
A strong answer: Two specifics from the posting or the company's actual work, plus an honest line about what you want to get better at here.
- 10.
Walk me through your resume.
Why they ask it: Checks that your story holds together and that the transitions were deliberate rather than accidental.
A strong answer: Chronological but fast, with a reason attached to each move and more time on the roles closest to this one.
- 11.
Tell me about a time you failed.
Why they ask it: Tests self-awareness and whether you own outcomes. Interviewers are listening for a real failure, not a disguised strength.
A strong answer: A genuine miss, what you specifically got wrong, the cost, and the concrete thing you changed afterwards that has since held up.
- 12.
Tell me about a conflict with a coworker or manager.
Why they ask it: Predicts how you behave when the team disagrees. The trap is blaming the other person.
A strong answer: The substance of the disagreement, what you did to understand their position, how it resolved, and what the working relationship looked like after.
- 13.
What's your greatest strength?
Why they ask it: Checks whether you know what you're actually good at and can prove it.
A strong answer: One strength that maps to the posting, plus a short example where it produced a measurable result.
- 14.
What's your greatest weakness?
Why they ask it: Tests honesty and whether you're actively working on something. Rehearsed non-answers ('I work too hard') read as evasive.
A strong answer: A real limitation that isn't core to the job, the system you built to manage it, and evidence it's improving.
- 15.
Tell me about a time you had to influence someone without authority.
Why they ask it: Almost every role depends on getting people who don't report to you to change course.
A strong answer: What you wanted, why they resisted, the evidence or framing that moved them, and what actually shipped as a result.
- 16.
Where do you see yourself in five years?
Why they ask it: Tests whether this job fits your trajectory, which is a retention question in disguise.
A strong answer: A direction rather than a title, and a line about the skills this role would build toward it. Vague ambition and rigid title-chasing both land badly.
- 17.
Why are you leaving your current job?
Why they ask it: Screens for red flags. Interviewers listen for how you talk about people you no longer work with.
A strong answer: Forward-looking and specific about what you're moving toward. Criticism of a former employer costs you more than it gains, even when it's deserved.
- 18.
What are your salary expectations?
Why they ask it: Checks whether you've done market research and whether you're in range before anyone spends more time.
A strong answer: A researched range with your target near the bottom of it, framed against the scope of the role. Deflect once if the posting has no band, then answer.
- 19.
Do you have any questions for us?
Why they ask it: The most under-prepared question in the interview, and the one that most changes the final impression.
A strong answer: Two or three questions about how the team actually works: what the first 90 days look like, how success is measured, what the hardest part of the job is.
Every round ends in a scorecard like this
Your Blockchain Developer answers, quoted back, scored on what this role is judged on, with the line to say instead.
Real screen from the app. Sample from a product design round.
Related roles
All Engineering →No spam. Unsubscribe anytime.
Ready to practice as a Blockchain Developer?
Sign up free, no card. 30 voice minutes and unlimited typed interviews, each ending in the complete scorecard: rubric scores, strengths, and what to fix next. Nothing is blurred.
- ✓ Predefined role or paste any job description
- ✓ Rubric scores with evidence quotes
- ✓ 888+ roles to choose from
Questions & answers
- Is the Blockchain Developer mock interview free?
- Yes. 30 voice minutes and unlimited typed Blockchain Developer interviews, no card. You get the complete rubric scorecard every time, with the evidence quoted from your own answers. Nothing is blurred.
- Can I use my own job description instead?
- Yes. Predefined roles are starting points. Paste any JD in the setup form and your AI interviewer will tailor questions to that posting.
- How is scoring tailored to this role?
- We pre-fill a realistic Blockchain Developer job description and interview format so questions and the scorecard match how this role is actually interviewed.
- Should I tailor my resume before practicing?
- Run a resume fit check against a Blockchain Developer job description first, then practice the interview with the same JD for a tighter loop.