Nuvento – India

For all the enquiries and resume submission 
please email to naseeba.parvin@nuvento.com

anindita.ghosal@nuvento.com

Build your Career with Nuvento

Location: Kochi, Kerala
About the Role

We’re modernizing a high-throughput, multi-service platform (Django/DRF + Celery backend, several coordinating internal services, React/TypeScript frontend) and migrating its deployment infrastructure to Kubernetes, while continuing to ship features across multiple environments (dev, demo, UAT, production). We need a Release Manager to own the release process end-to-end – planning, coordination, risk management, and go-live execution – working closely with engineering, QA, and the DevOps/Platform team. 

Responsibilities
  • Own the release calendar and cadence across all environments, coordinating code freezes, release windows, and blackout periods with engineering, QA, and business stakeholders.
  • Sequence rollouts across multiple customer-specific deployment environments, each with its own maintenance window and cutover timing - this is not a single-production-environment release model.
  • Define and enforce the release process: a defined versioning scheme (e.g., semantic versioning) and release train cadence, branching strategy, change approval workflow, required sign-offs (tests, migrations, security review), and release notes.
  • Run go/no-go decisions for each release based on test results, open defects, rollback readiness, and infrastructure readiness - escalating and holding a release when criteria aren't met, even under schedule pressure.
  • Coordinate cross-team release readiness: confirm database migrations, background-task/queue changes, feature flags, and configuration changes are sequenced correctly and communicated to all affected teams.
  • Govern feature-flag usage across releases: who can toggle a flag, when a flag graduates to permanent code or gets removed, and ensuring flag state is tracked as part of what's actually shipped in a given release.
  • Own rollback and contingency planning for every release: a documented rollback path, clear rollback triggers, and a tested procedure, not just a plan on paper.
  • Partner directly with DevOps/Platform on deployment execution - you own the "should we release and what could go wrong," they own the "how it gets deployed"; both roles need to be in sync on timing and readiness.
  • Own hypercare coordination immediately after each release: driving the stabilization window, tracking open issues against the release, and making the call on when a release is confirmed stable versus needs rollback.
  • Maintain release documentation: release notes, known issues, rollback runbooks, and a historical release log for audit and incident-review purposes.
  • Manage stakeholder communication before, during, and after releases - status updates, incident communication if a release causes an issue, and post-release retrospectives.
  • Own external customer communication for release-related downtime and maintenance windows, aligning timing with contractual SLAs and customer-specific notice requirements.
  • Track and report release metrics: release frequency, change failure rate, rollback rate, time-to-detect and time-to-resolve post-release issues.
  • Identify and drive process improvements to reduce release risk and manual toil over time (e.g., pushing toward more automated gating, better test coverage before sign-off, safer deployment patterns).
Required Experience
  • 6+ years in release management, release engineering, or a senior program/technical project management role with direct release ownership for production systems.
  • Demonstrated experience running releases for a system with both a web application and asynchronous/background processing (e.g., queued or scheduled jobs) - understanding that "the deploy succeeded" and "the system is healthy" are different questions.
  • Experience owning go/no-go decisions under real business pressure, including the judgment to delay or roll back a release.
  • Experience designing and enforcing a change management/approval process across multiple teams (engineering, QA, DevOps/infra, product).
  • Comfortable working with engineering and DevOps teams on release-relevant technical detail - database migrations, feature flags, environment configuration, rollback mechanics - without needing to personally execute the deployment.
  • Experience running hypercare/stabilization periods after major releases or go-lives, including defining exit criteria for when hypercare ends.
  • Strong stakeholder communication skills, including writing clear release notes and incident-style updates for non-technical audiences.
  • Experience with release/project tracking tooling (e.g., Jira, Azure DevOps Boards) and CI/CD pipeline visibility sufficient to track release status without being the pipeline's operator.
  • Solid hands-on proficiency with git: comfortable reading commit history and diffs, cherry-picking specific commits into a release branch, resolving cherry-pick conflicts, tagging releases, and reasoning about what is and isn't included in a given release cut - this is a hands-on skill for the role, not delegated to engineering.
  • Experience releasing into multiple customer-specific production environments (not just a single production instance), including sequencing rollouts and managing independent maintenance windows per customer.
Nice to Have
  • Familiarity with Kubernetes-based deployment concepts (rolling updates, canary/blue-green patterns) at a level sufficient to reason about risk, not to operate the cluster.
  • Experience in a regulated or compliance-sensitive environment where change control and audit trails are a hard requirement.
  • Background in QA or test management, giving informed judgment on whether test coverage is sufficient for a go/no-go call.
What Success Looks Like in the First 90 Days
  • A documented, adopted release process with clear roles, approval gates, and rollback requirements that all teams follow.
  • A release calendar in place and visible to all stakeholders, with freeze/blackout periods respected.
  • At least one release run through the full process end-to-end, including a hypercare window with a clean, criteria-based exit.
  • Baseline release metrics (frequency, change failure rate, rollback rate) established and reported.
Location: Kochi, Kerala
About the Role

We’re migrating a high-throughput, multi-service document-processing platform (Django/DRF + Celery, several internal services coordinating through shared task queues) onto Azure Kubernetes Service (AKS), targeting sustained throughput of 1,000+ files/hour with production-grade reliability and disaster recovery. We need a senior, hands-on engineer who can own this migration end-to-end and then run the platform day-to-day. 

