Blockchain Developer
Interview Questions.

What the interviewer is looking for: A strong answer clearly distinguishes between permissionless and permissioned access, decentralization levels, and consensus mechanisms. Red flags include confusing privacy with permissioning or providing generic, non-specific use cases.

What the interviewer is looking for: A strong answer defines a Merkle Tree as a tree of hashes, where each leaf node is a hash of a data block and each non-leaf node is a hash of its children. It should highlight its use in verifying data integrity and efficient verification of transactions (e.g., in Bitcoin's blocks). Inability to explain its efficiency benefits is a red flag.

What the interviewer is looking for: The candidate should identify the 'oracle problem' – smart contracts cannot directly access external data. A strong answer will explain how oracles act as bridges, fetching and verifying off-chain information, and discuss challenges like data integrity, trust, centralization risks, and latency. Not mentioning the trust aspect of oracles is a red flag.

What the interviewer is looking for: The candidate should define smart contracts as self-executing, tamper-proof agreements on a blockchain. They should highlight automation and immutability as key differentiators from legal contracts. A good answer provides a clear, concise scenario like escrow or voting. Vague or incorrect definitions are red flags.

What the interviewer is looking for: A strong answer defines immutability as the inability to change data or code once recorded on the blockchain. It should highlight its benefits (trust, transparency) and also discuss its disadvantages, such as difficulty in bug fixing, upgrading contracts, or responding to unforeseen legal/regulatory changes. Not addressing the downsides is a red flag.

What the interviewer is looking for: A strong answer will explain that upgradeability allows modifying contract logic without changing its address or state, addressing immutability's drawbacks. Common patterns like Proxy Contracts (e.g., UUPS, Transparent Proxy) should be discussed, highlighting their use of delegatecall. Not mentioning the delegatecall mechanism is a significant red flag.

What the interviewer is looking for: A strong answer correctly identifies 'msg.sender' as the address of the caller and 'msg.value' as the amount of Ether sent with the call. The candidate should provide practical examples, such as restricting access or handling payments. Confusion between these or incorrect usage indicates a lack of fundamental understanding.

What the interviewer is looking for: A strong answer explains that 'payable' allows a function to receive Ether. The candidate should provide a clear use case, such as a crowdfunding contract or a token sale. Forgetting to mention that it's required for a contract to receive Ether directly via a transaction is a red flag.

What the interviewer is looking for: The candidate should correctly differentiate 'require' (for validating inputs and conditions before execution), 'assert' (for checking invariants and internal errors), and 'revert' (for custom error messages). A strong answer will explain their gas cost implications and when to use each for optimal contract design. Misunderstanding their specific use cases is a red flag.

What the interviewer is looking for: The candidate should explain that a provider connects Web3.js to an Ethereum node. A strong answer will demonstrate knowledge of common providers like HttpProvider, WebsocketProvider, or the in-browser provider (MetaMask). Incorrect syntax or misunderstanding the connection mechanism are red flags.

What the interviewer is looking for: The candidate should explain that the ABI (Application Binary Interface) describes the contract's functions and events, while the address specifies its location on the blockchain. A strong answer will mention obtaining the ABI from compilation artifacts (e.g., Hardhat/Truffle) or block explorers. Confusion about their roles is a red flag.

What the interviewer is looking for: A strong answer defines gas as the unit of computational effort on the Ethereum network, explaining its role in preventing spam and fairly compensating miners. The candidate should know that running out of gas causes the transaction to revert, but the gas consumed is still paid. Confusion about gas price vs. gas limit is a red flag.

What the interviewer is looking for: A strong answer will list key ERC-20 functions like 'totalSupply', 'balanceOf', 'transfer', 'transferFrom', 'approve', 'allowance', and events like 'Transfer' and 'Approval'. The candidate should explain the purpose of each, especially the 'approve'/'transferFrom' pattern for delegated transfers. Missing core functions or events indicates a gap in understanding token standards.

What the interviewer is looking for: The candidate should correctly identify the scoping rules (function, block) and re-assignment capabilities of each keyword. A strong answer will emphasize 'let' and 'const' for modern JavaScript development due to block scoping, promoting 'const' for immutable references. Misunderstanding hoisting or scope is a red flag.

What the interviewer is looking for: A strong answer defines hashing as a one-way function producing a fixed-size output (hash/digest) from input data. It should highlight properties like determinism, collision resistance, and avalanche effect, explaining its use in linking blocks (block header hash) and ensuring data integrity. Confusing hashing with encryption is a red flag.

What the interviewer is looking for: The candidate should outline the steps: clone, make changes, add to staging, commit, and push. A strong answer will mention common commands like 'git clone', 'git add', 'git commit', 'git push', and ideally 'git status' or 'git log'. Skipping steps or incorrect command usage are red flags.

What the interviewer is looking for: The candidate should clearly differentiate PoW's reliance on computational power from PoS's reliance on staked assets. A strong answer will discuss energy consumption, security against 51% attacks, decentralization, and scalability for both. Mixing up their characteristics or failing to mention key trade-offs are red flags.

What the interviewer is looking for: A strong answer defines reentrancy as a vulnerability where an external call can call back into the original contract before its state has been updated. Prevention methods like Checks-Effects-Interactions pattern, reentrancy guards, and using 'transfer'/'send' for Ether transfers (with their gas limits) should be mentioned. Not knowing prevention techniques is a red flag.

What the interviewer is looking for: The candidate should name either Hardhat or Truffle and describe the basic steps: setting up a project, writing tests (e.g., using Mocha/Chai), and running them on a local blockchain (like Hardhat Network or Ganache). A strong answer shows familiarity with the chosen framework's CLI. Lack of practical steps is a red flag.

What the interviewer is looking for: A strong answer will mention components like collateral management, interest rate models, liquidation mechanisms, and token interactions (e.g., ERC-20, ERC-721). Security considerations should include reentrancy, flash loan attacks, oracle manipulation, integer overflow/underflow, and access control. A lack of specific DeFi knowledge or security awareness is a red flag.

What the interviewer is looking for: A strong answer will present a clear problem, detail the steps taken to diagnose and resolve it, and reflect on the lessons learned. The candidate should demonstrate problem-solving skills, resilience, and the ability to learn from experience. Blaming others or providing a trivial problem/solution are red flags.

What the interviewer is looking for: The candidate should articulate genuine interest in blockchain technology, perhaps linking it to personal projects, industry trends, or its potential impact. Mentioning specific aspects like decentralization, security, or innovative applications is good. A generic answer or lack of enthusiasm is a red flag.

What the interviewer is looking for: A strong answer will list specific resources like official documentation, reputable blogs, forums (e.g., Stack Exchange, Reddit), conferences, or following key figures on social media. It demonstrates proactiveness and a commitment to continuous learning. Claiming to 'just read online' without specifics is a red flag.