Backend Engineer
Summary
Designs, builds, and scales the backend services and APIs behind Veda's DeFi yield platform, owning projects end-to-end from design through production, testing, and on-call. Core stack: Python (or Go/Rust/Java/C++), Postgres/MySQL, REST APIs, Docker/Kubernetes, and AWS/GCP cloud.
About:
Role:
Responsibilities:
- Design and build scalable backend systems powering Veda’s API and internal services
- Own projects end-to-end — from scoping and design to implementation, testing, and production delivery
- Collaborate with product and infrastructure teams to turn technical debt into modern, maintainable, and highly available systems
- Write clean, well-tested code, and maintain strong CI/CD hygiene
- Deploy, monitor, and scale services in production using modern cloud tooling (AWS, GCP, or similar)
- Contribute to system design discussions covering performance, reliability, and data architecture
- Participate in on-call rotations and incident response for production systems
- Continuously identify and drive improvements in system reliability, observability, and performance
Qualifications:
- 6+ years of professional backend engineering experience
- Proven experience delivering production systems end-to-end (scoping → design → implementation → production)
- Strong programming skills in Python or another modern backend language (e.g., Go, Rust, Java, C++)
- Solid understanding of REST APIs, relational databases (Postgres or MySQL), and service-based architectures
- Experience with version control (Git), unit/integration testing, and CI/CD pipelines
- Familiarity with cloud environments (AWS, GCP, Azure) and containerization (Docker, Kubernetes)
- Experience participating in an on-call rotation or owning production systems
- Demonstrated ability to design scalable systems and refactor legacy components
Preferred Skills & Experience:
- Experience in fintech, crypto, or other high-availability systems
- Familiarity with asynchronous task queues, event-driven architecture, or distributed systems design
- Prior experience in startups or early-stage, high-ambiguity environments
- Contributions to open-source projects or technical leadership on significant internal initiatives