Smart Contract Developer
Resume Metrics

Lean on description instead. Numbers help, but the size and aim of what you did carry weight without one. Wrote the protocol's first invariant suite? Drove the contracts from no audit to a clean sign-off? Fixed the security standard every new function must meet? All of them register as genuine impact, and not one depends on a figure you never had. The descriptive cards higher up show a worked example for every type.

A careful estimate is fine, provided the math holds and you can explain the steps to an interviewer. Say gas fell by something like half once you refactored a contract but no one recorded it: "gas roughly halved" is legitimate. Where the real numbers are confidential, use relative percentages. The rule that never bends: the figure has to be reproducible on demand.

Skip it. Made-up numbers fall over the instant a panel starts probing, and contract figures always get probed: a technical interviewer may ask which audit signed it off, or how you reached that gas number. One bogus stat can bury an interview that was otherwise going well. A descriptive point is far safer; it stands firm and still lands.

No. Save your figures for whichever bullets genuinely do the work in your most recent role, the block a recruiter reads first. Tag every single one and your strongest lines fade into the crowd, and soon you are padding with weak stats. A lean, defensible set outdoes a resume papered with numbers.

Go with the harder-hitting one, provided it is honest. Proportional wins land cleanest in percent ("cut gas 60%"); a large absolute total speaks for itself ("80M secured in TVL"). A lone percentage tied to nothing should go, since "improved efficiency 40%" only begs the against-what question. If there is space for both, pair them up: "cut gas per mint 54%, from 180k to 82k."

You can, and those numbers are more reachable than most juniors expect. The gas on a function before and after your fix, the count of contracts you shipped, coverage you raised, or vulnerabilities you spotted before mainnet all sit within an early internship or something you built on the side. Nobody expects revenue; they want a sign you improved something real.

For contracts still on-chain, a chain explorer like Etherscan carries your gas, transaction counts, and deployment history; run a Foundry gas report and it itemizes each function's cost within seconds; your audit reports hold every finding you resolved. For total value locked and value secured, pull from a dashboard like DeFiLlama. Where the project is long dead, estimate carefully and flag that you did.

Keep it to one. The single figure at the summit, your secured value or your best gas or audit result, is what buys those ten seconds. Everything else can live down in the work-experience bullets, and the summary itself stays fast to read. My smart contract resume guide shows how to write it.