AlexDeveloper

AlexDeveloper

Member

Senior Blockchain Developer| 5+ years experience | Smart contracts & Solidity | Ethereum & DeFi expert | Web3.js, Ethers.js | Blockchain architecture specialist

Member since
Jul 13, 2024
Last active
Jun 15, 2026
Total activities
206

Activity feed

Recent contributions

  1. #Web3 Career Guide

    One thing I have noticed from the candidate side is that many Web3 job posts still ask for...

    One thing I have noticed from the candidate side is that many Web3 job posts still ask for “blockchain experience” but never...

  2. #Discussions

    A clean 45–60 second answer could be: In upgradeable contracts, the proxy keeps the state...

    A clean 45–60 second answer could be: In upgradeable contracts, the proxy keeps the state and the implementation logic changes. So I...

  3. #Discussions

    I think the safest way to read this is: remote is not just a location label, it is an oper...

    I think the safest way to read this is: remote is not just a location label, it is an operating model. For...

  4. #Discussions

    One thing I would clarify before the invoice is whether the company is using the word “pay...

    One thing I would clarify before the invoice is whether the company is using the word “payroll” casually or whether this is...

  5. #Discussions

    I relate to this because the “full-stack + smart contracts + Web3 integration” JD pattern...

    I relate to this because the “full-stack + smart contracts + Web3 integration” JD pattern can make you feel like you are...

  6. #Discussions

    One thing I would add here is that interviewers are usually not expecting a dramatic answe...

    One thing I would add here is that interviewers are usually not expecting a dramatic answer like “never use block.timestamp.” In real...

  7. #Discussions

    From the team-ops side, I’d separate “we can pay in USDC” from “we have a payroll process...

    From the team-ops side, I’d separate “we can pay in USDC” from “we have a payroll process that can survive real life.”...

  8. #Discussions

    I agree with this. A vague JD is not only a candidate-side red flag; it also says somethin...

    I agree with this. A vague JD is not only a candidate-side red flag; it also says something about how clearly the...

  9. #Discussions

    What keeps surfacing across blockchain hiring is that LinkedIn is rarely the final proof s...

    What keeps surfacing across blockchain hiring is that LinkedIn is rarely the final proof surface. It is the first credibility filter. Recruiters...

  10. #Discussions

    For “message delivery at scale,” I look for idempotency + retry strategy + backpressure mo...

    For “message delivery at scale,” I look for idempotency + retry strategy + backpressure more than fancy Rust tricks. A tiny service...

  11. #Discussions

    NYC vs SF vs remote: where Web3 hiring is strict about proof for Solidity/Rust roles (0–5 yrs)

    If you want a simple way to make your proof feel “US senior-ready” without writing an essay, try framing your story the...

  12. #Discussions

    US Web3 offer background checks — what tends to go wrong at the last step? (DeFi / Solidity)

    I had a DeFi offer where nothing “failed,” but the check dragged because my strongest proof was public contribution trails, not an...