Role Middleware and Linux Platform Engineer (L2): addendum to the

core CIMS Platform Engineer JD

Seats (Year 1 / Year 3) 2 / 2

Location India-based. 24x7 shifts with handover overlap. On-call rota for

escalation.

Minimum experience 5+ years in middleware or file-transfer operations on Red Hat

Enterprise Linux in production (proposed, pending approval).

Reports to Technical Lead (L2 lead for middleware)

Purpose

The middleware and platform engineer keeps the CIMS file-transfer and messaging layer running. That covers the ProFTPd

SFTP service, the Apache reverse proxy in the DMZ, IBM MQ and MFT interfacing, and the Red Hat Linux servers beneath

them. The client runs RHEL from version 5 to 9 across on-premises and Azure, so the role needs diagnostic depth across

that range. Infrastructure, OS patching and network changes stay with the client's infrastructure team; this role diagnoses,

fixes at the application and middleware layer, and coordinates the handoffs.

Responsibilities

 Diagnose Linux faults on RHEL 5 to 9: file systems and inodes, CPU, memory and swap, NFS mounts, file ownership

and permissions, service accounts and scheduled jobs.

 Run and fix the SFTP (ProFTPd) and Apache reverse proxy services in the DMZ, including TLS and proxy configuration.

 Administer IBM MQ for CIMS interfacing: queue managers, channels, queues, dead-letter queues and error logs;

coordinate MFT changes with the integration team.

 Manage the certificate and key lifecycle for TLS, SFTP keys and AS2 certificates: inventory, expiry, renewal and change.

 Write and maintain scheduled path, permission and file-age checks that feed monitoring.

 Support the SFTP portal application and the FTP event daemon on JBoss and Linux, and track ProFTPd version

currency (the TDD lists two ProFTPd versions, one of them 1.3.4b).

 Coordinate with the client's infrastructure,



network and integration teams on cross-boundary faults (on-premises and

Azure).

Must-have skills

 Red Hat Enterprise Linux diagnostics on RHEL 5 to 9: logs, processes, load, CPU, swap, file systems, inodes and

permissions (must-have).

 IBM MQ administration in production: queue managers, channels, queues, dead-letter queues and MQ error logs

(must-have).

 Capacity and storage on NFS-mounted document stores: growth, purge rules and inode use (must-have).

 Certificate and key management: keytool or openssl, keystore formats (JKS, PKCS12), expiry tracking and renewal

(must-have).

Job description. Anonymised for posting. Confirm before publishing.

 SFTP and reverse-proxy services in production: ProFTPd or equivalent, Apache HTTPD with mod_proxy and TLS (must-

have).

 Scripting for monitoring checks, with Bash plus Python or Perl, and exit codes that Nagios reads (must-have).

 AI-assisted delivery: uses an approved AI assistant for log analysis and runbook drafting, and checks its output (must-

have).

Nice to have

 Windows Server administration for DMZ nodes.

 Azure virtual machines and networking awareness (RHEL 9 on Azure).

 Kubernetes or AKS awareness.

 Managed file transfer (MFT) product experience.

 NSS or OpenSSL TLS library awareness.

 Security Vault component: client-specific credential and secret handling (learned in knowledge transfer).

 Hybrid on-premises-to-Azure bridge component: how it carries messages across the boundary.

Tools

Red Hat Enterprise Linux 5 to 9; IBM WebSphere MQ; ProFTPd; Apache HTTPD; Nagios; ServiceNow; Microsoft Azure

(VMs); GitHub Copilot.

How success is measured

 Partner file-transfer incidents resolved within P1 and P2 windows.

 Certificates and keys renewed before expiry, with zero expiry incidents.

 Fewer Linux file-system and permission incidents, with checks that catch them before the partner does.

Pay: ₹291,000.00 - ₹1,600,000.00 per year

Work Location: Remote

📌 Middleware and Linux Platform Engineer-Contract (India)
🏢 Ultrafly Solutions Private
📍 India