Pay grades and fair increments in IT infrastructure and managed services

The P1 bridge call has run for two hours. The L3 who finally finds the faulty trunk on the core switch is paid less than a newly hired L2 on the same shift. The L2 came through a hurried campus drive when the contract was ramping. The L3 knows, because payslips get compared over tea in the NOC. A week later he is interviewing at a cloud firm. Infrastructure and managed service teams do not lose engineers to a big salary alone. They lose them to pay that cannot be explained.

This guide is for owners and delivery heads of IT support firms, managed service providers, networking service companies, cloud service companies and data centre operators. It builds grades from the work, shows how to keep on-call and night pay separate, and sets out an increment cycle with a fixed calendar. Pair it with our compensation benchmarking service when you want market ranges.

Rung and track: service desk, field, network, systems, cloud, data hall.
Handles alone: the fault types and change types signed off for this rung.
Needs a second pair of eyes for: firewall rule changes, hypervisor patching, production cutover, SAN zoning.
Writes: runbook pages, RCA drafts, handover notes at shift change.
Teaches: the next rung down, in shadow sessions.
Evidence: three live scenarios scored by a lead, plus ticket quality sample.
Pay range: floor, midpoint, ceiling, set by the firm after market checks.

A typical ladder runs from L1 service desk analyst to L2, L3, shift lead, service delivery manager and architect. In a data centre the ladder includes rack and stack technician, cabling specialist, facility technician for UPS and cooling, and a duty manager. Do not force one ladder onto both worlds. See the role design page for managed service providers for a start.

• Service desk: first contact fix, ticket notes that another engineer can follow, and Active Directory lockout and mailbox cases closed without a callback.
• Network: switchport and VLAN changes, transceiver and firmware swaps, routing failover drills, and clean config backups after each change.
• Systems: hypervisor patching, snapshot discipline, backup restore tests, Zabbix or Grafana alert tuning and replication checks.
• Cloud: Terraform or Ansible code reviews, cost tagging, load balancer rules and the quality of the post-incident write up.
• Data hall: PDU and busbar loads, chiller and CRAC alarms, generator test runs, cable labelling and the discipline of the visitor log.

Some engineers hold skills the market prices high: BGP routing, SAN zoning, VMware clusters, Kubernetes operators, OT networks in a factory. A manager who bargains with each one privately creates envy. Publish a short list of scarce skills, review it twice a year, and attach a skill allowance with an end date. When the market cools, the allowance lapses by rule and nobody feels singled out.

• Night rotation, weekend pager, patch window attendance and customer site travel are conditions of the rota. Pay them as allowances, written in one rulebook that every delivery manager follows.
• Priority one call-outs after midnight should have a stated rate and a stated rest rule for the next day.
• Standby without a call and standby with a call are two different things. Define both.
• A colocation floor with raised flooring, hot aisle and cold aisle conditions may merit a different duty allowance from a cosy office. Say so openly.

Allowances inside base pay make day staff look underpaid and night staff look overpaid. The first move from nights to days then becomes a quarrel. See the attendance page for IT support firms for rota ideas.

Vendor exams for networking, hypervisors or cloud platforms are signals of effort. They are not proof of judgement during an outage. Make an exam one input to eligibility for the next rung, alongside the scenario check. If the firm pays for the exam, add a short service commitment, and have a qualified professional review the wording. Without such rules, engineers collect badges and leave for a rival.

1. 1

   Announce the date in the first quarter

   Everyone should know the month that decisions are taken and the month that new pay begins.

2. 2

   Run the scenario checks two weeks before

   Each engineer faces live cases for their rung. Leads score them against a rubric.

3. 3

   Map people against ranges

   List engineers below the floor, within the range, and at the ceiling. A ceiling case needs a promotion, a role change or a one time award.

4. 4

   Agree the pool

   Split it by scenario result, delivery record, range position and critical skills. Keep a small reserve for corrections.

5. 5

   Hold the individual talks

   Every engineer hears the outcome in a ten minute conversation before any letter.

6. 6

   Audit afterwards

   Compare outcomes by team, gender, site and manager. Fix distortions in the next cycle.

A network service company, a cloud firm and a support firm may use the same title with different market value. Check three pages before copying ranges. Start with the compensation page for networking service companies. Then the benchmarking page for cloud service companies. Last, the rewards page for IT support firms.

The full list of business types is on the IT infrastructure and managed services HR hub. If you wish to build grade cards with help, begin with the requirements form.