By Peter Miller · Published September 14, 2026 · Last updated: September 15, 2026
11 min read
You're not missing callbacks because you forgot a logo. You're missing them because Workday never sees the floor: ticket volume, stack, on-call, production versus a lab.
How to get a job in IT isn't a cert pile plus forty product names. It's those four facts in the experience bullets a parser actually maps. Don't spray another requisition until you check your resume for free against the same posting. If the portal wants a letter, generate a cover letter that names the floor, not the tool dump.
Recruiters don't score a tool museum. They search for the environment they have to staff tonight.
So here's the move. Pull the floor out of the posting. Put it in the first eight words of your current job. Then stop adding products.
Do these three things first
- Open tonight's posting and highlight stack, ticket volume, on-call, and production versus lab.
- Rewrite the first bullet under your current job so those four land in the first eight words.
- Delete any tool in Skills that is not named in an experience or project bullet.
The floor Workday keeps and the tool list it parks
Workday and Greenhouse do not hire you for a product brochure. They import a file into fields: titles, employers, dates, a skills bucket, then the text of each job.
The Skills list doesn't get you screened in. The bullet that repeats the environment does.
I've screened IT files in Workday where Skills listed thirty tools and Experience never named ticket volume, on-call, or whether the stack was production.
That pattern is boring and specific. A help desk posting asks for a queue. A sysadmin posting asks for production servers and a change window. A cloud posting asks whether you touched prod subscriptions or a sandbox. If those facts only live in your head, the importer has nothing to map and the recruiter has nothing to search.
Job searching is already hard. You don't need a new personality. You need the floor in the bullets.
Read how to list skills on a resume after you lock the bullets. Skills is an index. Proof sits under Experience.
How to get a job in IT when the floor never makes the bullets
Step 1: Steal the floor from the posting
Don't start in Skills. Open the requisition. Highlight four things only: stack names, volume or seat count, on-call or shift language, and any hint of production versus lab, sandbox, or classroom.
Those four are what a recruiter types into Workday later. "ServiceNow" without a queue is a product. "40 to 60 ServiceNow tickets per shift, 900 seats" is a floor. Same product. Different search hit.
Postings leak the floor even when they look like keyword soup. "Follow-the-sun" means someone else owns nights, or you do. "PagerDuty" means on-call is real. "Homelab welcome" means they expect junior lab work and will still ask what was production. "HIPAA" plus desktop support means endpoints, not a cert slogan.
Edge case: The posting is only a tool dump. Infer the floor from the employer type. An MSP sells ticket volume. A hospital sells endpoints and change control. A product company sells production systems and a pager. Write that floor into the bullets, then match the two or three stack names they actually repeated.
Step 2: Rewrite current-role bullets around the floor
Take the first bullet under your current job. If the first eight words are "Responsible for troubleshooting" or a list of logos, rewrite it tonight.
Help desk, 80-seat MSP
Before: Responsible for troubleshooting hardware and software. Windows, Microsoft 365, Active Directory, ServiceNow, Slack, Zoom, Jira, Okta, printers.
After: Triaged 40 to 60 ServiceNow tickets per shift for a 900-seat office, L1/L2 Windows 11 and Microsoft 365, no after-hours on-call, production endpoints only.
Windows sysadmin, regional manufacturer
Before: Managed servers and implemented best practices across a hybrid environment using VMware, AWS, Azure, Terraform, Ansible, Kubernetes, Docker, Splunk.
After: Patched 80 production Windows servers (AD, file, print) on a monthly change window, on-call one week in four, no lab-only admin work in this role.
Junior cloud, SaaS ops
Before: AWS, Azure, GCP, Terraform, Kubernetes, Docker, Jenkins, GitHub Actions, Prometheus, Grafana.
After: Wrote Terraform for 3 production Azure subscriptions (app + data), weekday business-hours support, no pager, production only in this block.
Numbers inside those bullets are templates for your floor, not claims about the market. Swap in your real queue, seat count, rotation, and whether the work was prod.
Copy-paste this skeleton into a notes file and fill it once per current-job bullet.
Copy-paste IT environment bullet
[Verb] [volume or cadence] [stack] for [who or where], [on-call: yes/no and rotation], [production or lab]. [Result if you have one.]
Edge case: You carried unofficial on-call. Write it as unofficial and name the hours. Hiding it makes the next screen treat you as business-hours only. Inventing a formal rotation gets you caught in the first week. Unofficial Friday 6 p.m. to Sunday 8 a.m. for a 40-person office is still a floor. Put it in the bullet.
Homelab and bootcamp projects belong under Projects. Write "lab" in the first eight words so Greenhouse does not map a sandbox as a job. Production stays under Experience.
Step 3: Keep Skills as a short index, not the proof
Skills is where parsers park names. It is not where recruiters learn whether you sat a queue or shipped to prod.
Trim to the posting's stack plus what you can defend on a phone screen. Comma-separated, single column. No bars, no grids, no icons.
Then repeat each kept name inside a bullet next to volume or prod. If ServiceNow is in Skills and nowhere in Experience, the search may still find the word, and the human still has no floor. That is how a qualified help desk file looks like a brochure.
Certifications sit in their own block: full name, issuer, year. They do not replace the environment sentence. If tonight's posting names CompTIA A+, Network+, or Security+, copy the full cert name from CompTIA's certification catalog into Certifications with the year. Don't write a nickname the importer won't map. A+ without ticket volume still reads as classroom. AZ-104 without a production subscription still reads as study.
If you don't have a paid IT floor yet, a registered apprenticeship is a job with a sponsor, not a bootcamp recap. Search IT support and help desk occupations on Apprenticeship.gov , then list the sponsor, occupation title, and start month the same way you would a help desk role. Don't paste the program brochure into Skills.
The skills post walks placement and format. This page is the floor those skills have to attach to. Use both. Don't paste twenty adjacent products and call it Experience.
Step 4: Make Workday import the environment
A perfect bullet still dies if the importer reads a two-column template out of order. Build a single-column file. Standard headers: Summary, Experience, Education, Skills, Certifications. Dates inline with the title, Month Year, Present spelled out.
Put name, phone, email, and city in the body, not only in a header. Workday instances skip header regions. A blank phone on the candidate profile is a silent reject, not a formatting debate.
After upload, read every field. If the current job title lands in Skills, or dates vanish, the file still has a table or a text box. Rebuild rather than decorating. The Workday playbook is in the Workday resume format that parses cleanly.
Lean DOCX on older enterprise portals. A text-selectable PDF is fine on newer career sites. Never a scan. Never a design export that looks pretty and copies as garbage. If you want a machine pass before you click Apply, run a free ATS check on the same file you will upload.
Step 5: Put one environment line in the letter, then stop
The letter is not a second tool dump. One sentence should match the first experience bullet: volume, stack, on-call, prod versus lab. Then point at the requisition's floor, not at your enthusiasm.
That is the same rule as why personalized cover letters convert better: one proof line, not a biography.
Draft it in the cover letter generator, then paste your environment sentence so the letter and the resume agree. Two tools is enough. Checker, then letter.
This won't fix applying to senior SRE roles with six months of help desk. It stops a qualified IT file from looking like a product brochure while the queue, the pager, and the prod stack stay invisible.
Where IT files go quiet in the parser
A forty-tool dump is not experience. Parsers park it. Humans skip it. The search that matters is the bullet with volume and prod.
Lab work wearing a job title. Homelab under Experience makes Workday invent employment. Keep it in Projects and say lab.
One file for help desk and engineering. The floors differ. Rewrite the first bullet for the requisition you are in, or you look confused in both.
Certs stacked above a current job. The importer fills education-shaped fields first and the recruiter still has not seen your queue.
Hiding unofficial on-call. The next team will ask. Write the hours you actually covered.
Creative headers. "My journey" and "Toolbox" do not map. Use Experience and Skills.
Contact only in a header bar. Some Workday configs never read it. Phone in the body.
Spraying fifty portals before rewriting the first bullet. The same silent file hits every parser. Fix the floor once. Then apply.
Run the file against tonight's requisition
Environment work is wasted if Greenhouse imports a blank phone or a scrambled title. Upload the resume you will actually send and check your resume for free against the same posting. Fix parse order, dates, and missing contact first.
If the portal asks for a letter, keep it as short as the first bullet. Use the cover letter generator, then add one floor-proof line from Experience. Don't stack four tools. Two is enough: checker, then letter.
Rewrite the first bullet before you apply again
Getting callbacks in IT is not a longer tool list. It is ticket volume, stack, on-call, and production versus lab in the bullets Workday actually maps.
Open tonight's posting. Highlight the floor. Rewrite the first bullet. Trim Skills to names you can defend. Then leave the logos alone.
Pair this with why weak bullet points get ignored if the first eight words still start with "Responsible for." The environment has to show up as work, not as a caption.
Frequently asked questions
No. Keep Skills as a short index of the stack in tonight's posting plus what you can defend on a screen. Repeat the same names inside experience bullets next to ticket volume, on-call, and production versus lab. A tool that only lives in a dump does not prove you worked that floor.
Yes. Help desk files lead with ticket volume, seat count, L1 versus L2, and whether you owned a queue. Engineering files lead with production systems, change windows, and on-call. Do not ship one tool list to both requisitions. Rewrite the first bullet so the floor matches the posting.
Put lab work under Projects and write lab in the first eight words. Production roles go under Experience with ticket volume, stack, on-call, and prod versus lab stated plainly. Mixing them in one block makes Workday map a sandbox as if it were a job, and the phone screen will test the difference.
Only if you have almost no paid IT floor yet. For anyone with a current help desk, admin, or ops role, put Experience first so the importer fills jobs and dates before cert names. List the cert under Education or Certifications with the full name and year. A cert does not replace environment in the bullets.
Use a single-column DOCX or a text-selectable PDF. Avoid two-column templates, icons next to phone numbers, and scanned PDFs. After upload, read every auto-filled field before you continue. If titles, dates, or skills come back blank, fix the file and upload again.