IT Resume for Career Shifters: Before and After Examples

A good IT resume for career shifters is one page, opens with a short summary and a skills section that mirrors the job post, then rewrites your old work in IT terms: tickets, troubleshooting, documentation, data and process. Add a projects section with two or three things you actually built, tested or configured. You're not hiding your BPO, teaching or retail years. You're translating them so a tech recruiter can see the overlap in six seconds.

Most career shifter resumes I review have the same problem. The experience is there, but it's written for the old industry. "Handled customer concerns" means a lot to a BPO team lead and almost nothing to an IT hiring manager. The fix is mostly rewriting, not inventing.

What should an IT resume for career shifters look like?

Keep it to one page. Unless you have ten years of directly relevant IT work, a second page just gives the recruiter more to skip. Here's the order that works for most shifters:

1. Name, city (Pasig, Cebu City, etc.), phone, email, LinkedIn URL, and a GitHub or portfolio link if you have one.
2. A three-line summary: target role, your transferable strength, and proof you've been learning.
3. Skills, grouped by type (more on this below).
4. Projects, two or three, each with one or two lines.
5. Work experience, most recent first, rewritten in IT language.
6. Certifications and training (Google IT Support, Cisco Networking Academy courses, Microsoft Learn paths, TESDA NC if relevant).
7. Education, short.

Notice that projects sit above work experience. When your last job title says "Customer Service Representative" and you're applying for IT Support Analyst, you want the recruiter to see relevant proof before they see the title.

No photo, no birthday, no religion, no "Objective: to obtain a challenging position." Save it as a PDF named something like Juan-Dela-Cruz-IT-Support-Resume.pdf, not resume final v3 (2).pdf.

Before and after: BPO experience

BPO agents have more IT-relevant experience than they think, especially anyone who took tech support calls for a telco or ISP. The trick is naming the tools and the process. If you need the bigger picture on making this switch, read the BPO to IT career shift guide.

