Evaluate Decentralized Finance (DeFi) Engineer candidates across 4 weighted areas: technical proficiency, systems and trade-offs, evidence and rigour, and collaboration and communication. Technical proficiency leads at 35%, so check depth in Solidity or Vyper: proxy upgrade patterns, assembly gas optimisation, Foundry or Hardhat test suites, ERC-20/4626 edge cases, and reentrancy or oracle. Use the rubric to compare role-specific evidence consistently.
For technical proficiency, look for evidence the candidate names specific contracts they wrote, explains storage layout and delegatecall risks precisely, and cites gas figures from real deployments. For systems and trade-offs, look for evidence the candidate argues trade-offs with economic reasoning, describing MEV exposure, capital efficiency, and admin key or timelock decisions they defended.
Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
Complete evaluation framework
What to assess and how to score it
Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.
01
Evaluation factor
Technical proficiency
35% weight
Check depth in Solidity or Vyper: proxy upgrade patterns, assembly gas optimisation, Foundry or Hardhat test suites, ERC-20/4626 edge cases, and reentrancy or oracle manipulation defences.
Evidence to listen for
Command of the languages, frameworks, and data tools the role actually uses
Understands correctness, performance, and failure modes, not just syntax
Has opinions on testing and can justify them
Reads and reasons about code they did not write
Five-point scoring guide
1
Poor
Cannot work independently; fundamentals are missing.
2
Needs Improvement
Weak fundamentals; output needs heavy review.
3
Satisfactory
Competent for the role; needs guidance on complex or unfamiliar work.
4
Very Good
Strong practitioner; handles hard problems with little guidance.
5
Excellent
Names specific contracts they wrote, explains storage layout and delegatecall risks precisely, and cites gas figures from real deployments.
02
Evaluation factor
Systems and trade-offs
25% weight
Probe architecture calls: AMM curve choice, liquidation engine design, oracle selection (Chainlink versus TWAP), L2 versus mainnet deployment, and where they accepted centralisation for safety.
Evidence to listen for
Reasons about scale, latency, cost, and failure before writing code
Names the trade-off they chose and what they gave up
Understands the data lifecycle end to end
Anticipates what breaks at ten times the volume
Five-point scoring guide
1
Poor
No thinking beyond the immediate task; no awareness of scale or failure.
2
Needs Improvement
Limited architectural awareness; struggles with design decisions.
3
Satisfactory
Works within an existing design; makes sound local decisions.
4
Very Good
Designs for scale and maintainability; articulates trade-offs clearly.
5
Excellent
Argues trade-offs with economic reasoning, describing MEV exposure, capital efficiency, and admin key or timelock decisions they defended.
03
Evaluation factor
Evidence and rigour
25% weight
Test verification habits: fuzz and invariant testing in Foundry, forked mainnet simulations, formal verification with Certora, audit findings received, and post-incident or bug bounty responses.
Evidence to listen for
Validates results rather than trusting output
Knows how their work is measured and what a bad result looks like
Can describe a time their own analysis or model was wrong and how they caught it
Careful about data quality, leakage, and silent failure
Five-point scoring guide
1
Poor
Ships unvalidated work; no notion of how correctness is checked.
2
Needs Improvement
Validates superficially; misses obvious quality or leakage issues.
3
Satisfactory
Reasonable checks in place; rigour drops under time pressure.
4
Very Good
Validates thoroughly; can name a real error they caught in their own work.
5
Excellent
Quotes coverage and invariants they wrote, describes an audit finding they disputed or fixed, and shows measured TVL or exploit outcomes.
04
Evaluation factor
Collaboration and communication
15% weight
Assess work with auditors, protocol governance forums, and DAO contributors: writing specs, snapshot proposals, and explaining contract risk to non-engineering token holders.
Evidence to listen for
Explains technical work to non-technical stakeholders
Gives and takes code or peer review constructively
Documents enough that the work survives their absence
Aligns with team process rather than working around it
Five-point scoring guide
1
Poor
Cannot work in a team; resistant to feedback.
2
Needs Improvement
Communication issues create rework; lone-wolf tendencies.
3
Satisfactory
Adequate team member; documentation and review participation are light.
4
Very Good
Communicates well; reliable reviewer and collaborator.
5
Excellent
Points to public governance posts or audit correspondence and explains complex mechanism risk plainly to treasury or community stakeholders.
Evidence-led prompts
Interview questions for a Decentralized Finance (DeFi) Engineer
Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.
01
Can you describe a DeFi project you worked on and a problem you had to solve on it?
02
Which DeFi protocols or platforms are you most familiar with?
03
Can you describe how you have worked with decentralised exchanges in your projects?
04
What approaches do you use for securing decentralised finance applications?
05
Can you explain the role of smart contracts here and how you have used them?
