Find the IT work you want to try
Search for “IT intern” and more specific terms such as “IT support intern,” “systems intern” or “cloud intern.” Read whether the assignment supports users, maintains infrastructure or works with a business application.
Check location, enrollment, dates and the requested skills on the original posting. The Gartner example below has a specific graduation target and stated deadline; its listed tracks do not guarantee the work you would receive.
Read the tasks behind the IT title
BLS distinguishes direct user support from network testing, troubleshooting and maintenance. An employer's IT program can also include software development, security or data work. Read the project descriptions before deciding what to prepare.
Choose a sample that resembles the assignment
| Work area | An intern-sized task to ask about | Practice evidence |
|---|---|---|
| Help desk or user support | Diagnose a user's access or device problem | A clear ticket, safe checks and a tested resolution |
| Cloud or infrastructure | Support a deployment, inventory or operational check | A permitted lab with setup, failure handling and cleanup |
| Business systems | Trace a workflow through an application | Requirements and test cases for a proposed change |
| Data or software within IT | Build or check part of an internal system | Code or a data reconciliation with reproducible tests |
Sources[1]
Check the Gartner example
A specific 2027 posting shows why the details matter
Gartner's Summer 2027 IT Intern posting, requisition 113095, lists an October 9, 2026 application deadline and May 2028 graduation. As reviewed September 17, it requires commuting distance to Stamford, Connecticut, U.S. work authorization and relevant technical study. The requirements list computer science, math or a related engineering field and software-development fundamentals.
Its listed work areas include development, cloud, AI integration, security and data science. That is not a general help-desk opening. The posted hourly estimate is $17–$25, with employer-stated qualifications that actual rates can differ. Confirm the actual assignment and offer rather than treating the range as guaranteed pay.
Sources[2]
Build a safe lab project
Build one small system you can restore or explain
On your own device, use a toy application or sample files to document installation, a common failure and recovery. Keep versions and prerequisites in the instructions. Have another person follow them without your narration.
For a cloud exercise, check the service's current prices and account limits before provisioning anything, then document cleanup. A local exercise is preferable when you cannot bound the cost. Do not buy a certification simply because the role says IT; first identify the skills or credentials the actual vacancy requires.
Include the symptom, checks, resolution and how you verified the result. Remove personal records and secrets. Label a lab as a lab rather than claiming responsibility for an employer's infrastructure.
Practice troubleshooting
Practice a problem you can investigate without unsafe shortcuts
Fictional ticket: ‘I can sign in, but I cannot open the team's shared project.’ Successful sign-in does not establish permission to every resource. Start by recording the exact error, resource and affected account, without collecting passwords or tokens.
The useful output is the evidence that narrows the problem. It is not ‘gave everyone administrator access.’ Test only systems you own or are explicitly authorized to use.
A safe investigation plan for the fictional access problem
| Check | What it helps distinguish | Boundary |
|---|---|---|
| Confirm the intended resource and exact error | A wrong link versus a real access problem | Do not paste private links into a public portfolio |
| Check the documented account role with the authorized owner | Expected restriction versus a missing approved permission | Do not change access simply to make the error disappear |
| Re-test the intended task after an approved correction | Successful sign-in versus successful completion | Confirm with the user and record the actual result |
Ask about review and escalation
Ask who reviews changes and handles escalation
‘What access would an intern receive? Which changes require approval? Who helps when I cannot resolve a ticket?’ Also ask about shifts, office days and on-call expectations.
A useful internship lets you understand why a fix worked. Choose between offers partly on whether someone reviews your diagnosis and documentation, not simply on how many technologies appear in the title.