Backend Engineer

About the role

Mem0 is building the memory layer for AI agents, providing long-term memory that lets AI remember conversations and build real context over time. This Backend Engineer role owns the backend platform, designing clean REST APIs, modeling data across relational and graph stores, and operating services in production. You'll debug customer issues end-to-end, optimize performance, and collaborate with frontend and research teams. Based in Bangalore, Karnataka, India, this is a remote full-time position reporting directly to Co-founder and CTO Deshraj Yadav.

What you’ll do

• Design & ship REST APIs: define contracts, versioning, auth, rate limits; write migrations and docs
• Model data & schemas across relational (Postgres) and graph (e.g. Neo4j) stores; enforce integrity and performance
• Debug customer issues end to end: trace with logs, metrics and traces, reproduce, fix, and write preventative guardrails
• Optimize performance: tune slow SQL with EXPLAIN/ANALYZE, indexes, partitioning, pagination, and caching (e.g. Redis)
• Build services in Python: async where it helps (FastAPI, Django/DRF, Flask), background jobs, queues, schedulers
• Operate in the cloud: containerize with Docker, deploy on Kubernetes (EKS), and use AWS primitives (EC2, RDS/Aurora, S3, IAM)
• Instrument everything: custom metrics, structured logging, tracing; set SLOs and alerts (CloudWatch/Prometheus/OpenTelemetry)
• Collaborate & ship: work with frontend and research to scope APIs and deliver features to production

What you’ll bring

• 5+ years building backend systems and shipping REST APIs to production
• Strong Python fundamentals with experience in async programming and a major web framework (FastAPI/Django/Flask)
• Solid data modeling and SQL skills with hands-on query tuning and performance debugging in Postgres/MySQL
• Experience with graph databases (e.g. Neo4j or Amazon Neptune) and data modeling trade-offs
• Comfortable running services on AWS with Docker and Kubernetes
• Demonstrated root-cause analysis and ownership from incident to prevention
• Clear communicator and effective collaborator with frontend, research, and customers

Nice to have

• GraphQL/gRPC; event-driven systems (SNS/SQS/Kafka) and background workers (Celery/RQ)
• Caching, rate limiting, multi-tenancy, and feature-flag strategies
• Security & privacy best practices (PII handling, secrets management)
• Deep observability experience (OpenTelemetry, SLO-based alerting)
• Prior work with search/retrieval or memory systems
• On-call experience and running blameless postmortems
• Prior time at an early-stage startup; Series A, YC, or founding engineer experience

Skills