Nobody Teaches the Real Onboarding: What New IT Hires Spend Their First 90 Days Actually Searching For
The certificate on the wall says you know Windows Server. It says nothing about the ancient printer driver locked to a departmental workstation, or the firewall rule nobody documented in 2019 that quietly keeps payroll running.
That gap between the official curriculum and the actual job has a shape. Look at the search behavior of IT professionals in their first 90 days at a new position, and a remarkably consistent pattern emerges — a shadow syllabus that repeats across enterprises from Des Moines to Dallas.
Week One: The Archaeology Phase
New hires rarely start by searching for technology. They start by searching for context.
The most common early queries are procedural and organizational: how to request access to a change management system, what a particular internal acronym stands for, how to read the ticket routing rules. Forum posts from first-week sysadmins cluster around one theme — figuring out who owns what. In enterprise environments, the answer to "who do I call about this VLAN" is often a person who left the company two years ago.
This is also when the predecessor's legacy becomes a daily obstacle. Unlabeled patch panels, scripts with no comments, and service accounts whose purpose nobody remembers. The searches here are desperate and specific: PowerShell syntax for auditing scheduled tasks, tools for mapping undocumented network dependencies, and — tellingly — whether it's acceptable to rebuild a server rather than reverse-engineer it.
Weeks Two Through Six: The Firewall Rule Hunt
By the second month, the questions get more technical, and one topic dominates disproportionately: firewall and access rules that exist in production but exist nowhere else.
Sysadmins describe a familiar ritual. An application breaks. The logs point to a dropped connection. The change history shows nothing. The only path forward is tracing a rule that was added during an incident years earlier, by someone operating on the theory that documentation could wait.
The searches that follow — comparing rule bases, exporting configurations to readable formats, understanding legacy VPN tunnel configurations — reflect a genuine skills gap. Security certifications teach the principle of least privilege. Very few teach how to excavate privilege that has already accumulated for a decade.
The Cloud Reality Check
Engineers moving from on-premises roles report a different curve. Their early searches center less on specific services and more on cost and governance — how billing alerts actually work, why a resource tag matters, what happens when a dev team spins up something that never gets shut down.
The pattern suggests that cloud transitions fail less from technical ignorance than from financial and procedural ignorance. The technology is well-documented. The organizational discipline around it is not.
What This Means for Hiring Managers
The shadow syllabus is, in part, an indictment of onboarding. When new hires spend their first month reverse-engineering undocumented infrastructure, the cost is measured in delayed productivity and elevated risk — a new administrator who doesn't know why a rule exists is one confident decision away from removing it.
Organizations that onboard well tend to share three habits:
- A living dependency map, even a rough one, that new staff can query before they have to ask
- Protected time with the outgoing or senior admin, structured around the questions new hires are already searching for
- A norm that documentation happens at the moment of change, not after the incident fades from memory
What It Means for New Hires
For the person starting the job, the lesson is to treat the first 90 days as a documentation project in reverse. Every time you search for something the company should have told you, write the answer down. The document you build in your first quarter is frequently the one that saves your successor — and establishes your reputation in the meantime.
The certifications got you through the door. The shadow syllabus is what you leave behind for the next person standing where you are now.