Forty-six billion dollars. That is how much capital currently sits in Aave's smart contracts, earning yield, securing loans, and operating without a single human approving a transaction. No bank in history has achieved that level of automated trust this quickly. If you want to work somewhere that your code directly manages more value than most countries' GDP, Aave is the short list.
But working at Aave is not like working at a bank. It is not even like working at most crypto companies. The team is small, the stakes are enormous, and the relationship between Aave Labs (the company) and the Aave DAO (the governance layer) creates a dynamic that does not exist anywhere in traditional tech. Here is what that actually looks like from the inside.
What Aave Builds
Aave is a decentralized lending and borrowing protocol. Users deposit assets to earn interest. Borrowers put up collateral and take out loans. Liquidators keep the system solvent. All of this runs on smart contracts with no intermediary.
The protocol has gone through three major versions. Aave v3, the current iteration, introduced features like efficiency mode (allowing correlated assets to be borrowed at higher LTV ratios), isolation mode for risk-limiting new asset listings, and Portal for cross-chain liquidity transfers. The protocol is deployed across Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Base, and several other chains.
Then there is GHO, Aave's native stablecoin. GHO is minted by borrowers against their collateral within the Aave protocol, creating a revenue stream that flows to the DAO rather than to external stablecoin issuers. It is one of the more ambitious expansions of a lending protocol into monetary infrastructure.
With 96 public GitHub repositories, over 6,700 stars, and an Ethos score of 1903 ("reputable" level with 551 reviews), Aave is one of the most established and scrutinized codebases in all of DeFi.
Engineering Culture
The engineering team at Aave Labs is deliberately small. This is not a company that hires 300 engineers and organizes them into squads. The team operates more like a special forces unit — a handful of deeply experienced protocol engineers who each own significant portions of the codebase and carry real decision-making authority.
This has consequences. Autonomy is high, but so is the pressure. When your smart contracts custody $46.6 billion in TVL, every line of code matters in a way that is viscerally different from most software jobs. A subtle bug in a lending rate calculation could mean millions drained before anyone notices. A gas optimization that works on one chain but not another could break a multi-chain deployment.
Security is not a department at Aave. It is an obsession that permeates everything. Code goes through internal review, multiple external audits, formal verification where applicable, and community review through the governance process before it touches mainnet. If you are the kind of engineer who gets impatient with review processes, this is not your environment. If you are the kind who sleeps better knowing that every edge case has been hammered on by multiple sets of eyes, you will thrive.
Aave has processed hundreds of billions in cumulative lending volume without a major smart contract exploit. That track record is not an accident — it is the result of a security culture that treats every deployment as if a mistake could destroy the protocol. Because it could.
What Roles They Hire
Aave careers span several disciplines, though engineering is the center of gravity.
Solidity Developers / Protocol Engineers — The core hiring need. You will design, implement, test, and deploy the smart contracts that power the lending protocol, GHO, and new product expansions. This means writing Solidity that handles complex financial logic — interest rate models, liquidation mechanics, oracle integrations, cross-chain message passing — all at a level of rigor that would satisfy both external auditors and the governance community.
Frontend Engineers — The Aave interface (app.aave.com) is how most users interact with the protocol. Frontend engineers build React/TypeScript applications that communicate with the smart contracts across multiple chains, display real-time lending data, and handle wallet interactions. Multi-chain UX is a genuinely hard problem.
Risk Analysts — Aave manages risk across dozens of assets on multiple chains. Risk analysts model scenarios, set protocol parameters (LTV ratios, liquidation bonuses, borrowing caps), and monitor the health of the system. This role sits at the intersection of quantitative finance and protocol mechanics.
Product Managers — Coordinating between engineering, governance, community, and the broader DeFi ecosystem. PMs at Aave need deep protocol knowledge because every product decision has governance implications and economic consequences.
DevRel / Integration Engineers — Aave is a composability layer for DeFi. Other protocols build on top of it. Integration engineers help third-party developers use Aave's contracts, SDKs, and APIs, which requires both strong communication skills and a genuine understanding of the protocol's architecture.
Tech Stack
If you are applying for a technical role, here is what you should be comfortable with:
- Solidity — Expert level. You should understand storage layout optimization, the proxy patterns Aave uses for upgradability, and how to write gas-efficient code that remains readable and auditable.
- Foundry / Hardhat — Aave's codebase uses both. Foundry for its speed and fuzzing capabilities, Hardhat for deployment scripting and some legacy tooling. Be fluent in at least one; conversant in both.
- TypeScript — For frontend development, SDK work, deployment scripts, and tooling. TypeScript is the glue language of the Aave ecosystem.
- The Graph — Aave uses subgraphs to index on-chain data for the frontend and analytics. Understanding how to write and deploy subgraphs is valuable.
- Multi-chain deployment — Not just "deploy the same contract to another chain." Multi-chain at Aave means managing different oracle setups, gas parameters, governance configurations, and bridge integrations per chain.
- OpenZeppelin — Aave's contracts build on and extend standard OpenZeppelin patterns. Deep familiarity with AccessControl, proxy patterns (especially UUPS), and ERC20 implementations is expected.
Before applying, read the Aave v3 codebase on GitHub (github.com/aave). Seriously. Reading how they structure their contracts — the separation between the Pool, the PoolConfigurator, the PriceOracle, and the various strategy contracts — will tell you more about what the job requires than any job description.
Interview Process
Aave jobs are competitive. The interview process reflects the seriousness of the work.
Initial Screen — A conversation about your background, your understanding of DeFi, and why Aave specifically. Generic "I want to work in crypto" answers will not cut it. They expect you to understand how the lending protocol works at a mechanical level — what happens when a position becomes undercollateralized, how interest rates adjust based on utilization, what role flash loans play in the ecosystem.
Technical Assessment — For Solidity roles, expect either a take-home contract implementation or a live coding session. The problems are DeFi-flavored: implement a simplified lending pool, design a liquidation mechanism, optimize a contract for gas. They are not looking for speed — they are looking for correctness, security awareness, and clean code.
Protocol Deep Dive — A conversation with senior engineers about protocol design. You might discuss how you would add a new feature to Aave, how you would handle a specific risk scenario, or how you would approach a cross-chain deployment challenge. The goal is to assess whether you can reason about systems that handle billions in value.
Security Mindset Evaluation — This shows up throughout the process, not as a separate stage. Every technical discussion includes security considerations. Can you identify the vulnerability in a code snippet? Do you instinctively think about reentrancy, oracle manipulation, and flash loan attacks? This is not optional knowledge — it is table stakes.
The process is thorough but not drawn out. Aave is a small team and they respect candidates' time. Expect 3-4 rounds over 2-3 weeks.
Compensation and Aave Salary
Working at Aave comes with competitive DeFi-level compensation. Based on available data and comparable protocol roles:
| Level | Estimated Base Salary | Total Comp (with AAVE tokens) |
|---|---|---|
| Mid-Level Engineer | $160,000 - $210,000 | $250,000 - $380,000 |
| Senior Engineer | $200,000 - $260,000 | $350,000 - $500,000 |
| Staff / Lead | $240,000 - $280,000+ | $450,000 - $600,000+ |
| Risk Analyst | $140,000 - $200,000 | $200,000 - $350,000 |
| Product Manager | $150,000 - $220,000 | $250,000 - $400,000 |
AAVE tokens are a meaningful component of total compensation. The token has established liquidity and a multi-year track record, which makes it less speculative than tokens at earlier-stage protocols. That said, token compensation still carries market risk — your total comp will fluctuate with the price of AAVE.
Aave Labs operates as a remote-first company, which means compensation is generally benchmarked against global DeFi rates rather than adjusted for location. This works in your favor if you are based outside of San Francisco or New York.
The DAO Dynamic
This is the part that makes working at Aave genuinely different from almost any other employer in tech.
Aave Labs is a company. It has employees, a CEO (Stani Kulechov, the founder), and a corporate structure. But the Aave protocol is governed by the Aave DAO, where AAVE token holders vote on proposals that control everything from which assets are listed to how protocol revenue is allocated to whether Aave Labs' own proposals get implemented.
In practice, this means the code you write at Aave Labs does not automatically ship. Major protocol changes go through a governance proposal process: an initial discussion on the governance forum, a Snapshot temperature check, and then an on-chain vote. Your work needs to convince not just your engineering lead but also the broader community of token holders, delegates, and risk service providers who evaluate every change.
This can feel slow if you are coming from a startup where the CTO just decides what ships. But it creates a level of rigor and transparency that is rare in software development. Your code is reviewed publicly. Your design rationale is debated openly. And when something does ship, it has been stress-tested by a community that has billions of dollars at stake.
The other implication: Aave Labs is not the only entity building on Aave. Other teams submit governance proposals, build integrations, and contribute to the protocol. You are part of an ecosystem, not just a company. Some engineers love this distributed model. Others find the lack of unilateral control frustrating. Know which camp you are in before applying.
Who Thrives at Aave
Based on the culture and the work, the people who do well at Aave tend to share a few characteristics:
- Security-first thinkers. If your instinct when reading code is to look for what could go wrong, you belong here.
- DeFi natives. You use the protocol. You understand liquidation mechanics not from a textbook but because you have watched them happen on-chain. You have opinions about interest rate models.
- Self-directed operators. With a small team and high autonomy, nobody is going to micromanage your calendar. You need to be the kind of person who identifies what needs to be done and does it.
- Governance-comfortable. You are okay with your work being publicly debated and voted on. You can write a governance proposal that is technically precise and also readable by non-engineers.
- Multi-chain thinkers. Aave runs on eight-plus chains. You cannot think in Ethereum-only terms.
How to Position Yourself
If you want to maximize your chances of landing an Aave role, here is what actually moves the needle:
- Read the Aave v3 codebase. Understand how Pool.sol works. Trace a supply transaction from the user's wallet through the contract. Understand how the aToken rebasing mechanism works.
- Participate in Aave governance. Read proposals on governance.aave.com. You do not need to vote (you would need tokens for that), but understanding the governance process demonstrates genuine interest.
- Build something on Aave. Fork the protocol on a testnet. Build a simple integration. Write a liquidation bot. Demonstrable hands-on experience with the actual codebase is more valuable than any resume bullet point.
- Contribute to open issues. Aave's GitHub repositories have open issues. Even a well-crafted PR on documentation or test coverage shows initiative.
- Understand GHO. The stablecoin is a major strategic priority. Having an informed perspective on its mechanics and growth strategy signals that you think about Aave as a system, not just a lending pool.
The team is small and the bar is high, but for the right person — someone who combines deep Solidity skills with DeFi fluency and a security-first mindset — Aave is one of the most compelling places to build in all of Web3.
Explore current Aave jobs on gm.careers or browse related Solidity developer roles and DeFi engineer positions to find your next opportunity.