Responsibilities
  • Design and build the AKS cluster topology: node pools segmented by workload (API/web, Celery workers, spot pool for low-priority/background queues), cluster autoscaler configuration, and workload placement via node selectors/taints.
  • Implement queue-depth-based autoscaling for Celery workers using KEDA (Redis/RabbitMQ scalers), replacing naive CPU-based HPA for latency-bound, LLM-call-heavy workloads.
  • Stand up managed data services: a managed PostgreSQL offering (zone-redundant HA, point-in-time recovery) and a managed Redis offering, migrating off self-hosted in-cluster database/cache/connection-pooler containers.
  • Own the disaster recovery program: automated backup/restore testing, defined RTO/RPO targets, and validation of application-level recovery paths (e.g., task/pipeline resumability via checkpoint models).
  • Build and maintain CI/CD pipelines for multi-service container builds, registry push, and cluster deploys across multiple environments, with per-environment config/secrets management via a managed secrets store.
  • Write and maintain infrastructure as code (Terraform or Bicep) for all cloud resources - no manual/click-ops changes to production infrastructure.
  • Implement observability: dashboards and alerts for API latency, queue depth/lag, worker autoscaling behavior, task failure rates, and resource saturation per service.
  • Configure ingress, TLS, and network policies across multiple internal services.
  • Tune resource requests/limits, concurrency, and prefetch settings per queue tier (default/priority/slow) based on real load testing against target throughput.
  • Partner with backend engineers on load testing, capacity planning, and incident response for pipeline run failures, stuck queues, and external connector outages.
  • Maintain runbooks for rollout, rollback, scaling, and disaster recovery procedures.
  • Set up and run hypercare monitoring around go-lives and major releases: heightened alert thresholds, active dashboard watch, and a defined escalation path for the stabilization window, tapering back to steady-state monitoring once the release is confirmed healthy.
  • Stand up 24x7 monitoring with proactive alerting (not just reactive dashboards): threshold- and anomaly-based alerts on API/queue/worker health routed to an on-call rotation with paging (e.g., PagerDuty/Opsgenie/Azure Monitor alerting), tuned to minimize noise and alert fatigue.
Required Experience
  • 7+ years in DevOps/Platform/SRE roles, including at least 4 years running production Kubernetes at scale (managed Kubernetes on a major cloud provider — AKS experience specifically preferred).
  • Demonstrated ownership of at least one Kubernetes migration or major platform re-architecture from start to finish, not just steady-state operation of an existing cluster.
  • Hands-on experience with Celery or an equivalent distributed task queue at scale, including queue routing, worker autoscaling, and debugging stuck/lost tasks under real production load.
  • Direct experience with KEDA or another event/queue-driven autoscaling approach (not just CPU-based HPA) — this is a core requirement, not a nice-to-have, given the I/O-bound nature of the workload.
  • Strong cloud background across compute, managed databases/cache, secrets management, storage, and networking (VNets, ingress controllers/gateways).
  • Infrastructure as code fluency (Terraform or Bicep) at a level where you design and review modules, not just apply existing ones.
  • CI/CD pipeline design for containerized multi-service applications, including secrets/config handling across environments.
  • Real database operations experience: backup/restore, point-in-time recovery, connection pooling, and performance troubleshooting on PostgreSQL in production.
  • Comfortable working directly with a Django/DRF + Celery backend — reading task routing config, diagnosing worker/broker issues, and coordinating with backend engineers on service boundaries.
  • Monitoring/observability ownership: able to define meaningful SLOs and alerting thresholds, not just build dashboards.
  • Prior on-call/incident response ownership for a production distributed system, with experience running or contributing to postmortems.
  • Experience designing and running 24x7 on-call coverage with a paging tool (e.g., PagerDuty, Opsgenie) and proactive, anomaly/threshold-based alerting - not just after-the-fact log review.
Nice to Have
  • Prior experience designing DR strategy for a system combining a relational database with asynchronous background processing (not just stateless web apps).
  • Experience with document/file-ingestion pipelines or connector-heavy architectures (e.g., third-party API integrations with retry/idempotency concerns).
  • Experience running LLM-backed or AI-agent workloads in production, and how their variable, I/O-bound latency affects autoscaling and cost.
  • Security-conscious defaults: least-privilege RBAC in Kubernetes, secret rotation practices, network segmentation between services.
What Success Looks Like in the First 90 Days
  • Cluster live in at least one non-production environment with queue-depth-driven worker autoscaling validated under load.
  • Managed database/cache migration plan (or completed migration) with a documented, tested backup/restore procedure and stated RTO/RPO.
  • CI/CD pipeline deploying to the cluster with zero manual apply steps required for a routine release.
  • A load test demonstrating sustained 1,000 files/hour throughput with documented bottlenecks and headroom.

What You Will Gain

  • Exposure to global enterprise clients and structured sales environments
  • Hands-on experience with AI-powered workflows and digital platforms
  • Understanding of sales funnels, lead nurturing strategies, and customer communication processes
  • Opportunities for learning, career growth, and internal mobility
  • Experience working within Nuvento’s MAGIC culture: Mastery | Accountability | Growth Mindset | Innovation | Customer Obsession