Lead Engineer - Systems

Altimetrik · Bangalore

Source and collection record

Last observed by our collector: 8 October 2026 at 11:02 pm IST. This is not a manual review or a confirmation from the employer.

Employer requisition: 906773

Job type and experience labels are automated discovery categories. The employer determines eligibility. Original experience wording was not retained separately; check the current employer page.

How sourcing and classification work · Report a discrepancy

Your application evidence checklist

Mark the statements you can support after reading the employer source. This checklist stays on this page; it does not score your eligibility or submit an application.

Attendance and availability: I checked the employer page for work location, office attendance, start date and duration.Current requisition: I checked the current employer requisition and its application requirements.

0 of 2 checks marked. Keep unresolved requirements as questions for the employer.

Collected role description

Application Support Engineer — L3 Responsibilities Own incident resolution across priority levels, RCA, and problem management Advanced diagnostics across MySQL, PostgreSQL, SQL Server, app logs, queues and integration interfaces Author new SQL and PowerShell scripts; mid-level .NET log and code investigation Patching, backup, and DR operations execution and validation Coach L2 engineers; maintain runbooks, KEDB and knowledge articles Hold SME ownership in one domain: Reporting / Clearing / Chargeback / Patching / Host interface / Message processing Represent support in change reviews and post-incident reviews; drive preventative actions to closure Shift-based coverage aligned to the agreed support roster, including on-call rotation Reliability & SRE Practices Define and maintain SLIs/SLOs for the owned domain; track error budget burn and escalate reliability risk Build automation that removes toil — auto-remediation, diagnostic tooling and scripted runbooks Own observability for the domain: dashboards, structured logging standards, distributed tracing, and ing on golden signals Lead blameless post-incident reviews; manage MTTR and incident recurrence as tracked metrics Monitor capacity and performance — throughput headroom, queue depth, database growth — and warn before saturation Plan and execute resilience testing: DR failover drills, backup restore validation and controlled game days Apply production readiness criteria to new releases (monitoring, runbook, rollback path) and use IaC/CI-CD to make operational changes repeatable and auditable Technical Skills MySQL, PostgreSQL — deep hands-on; SQL Server — mid-level PowerShell and SQL — authoring new scripts independently .NET — mid-level (code and log-level diagnostics) AWS (ECS, EKS, RDS, CloudWatch); Coralogix, Grafana / Grafana Cloud, PagerDuty, Jira Service Management Distributed tracing and metrics instrumentation (OpenTelemetry) — able to instrument and interpret traces, not just build dashboards Payments domain — card issuing and processing, plus one of ISO 8583 / ISO 20022, clearing and settlement, or chargebacks and disputes PCI DSS and FCA operational resilience — working knowledge ITIL-aligned incident, problem, and change management SRE practice — SLI/SLO definition, error budget tracking, toil reduction, blameless postmortems Infrastructure-as-code (Terraform / CloudFormation) and CI/CD pipelines for automated, auditable remediation Good to Have: Kubernetes operations at scale · Chaos engineering · AI-assisted troubleshooting tooling in a controlled environment · Confluence · Payments/fintech background

Collected experience requirement

4 - 6 Years