• Before: Handled inbound calls from customers with internet concerns.
• After: Resolved Tier 1 connectivity issues (no internet, slow speed, modem resets) for a telco account, walking customers through router checks and escalating unresolved cases with complete notes.
• Before: Used CRM to log customer issues.
• After: Logged and updated cases in Salesforce with clear reproduction steps, so Tier 2 could pick them up without calling the customer back.
• Before: Consistently met KPIs.
• After: Kept average handle time within target while maintaining CSAT above team goal for [X] consecutive months. (Use your real numbers. If you don't remember them, ask your old team lead or check your scorecards.)

See the pattern? Name the issue type, the tool, the action and the result. "Tier 1," "escalated," "ticket," "root cause" and "knowledge base" are words IT people use daily. If you did them, say them.

Before and after: teaching experience

Teachers make strong QA testers, trainers and support staff because they document, explain and check work all day. Your resume just needs to stop sounding like a DepEd form. The teacher to IT career guide covers which roles fit best.

• Before: Prepared lesson plans for Grade 9 Science.
• After: Wrote structured, step-by-step learning materials for 200+ students per term, revising them based on assessment results. (Again, your real numbers.)
• Before: Checked and recorded student grades.
• After: Tracked and analyzed grades for multiple sections in Google Sheets, using formulas to flag students below passing for early intervention.
• Before: Served as ICT coordinator.
• After: Set up and maintained classroom laptops and projectors, handled basic troubleshooting for faculty, and managed Google Classroom accounts for the school.

That last one is gold, and a lot of teachers bury it under "other duties." If you were the person everyone called when the projector wouldn't connect, that's IT support experience.

Before and after: retail and supervisor experience

Retail and store supervisors bring inventory systems, reporting, scheduling and people handling. That maps well to data, operations and support roles.

• Before: Supervised store staff and handled daily operations.
• After: Supervised a team of [X] staff across shifts, building weekly schedules and training new hires on the POS system.
• Before: Did inventory counts.
• After: Reconciled weekly inventory against POS reports in Excel, found recurring variances and traced them to receiving errors.
• Before: Prepared sales reports.
• After: Compiled daily and monthly sales reports for the area manager, using pivot tables to break down sales by category and time of day.

If you did any of these in Excel or Google Sheets, name the specific features: pivot tables, VLOOKUP or XLOOKUP, conditional formatting. Data hiring managers scan for those.

Whatever your old field, run every bullet through this quick check before you send anything:

1. Does it name a tool, system or type of problem?
2. Does it start with an action verb (resolved, logged, built, reconciled, trained)?
3. Would someone outside your old industry understand every word?
4. Is every number real and something you could explain if asked?
5. Does it connect to at least one requirement in the job post?

A bullet that fails two or more of these needs rewriting, not polishing.

How do ATS filters actually read your resume?

ATS stands for applicant tracking system. Many bigger companies and BPO-adjacent IT firms use one to sort applications before a human looks. You don't need to game it, but you do need to avoid tripping it up.

• Use a simple single-column layout. Fancy two-column Canva templates sometimes get read out of order.
• Use standard headings: "Skills," "Projects," "Work Experience," "Education." Not "My Toolbox."
• Put text in text, not inside images or icons.
• Mirror the exact words from the job post where they're true for you. If the post says "Active Directory," don't only write "AD."
• Submit as PDF unless the posting asks for Word.

Here's the thing: keyword matching only gets you to a human. The human still needs to believe you. Don't paste the entire job description in white text at the bottom. Recruiters have seen that trick.

Building a skills section that doesn't look padded

A skills section with 30 items reads as "listed everything from a YouTube playlist." Group them and keep only what you could answer an interview question about.

For an IT support target, something like:

• Support tools: ticketing (Zendesk, Freshdesk), remote desktop tools, Microsoft 365 admin basics
• Systems: Windows 10/11, basic macOS, Active Directory user and password management
• Networking: IP addressing, DNS, DHCP, basic router and Wi-Fi troubleshooting
• Other: typing speed [X] WPM, written English documentation, Google Sheets

Drop "MS Word" and "Internet browsing." Everyone has those. Drop "fast learner" and "team player" from skills entirely; show them in your bullets instead.

The projects section is where career shifters win

Without a past IT job title, projects are your proof. They don't have to be impressive. They have to be real and explainable.

Good beginner projects for support roles: a home lab where you set up a Windows Server trial with Active Directory, or a written troubleshooting guide for common Wi-Fi issues you published on GitHub. For QA: test cases and bug reports you wrote for a public demo site. For data: a cleaned dataset with a dashboard in Google Sheets or Looker Studio.

Write each one like a work bullet:

• Home lab, Active Directory: Set up Windows Server in VirtualBox, created OUs, users and group policies, and documented password reset and account lockout steps. [GitHub link]

If you're not sure what to build first, the free IT Job Starter Kit has a resume template and a role picker if you're still deciding which job to aim for. Grab it, then come back and rewrite your bullets with the before/after pattern above.

Once your resume is done, make your LinkedIn match it. Recruiters check both, and mismatched titles or dates raise questions. The LinkedIn profile guide walks through that.

Getting a second pair of eyes on it

You can write a strong resume on your own with the patterns above. The catch is that after years in BPO, teaching or retail, your old job's language feels normal to you, so you can't hear it anymore. A reader who works with IT hiring can. In our Career Shifter Track, the resume is the week 3 assignment: you write six transferable bullet points, submit the full rewrite, and a coach replies in writing with which lines to cut, which to sharpen, and which keywords from your target postings are missing. Week 4 then lines up your LinkedIn with the same story, so the two never contradict each other. If you want to see how the lessons are laid out first, the program page lists every week.

Frequently asked questions

Should I remove my BPO or teaching experience from my IT resume?

No. Removing it leaves a gap that looks worse. Keep it, but rewrite each bullet in IT language and cut the duties that have zero overlap with the job you want.

Can my IT resume be two pages?

For most career shifters, no. One page forces you to keep only what's relevant. Two pages make sense once you have several years of actual IT work to show.

Do I need certifications on my resume to get interviews?

They help, especially entry-level ones like the Google IT Support certificate, because they show you've studied the basics. But a cert with no projects is weaker than one or two solid projects you can explain in an interview.

Should I write a different resume for every job?

Keep one master resume, then adjust the summary, skills order and two or three bullets for each role type. Tweaking for IT support versus QA takes ten minutes and noticeably improves the match.