Aravind Prakash

DevOps | Tech enthusiast | cyber security researcher | AI-Ops

Vonnue · NILGIRI COLLEGE OF ARTS AND SCIENCE, THE NILGIRIS

About

Tech enthusiast | cyber security researcher | SRE | Backend dev

Experience

  • Vonnue (2 yrs 6 mos)
    • Senior Operations Engineer
      Dec 2024 - Present · 1 yr 11 mos

    • Sulthanbathery, Kerala, India
      Present

      Worked on the front line of production reliability, where failures are real, users are loud, and dashboards don't lie. Owned incident detection, triage, and investigation for customer-facing platforms at scale Correlated logs, metrics, traces, and real-user behavior to isolate failure domains quickly Diagnosed issues spanning distributed services, frontend delivery, APIs, DRM flows, and third-party dependencies Partnered with engineering teams during live incidents, supplying actionable data instead of assumptions Mentored L1 engineers to think in terms of systems, not tickets Improved operational maturity through runbooks, dashboards, and investigation playbooks Contributed insights that reduced repeat incidents and improved overall system reliability This role strengthened my foundation in observability, incident response, and reliability engineering, aligning closely with SRE / DevOps / Platform Engineering principles.

    • Operations Engineer
      May 2024 - Dec 2025 · 1 yr 8 mos

      I worked at the intersection of production systems, real users, and real failures — not toy problems. As an L1 TechOps Engineer, I was responsible for first-line investigation and incident triage across web and app platforms, ensuring issues were identified fast, scoped correctly, and escalated with context (not noise). What I actually did (and not just "monitored dashboards"): Investigated live production issues using New Relic (logs, dashboards, APM), browser DevTools, network traces, and API/GraphQL endpoints Performed root cause analysis at L1 level, isolating whether failures were frontend, backend, CDN, DRM, third-party, or user-environment related Monitored uptime, latency, error rates, and customer-impacting failures using tools like Pingdom & internal monitoring Acted as the bridge between support, engineering, and product, translating vague user issues into actionable technical findings Validated fixes, tracked regressions, and ensured issues didn't quietly return to production This role trained me to think like an engineer under pressure, not a ticket-closer — speed with accuracy, curiosity over assumptions.