BACKEND HEAVY -PLATFORM ENGINEER
Delhi NCR, IndiaFull-timeMid · 2-3 years
About this role
BACKEND HEAVY -PLATFORM ENGINEER
Engineering · Platform
📍 Noida 🕐 Full-Time 🧭 2-3 Years 🧩 Backend 60-70% / DevOps 30-40%
THE MISSION
We aren't automating scripts — we're deprecating the era of manual-heavy testing entirely. TestMu AI is building the world's first AI-native platform where Agentic Intelligence autonomously plans, authors, and self-heals the entire Quality Engineering lifecycle.
Build the backend systems and platform services — in Go — that power an AI-native platform, and own how they scale, deploy, and stay reliable.
THE PILLARS OF IMPACT
🚀 1. Backend Engineering (65%)
– Build custom platform services, tooling, and automation in Go — real solutions, not config or glue scripts.
– Design event-driven systems with Kafka, Redis, and MySQL.
– Develop and own APIs and service-layer logic end to end.
– Solve logical and automation problems by writing code, not wiring up off-the-shelf tools.
⚙️ 2. Infrastructure & DevOps (25%)
– Deploy and operate services on AWS and Kubernetes.
– Own service scaling, traffic management, and deployment pipelines.
– Handle AWS-level networking and platform performance.
🧠 3. Reliability & Incident Management (10%)
– Instrument services with APM and observability (New Relic, Sumo Logic, or similar).
– Lead incident response with strong SRE principles and resolve production issues swiftly.
– Build safeguards and strategies to prevent recurrence.
MUST-HAVES — DO NOT APPLY UNLESS YOU HAVE THESE
– You must be strong in Go (mandatory). Rust or Java is acceptable if you don't know Go; Python/JS only as a last resort.
– You must have real, production-grade coding ability — you build custom solutions, not just configure or script existing tools.
– You must know Kafka, Redis, and MySQL.
– You must have hands-on AWS and Kubernetes — service scaling, traffic management, deployment, and AWS-level networking.
– You must have observability/APM experience (New Relic, Sumo Logic, or similar) and reliability/SRE thinking.
– You must be able to explain service-layer architecture and reason through trade-offs effectively.
THE BAR — WHAT YOU MUST PROVE
Backend Building: Built custom platform services or tooling in Go (or Rust/Java) that other engineers rely on.
Event-Driven Systems: Designed and shipped systems using Kafka, Redis, and MySQL at real scale.
Cloud & Scale: Deployed, scaled, and managed traffic for services on AWS and Kubernetes.
Incident Management: Led resolution of critical production incidents and instrumented services with APM.
Architecture Understanding: Explained complex service-layer architecture and defended design trade-offs.