Senior Backend Engineer

Veda builds vault infrastructure for DeFi  manage billions total value locked across 15+ blockchain networks, powering yield strategies for partners including Kraken, Etherfi, and Plasma. Our protocol turns complex multi-chain DeFi positions into simple vault interfaces that institutional and retail users can actually trust.

We’re hiring a Senior Backend Engineer to be a key design partner in our next-generation platform infrastructure. You’ll own the systems architecture that sits behind billions in assets, event indexing, data pipelines, risk engines, multi-chain orchestration, the infrastructure that has to be right because real money depends on it.

You won’t be handed a spec. You’ll look at what we have, understand where we’re going, and figure out what needs to be built, rebuilt, or thrown away. Then you’ll build it.

You’ll work with the team to evolve our production infrastructure from its current state into a platform that can scale with our growth. This means:

• Designing and building the services that power our vault infrastructure, event indexing across 15+ chains, data platforms for risk calculation engines, real-time position tracking, and the orchestration layer that ties it all together.

• Owning the cloud architecture end to end. We run on AWS. You’ll make decisions about how our services are deployed, how they scale, how they fail gracefully, and how we maintain them without hero culture.

• Building data pipelines that are fast, correct, and auditable. Our vaults execute complex DeFi strategies across multiple protocols, Aave, Morpho, Uniswap, and more. The data infrastructure needs to keep pace with on-chain state across every network we operate on.

• Making our systems observable and operable. Monitoring, alerting, runbooks, oncall-friendly architecture. You’ll help us move from “one person knows how this works” to “anyone on the team can diagnose this at 3am.”

• Working across the boundary between on-chain and off-chain. Vault state lives on-chain. Risk calculations, indexing, caching, and API serving happen off-chain. You’ll design where that boundary sits and how data flows across it.

• Communicating clearly about technical decisions. Writing design docs that the team can actually follow. Explaining tradeoffs to non-engineers. Turning ambiguity into shared understanding. This matters as much as the code.

• Deep cloud architecture chops. Significant experience with AWS in production at scale.

• You’ve designed and operated systems where uptime matters, not “we should have five nines” slide decks, but actual production systems handling real load with real consequences when they break.

• Strong systems engineering fundamentals. You’ve built event-driven architectures, data pipelines, caching layers, and API services that handle high throughput. You know the difference between a system that works in a demo and one that works during a bull market.

• IaC fluency. Terraform, CI/CD, containerization, Infrastructure as Code. You believe infrastructure should be reproducible, version-controlled, and reviewable.

• Excellent communication skills. You can write clear design documents, explain architectural decisions to teammates with different backgrounds, and have productive disagreements about technical direction. You make the people around you better by making complex things understandable.

• You’ve seen production at scale. You’ve lived through systems that scaled past their original design. You know what breaks first, what compromises are temporary, and what shortcuts become permanent regret.

• Strong opinions, loosely held. You’ve formed strong views through experience and you’re willing to defend them, but you change your mind when presented with better information. You care about getting…