Skip to content

Strategy

Can't fill your IT job? The posting is an inventory, not a role

A listing for helpdesk, network, security and the ERP is an inventory of what one person carried. In all but the smallest estates, three of its four parts can't be held by any single hire.

Computing America IT. Help desk support, backups and network infrastructure.

Send the posting
4 min readComputing America
An office chair piled with keys, lanyards, badges and a coil of network cable.

In short

  • A posting that lists helpdesk, network, security and a line-of-business system describes more than one role. It's an inventory of what one person accumulated over years.
  • Sort a duty list by what each item demands (presence, availability, specialist depth, continuity of knowledge) and in all but the smallest estates one hire can hold only the first.
  • Availability is structural. A person sleeps, takes leave and eventually resigns, so one person alone is not a commitment to answer when the business is closed.
  • Co-managed IT is a written split: your hire owns presence and relationships, an outside team owns depth and continuity, and out-of-hours cover where the agreement provides it. An offer that winds down on the day you hire is staffing with a different invoice.
  • Write the inventory down before the knowledge leaves. It's the document a replacement provider would build in its first two weeks, and it's worth most while the outgoing person can still answer questions.

A posting like this can stall, or get reposted with the word senior added, because it asks one person to be four kinds of hire: someone present, someone reachable out of hours, a specialist, and the keeper of years of context. A typical posting reads like this:

  • Run the service desk and administer Microsoft 365 and Entra ID.
  • Own the firewall and the site-to-site VPN.
  • Manage endpoint protection, patching and backups.
  • Answer the customers' security questionnaires.
  • Be the expert on the ERP.

Five to seven years of experience, one regional salary.

How the list got that long

One person doesn't get all of that by decision. Each line arrived the week it broke. The Wi-Fi went down at the second site and they fixed it, so the network became theirs. An auditor asked who owned patching and they were the only one in the room who knew. Every step was locally sensible and cost nothing at the time, because the person absorbing it was competent and didn't complain.

The result is invisible until it leaves. The organization has no document describing it, because the document was a person. The posting is the first time anyone has written the estate down, and a manager wrote it from memory and a calendar.

Sort it by what each line demands

The list looks like one job because every item is IT. Sort it by what each item asks of whoever holds it, and the shape changes.

Fig. 1
  1. Presence

    The desk, the floor, joiners and leavers

    • To Your hire
  2. Your hire

    Known by name, in the building

  3. Availability

    Answering at 11 p.m. or over a long weekend when the firewall, the VPN or a restore fails

    • To Outside team · Only where agreed
  4. Depth

    Identity design, segmentation, backup architecture, the ERP, the questionnaire

    • To Outside team
  5. Continuity

    Why that VLAN exists, what the last provider changed

    • To Outside team
  6. Outside team

    Specialists, documentation, cover where agreed

One hire holds presence; an outside team holds depth and continuity, and availability only where a written agreement names who answers.

SourceThe co-managed arrangement this article describes.

  • Depth breaks in the expensive direction. A generalist guesses at identity design or segmentation, and the guess stays invisible until an auditor or an attacker tests it.
  • Continuity breaks by construction. It lived in the person who left, and a new hire starts at zero.

Why availability can't be fixed with effort

Yes, the person who left did answer at eleven at night. The business still had no availability commitment. NIST SP 800-61r3 (opens in a new tab) treats response as defined roles with stated responsibilities, coordinated against a plan that exists before the incident does. Our reading is that who is reachable, and by when, should be a property of the organization, not of one person's goodwill. When a single administrator is on a plane or in a hospital, no one is on call.

What co-managed means, and the test for it

Your hire keeps the desk, the floor and the joiners and leavers, and stops being the only person who has configured the firewall or knows why the VLAN exists. The outside team owns depth and continuity, and out-of-hours cover where the agreement provides it.

One limit applies to us. We're two engineers: we answer within one business hour, Monday to Friday, 8:00 to 18:00 Central, and we publish no after-hours rota. Where after-hours cover is in an agreement, it names who you call and what it costs. If you need a standing out-of-hours commitment, the availability column is one to buy from a provider that publishes a rota. Ask any provider for its rota in writing: who answers, how fast, at what price.

The split has to be a document, per system, with a name against each line. Two parties both loosely responsible for patching is worse than one named party, and the failure is silent until the month it wasn't covered.

Ask any provider what happens to a co-managed arrangement on the day you make the hire. If it winds down, you were offered a contractor to keep the lights on until you replace them. That's a legitimate product. Price and scope it as one.

A real co-managed arrangement changes what you recruit: a good generalist with a team behind them, not a network engineer, a security specialist and a password-reset person in one.

Ask the second question too: when we leave, what do we hold? The handover pack sets out what a good answer contains.

When one hire is enough

If the honest total across all four columns is one full-time job (a single site, a small staff, no line-of-business system anyone would call complex), hire the person and write down who answers when they cannot. And if the estate needs somebody on site most days, a remote arrangement will underserve you however good it is. Both are answerable in a 45-minute call, before anyone quotes.

Do this now, ideally before the last day

  1. 1.Mark each line of the posting with its column. Half an hour.
  2. 2.Sit with the person who is leaving and write down what isn't on the list: which vendor holds which circuit, what the shared-password account is for, what breaks every quarter, what they were about to do next and why. If they have gone, ask the previous provider for the same.
  3. 3.Establish who holds the keys, in whose name. Tenants, domains, licenses and circuits registered to a departing individual or a previous provider are a common lock-in, and the ownership record is rarely checked.
  4. 4.Restore one file and one mailbox item to another location. A backup dashboard doesn't count. Do it while the person who knows the system is still around.
  5. 5.Then decide the shape: hire, co-manage, or both. You can't decide it honestly before the inventory exists.

Sources

  1. 1.SP 800-61r3: Incident Response Recommendations and Considerations for Cybersecurity Risk Management (opens in a new tab), NIST

Next step

Send us the job posting.

Paste the duty list exactly as you posted it. We will sort it into the four columns this piece sets out and say which lines we would expect one hire to hold, and which ones need more than one person behind them to mean anything.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing