Posted 30 August, 2026
Linux SME Walkin Interview@ Gurugram Location
Tata Consultancy Services
Gurugram, HR, IN
Full Time
Reference: 6b9efb1c1ad33267
Job Description
Linux SME Walkin Interview@ Gurugram Location
\nLinux SME
\nLocation: Gurugram, Haryana
\nAddress: TCS GG7 office is located at Skyview Corporate Park, Sector 74A, Gurugram, Haryana, 122004
\nExperience: 6 years to 13 years
\nInterview Mode: Walk In Drive
\nInterview Date: 8th Aug 2025 (Saturday)
\nInterview Time: 10: 00 AM to 1: 00 PM
\nMandatory skill set:
\n- \n
- Linux/UNIX Operations & Troubleshooting (L2/L3) \n
- OS Currency, EOL Remediation & Patch Execution \n
- Monitoring/Event Mgmt Tooling (ServiceNow ITOM, SolarWinds, Grafana) \n
- Cloud Operations (AWS/Azure Linux) & Automation Exposure (SSM/Ansible) \n
- DR Support, Documentation, Risk & Capacity Inputs \n
- Linux Tower Architecture & Standardization (Target baselines), EOL Burn-down Strategy + Patch Governance/Automation (SSM direction), Observability/Event Mgmt Integration (ITOM/SolarWinds/Grafana) \n
Certification:
\n- \n
- RHCSA/RHCE or equivalent Linux administration credential; ITIL Foundation/ ITIL 4 Managing Professional. \n
Must-Have:
\n- \n
- Provide L2/L3 operations for customer’s UNIX/Linux estate across on‑prem + AWS + Azure + VMware, with strong focus on OS currency (EOL remediation), patch compliance, monitoring/event management integration, and operational stability \n
- Ownership of end-to-end Linux tower delivery service and transformation — driving Linux standardization, EOL burn-down strategy, patch automation adoption, DR readiness governance alignment, observability maturity, and SLA-led operations, emphasizing event management, patching automation, risk registry, and operating model maturity. \n
Tools / Platforms
\n- \n
- ITSM / Event Mgmt / AIOps: ServiceNow, ServiceNow ITOM \n
- Infra Monitoring: SolarWinds \n
- Observability / Logs: Grafana (Prometheus stack), Loki/Fluentd \n
- Patching: AWS SSM direction for patching onprem + cloud; SCCM/Intune \n
- Automation/Orchestration: ServiceNow + AWX/Ansible + Terraform \n
- Batch: Control‑M / Tidal (where Linux workloads rely on scheduling dependencies) \n
Good to have:
\n- \n
- AWS Cloud Practitioner or AWS SysOps (for Linux on AWS); Azure Administrator (for Linux on Azure); ServiceNow fundamentals; Ansible basics. \n
- AWS Solutions Architect (or SysOps), Azure Solutions Architect, ServiceNow ITOM fundamentals, automation certs (Ansible/Terraform) \n
Key Responsibilities:
\n- \n
- Provide advanced troubleshooting and resolution for Linux incidents (availability, performance, filesystem, user/access, services, kernel-related issues). \n
- Support operational activities across on‑prem, AWS, and Azure Linux estates, aligning to the broader customer operating model for infrastructure operations and administration. \n
- Execute OS version upgrades and remediation for EOL/EOS Linux servers, prioritizing critical systems and high-risk populations (e.g., EOL VMs) \n
- Maintain compliance with “supported version levels” expectations by ensuring planned upgrades and reducing vendor support risk exposure. \n
- Perform patch planning/execution and support the customer’s direction to extend AWS SSM for patching across on‑prem and cloud, including pre-check/post-check automation and maintenance coordination. \n
- Operate within the approved tool landscape for patch/image management (SCCM/Intune) where relevant to server operations and standardization. \n
- Integrate Linux monitoring into Customer’s ServiceNow ITOM event management approach and downstream monitoring tools like SolarWinds, plus observability via Grafana/Loki where used. \n
- Improve alert quality by participating in tuning thresholds and reduction of noisy events, consistent with the customer event management direction. \n
- Support DR readiness activities for Linux workloads, aligning to the TDAF callout that periodic DR testing/governance must be established (execution support, runbook validation, recovery assistance). \n
- Provide operational inputs into capacity planning and proactive risk identification (CPU/memory/storage growth trends). \n
- Maintain Linux SOPs/runbooks and update CMDB/service records as required through ServiceNow, aligned to the tool strategy emphasizing ITSM/CMDB integration. \n
- Define the Linux OS standard/version baselines and a sequenced plan to reduce EOL exposure (including EOL VM populations highlighted in inventory) \n
- Drive estate rationalization across platforms (VMware/AWS/Azure) and ensure “supported release” posture to reduce operational and security risk. \n
- Establish patch policy, cadence, and compliance reporting; operationalize customer’s direction to extend AWS SSM patching for on‑prem and cloud, including automation of checks and standardized runbooks. \n
- Align patch/image practices to Customer’s retained tool ecosystem (SCCM/Intune). \n
- Ensure Linux signals (metrics/logs/events) are integrated into ServiceNow ITOM event management and correlated with downstream tooling (SolarWinds) and observability dashboards (Grafana/Loki). \n
- Sponsor alert-quality improvements (threshold strategy, noise reduction) \n
- Implement Linux tower contribution to DR readiness, aligned to the TDAF callout that DR drills/process governance must be mandated and executed, ensuring Linux workloads meet agreed RTO/RPO expectations by criticality. \n
- Define Linux tower SLAs/OLAs, measurement methods, and reporting cadence. \n
- Ensure Linux tower maintains and governs a risk register and operational documentation discipline via ServiceNow/CMDB integration. \n
- Serve as the Linux tower escalation owner for P1/P2 issues, stakeholder communications, and cross-tower coordination (Compute/Network/DB/Storage). \n
15 years of Continuous Education.