You’ve applied to dozens of IT jobs. Maybe hundreds. Your resume lists every certification, every project, every technology you’ve touched. And yet—silence.

Here’s the uncomfortable truth: your resume probably isn’t getting read by humans. Applicant tracking systems (ATS) filter out most submissions before a recruiter ever sees them. And even when humans do look, they spend an average of 7.4 seconds deciding whether to keep reading or move on.

That’s not enough time to appreciate your home lab. It’s not enough time to understand your growth trajectory. It’s barely enough time to scan for keywords.

This article breaks down what actually works. You’ll see real resume structures (with commentary on why they work), templates for different experience levels, and the specific changes that get IT professionals more interview callbacks.

Why Most IT Resumes Fail

Before looking at examples, you need to understand why so many resumes never make it past the first filter.

The ATS Problem

Roughly 75% of resumes never reach human eyes. Applicant tracking systems scan for specific keywords, formatting patterns, and relevance signals. If your resume doesn’t match the job description closely enough—or uses formatting the ATS can’t parse—you’re automatically rejected.

Common ATS killers include:

  • Tables and columns (many systems can’t read them)
  • Headers and footers with important information
  • Embedded images or graphics
  • Fancy fonts or non-standard formatting
  • PDF files that aren’t text-based (scanned documents)

The Human Problem

When your resume does reach a person, you face a different challenge. Hiring managers and recruiters are overwhelmed. They’re looking for reasons to say no, not reasons to say yes. Your job is to make the “yes” obvious within seconds.

The biggest human-side problems:

  • Burying your best achievements under a wall of responsibilities
  • Listing technologies without context (knowing Docker matters less than what you did with it)
  • Generic objective statements that could apply to anyone
  • Typos, grammatical errors, or inconsistent formatting
  • Too much irrelevant experience, not enough relevant focus

The Positioning Problem

Many IT professionals write resumes that accurately describe their jobs—but don’t position them for the jobs they want. There’s a difference between documenting what you did and selling why you’re the solution to someone’s hiring problem.

If you’re a help desk technician who wants to move into system administration, your resume shouldn’t read like a help desk resume. It should emphasize the sysadmin-adjacent work you’ve already done.

Resume Structure That Works

Before diving into examples, here’s the structure that consistently performs well across IT roles:

The Ideal Order

1. Header (name, phone, email, LinkedIn, location—city and state only)

2. Professional Summary (3-4 sentences max, targeted to the specific role)

3. Technical Skills (organized by category, matching job description keywords)

4. Professional Experience (reverse chronological, achievement-focused)

5. Projects/Home Lab (only if relevant and impressive—see our guide on how to showcase home labs on your resume)

6. Education & Certifications (brief, at the bottom unless you’re entry-level)

What to Leave Out

  • Objective statements (outdated, replace with professional summary)
  • “References available upon request” (assumed, wastes space)
  • Full address (city and state is enough)
  • Photo (creates bias issues, unprofessional in US/UK)
  • Every job you’ve ever had (focus on relevant experience, last 10-15 years max)
  • Skills you can’t actually demonstrate in an interview

Entry-Level IT Resume Example

This is what works when you’re breaking into IT with no experience. The key is demonstrating potential through projects, certifications, and transferable skills.

What Entry-Level Done Right Looks Like

ALEX CHEN
Chicago, IL | [email protected] | (555) 123-4567 | linkedin.com/in/alexchen-it

PROFESSIONAL SUMMARY
CompTIA A+ certified IT professional with hands-on experience in Windows
troubleshooting, Active Directory, and network fundamentals. Built and
maintain a home lab running Windows Server, pfSense, and VMware. Previous
retail management experience brings strong customer service and
problem-solving skills to technical support roles.

TECHNICAL SKILLS
Operating Systems: Windows 10/11, Windows Server 2019, Ubuntu Linux
Networking: TCP/IP, DNS, DHCP, VPN configuration, Wireshark
Tools: Active Directory, Group Policy, VMware Workstation, PowerShell basics
Hardware: PC assembly, troubleshooting, component replacement, printers

PROJECTS
Home Lab Environment | Ongoing
• Deployed Windows Server 2019 domain controller with 5+ client machines
• Configured Group Policy objects for security settings and software deployment
• Implemented pfSense firewall with VLANs for network segmentation
• Documented all configurations in internal wiki for reference

Help Desk Simulation | 2025
• Completed Google IT Support Certificate hands-on labs
• Resolved 50+ simulated support tickets across hardware, software, and networking
• Practiced remote support using TeamViewer and Windows Remote Desktop

WORK EXPERIENCE
Assistant Store Manager | Best Buy | 2022-2025
• Managed team of 12, including scheduling, training, and performance reviews
• Resolved escalated customer complaints, maintaining 95% satisfaction rating
• Handled inventory management system troubleshooting for staff
• Trained employees on POS system updates and mobile device procedures

EDUCATION & CERTIFICATIONS
CompTIA A+ Certification (ce) | 2025
Google IT Support Professional Certificate | 2025
Associate of Applied Science, General Studies | City College | 2022

Why This Works

The summary leads with credentials, not aspirations. Instead of “seeking an entry-level position,” Alex immediately establishes certification and hands-on skills. The previous experience is reframed as an asset (customer service), not an apology.

Projects carry serious weight. The home lab section demonstrates real skills that align with help desk and junior sysadmin work. These aren’t theoretical—they’re practical environments with specific technologies.

Previous experience isn’t hidden—it’s translated. Managing a team, resolving escalations, and handling system troubleshooting are all relevant. Alex doesn’t pretend retail didn’t happen; instead, they extract the IT-adjacent value.

Technical skills are specific. Not just “Windows” but “Windows 10/11, Windows Server 2019.” Not just “networking” but “TCP/IP, DNS, DHCP, VPN configuration.” This helps with both ATS matching and human credibility.

Entry-Level Mistakes to Avoid

  • Listing every technology you’ve ever touched (focus on what’s relevant)
  • Including high school graduation (unless you’re under 22 with no other education)
  • Writing “proficient in Microsoft Office” (assumed, wastes space)
  • Using phrases like “seeking to leverage” or “passionate about technology”

Help Desk Resume Example

If you’ve been in IT for 1-3 years and want to either advance in support or transition to another specialization, your resume needs to show progression and impact.

Help Desk Resume That Gets Callbacks

MARIA SANTOS
Austin, TX | [email protected] | (555) 987-6543 | linkedin.com/in/mariasantos

PROFESSIONAL SUMMARY
IT Support Specialist with 3 years of experience supporting 500+ users across
Windows and Mac environments. Reduced average ticket resolution time by 35%
through process improvements and knowledge base development. Currently pursuing
Security+ certification to transition into security-focused roles.

TECHNICAL SKILLS
Support: ServiceNow, Zendesk, remote troubleshooting, on-site support, VIP support
Systems: Windows 10/11, macOS, Active Directory, Azure AD, Microsoft 365
Networking: TCP/IP, DNS/DHCP troubleshooting, VPN clients, basic firewall configuration
Security: MFA implementation, security awareness training, phishing identification
Scripting: PowerShell (basic), batch scripting for automation

PROFESSIONAL EXPERIENCE
IT Support Specialist II | Technica Solutions | Austin, TX | 2024-Present
• Provide Tier 2 support for 500+ users across 3 office locations
• Reduced average ticket resolution time from 4.2 hours to 2.7 hours (35% improvement)
• Created 25+ knowledge base articles, decreasing repeat ticket volume by 20%
• Mentored 2 junior support technicians during onboarding
• Manage VIP support queue for C-suite executives and department heads
• Led migration of 200 users to Microsoft 365 with zero productivity loss

Help Desk Technician | Regional Hospital Network | Austin, TX | 2022-2024
• Resolved 40+ tickets daily across hardware, software, and network issues
• Maintained 98% customer satisfaction rating across 1,500+ resolved tickets
• Supported HIPAA-compliant systems including Epic EHR
• Assisted with Windows 10 deployment project covering 400+ workstations
• Created automated imaging process using MDT, reducing deployment time by 50%

CERTIFICATIONS
CompTIA A+ (ce) | 2022
ITIL 4 Foundation | 2024
CompTIA Security+ | In Progress (Expected March 2026)

EDUCATION
Bachelor of Science, Information Technology | Texas State University | 2022

Why This Works

Numbers everywhere. 500+ users, 35% improvement, 25+ articles, 20% decrease, 40+ tickets daily. These quantified achievements make abstract work concrete and impressive.

Clear progression. The move from Help Desk Technician to IT Support Specialist II shows growth. The job titles and responsibilities demonstrate increasing scope.

Strategic positioning for the next role. The summary mentions Security+ and security interests. The skills section includes security-relevant experience. This person isn’t just documenting their help desk job—they’re building a bridge to cybersecurity.

Industry-specific value. HIPAA experience and Epic EHR support are valuable for anyone hiring in healthcare IT. This specificity creates competitive advantage.

Help Desk Resume Tips

  • Quantify everything possible: tickets per day, users supported, satisfaction ratings, time saved
  • Show process improvement: anyone can answer tickets, but creating knowledge bases or automating workflows shows initiative
  • Include VIP support if applicable: supporting executives demonstrates trust and communication skills
  • Highlight project work: deployments, migrations, and implementations separate you from pure ticket-takers

System Administrator Resume Example

At the sysadmin level, your resume needs to demonstrate independent ownership, architectural decisions, and technical depth. This is where you stop listing what you know and start proving what you’ve built.

Sysadmin Resume That Lands Interviews

JAMES WASHINGTON
Denver, CO | [email protected] | (555) 234-5678 | linkedin.com/in/jwashington-sysadmin

PROFESSIONAL SUMMARY
Windows Systems Administrator with 6 years of experience managing enterprise
infrastructure across hybrid environments. Architected migration of 150-server
environment to Azure, reducing infrastructure costs by 40%. Strong focus on
automation, security hardening, and documentation.

TECHNICAL SKILLS
Infrastructure: Windows Server 2016/2019/2022, Active Directory, Group Policy, DNS/DHCP
Cloud: Azure (VMs, AD, Backup, Site Recovery), AWS EC2 basics, Microsoft 365
Virtualization: Hyper-V, VMware vSphere, Azure Virtual Desktop
Automation: PowerShell, Azure Automation, scheduled tasks, SCCM task sequences
Monitoring: PRTG, Azure Monitor, Event Log analysis, performance tuning
Security: CIS benchmarks, security patching, vulnerability remediation, MFA

PROFESSIONAL EXPERIENCE
Senior Systems Administrator | FinanceFirst Inc. | Denver, CO | 2023-Present
• Manage 150+ Windows servers across on-premises datacenter and Azure
• Architected and executed hybrid cloud migration, moving 60% of workloads to Azure
• Reduced monthly infrastructure costs by $15,000 through rightsizing and reserved instances
• Implemented Azure Site Recovery for disaster recovery, achieving 15-minute RTO
• Developed PowerShell automation scripts reducing routine maintenance time by 8 hours weekly
• Hardened server configurations to CIS Level 1 benchmarks across entire environment
• Mentor team of 2 junior administrators on infrastructure and scripting best practices

Systems Administrator | Regional Manufacturing Co. | Denver, CO | 2020-2023
• Administered 80-server Windows environment supporting 400 users across 4 sites
• Upgraded domain from Windows Server 2012 R2 to 2019, including AD schema updates
• Implemented LAPS for local administrator password management
• Deployed WSUS and created automated patching process with 99% compliance rate
• Reduced backup recovery time by 60% through Veeam implementation and testing
• Created comprehensive documentation wiki covering all systems and procedures

IT Support Specialist | Same Company | Denver, CO | 2018-2020
• Promoted from help desk to systems role based on project contributions
• Led Windows 10 migration for 200 workstations using SCCM task sequences
• Provided Tier 2 escalation support for complex technical issues
• Maintained Active Directory user accounts, groups, and OUs

CERTIFICATIONS
Microsoft Azure Administrator (AZ-104) | 2024
Microsoft 365 Certified: Enterprise Administrator | 2023
CompTIA Security+ | 2021

PROJECTS
PowerShell Automation Library | github.com/jwash/sysadmin-scripts
• Developed 20+ scripts for common administrative tasks
• Includes automated reporting, user provisioning, and maintenance workflows

Why This Works

Architectural ownership is clear. This isn’t someone who follows runbooks—they architect migrations, make infrastructure decisions, and own outcomes. Phrases like “architected and executed” and “developed PowerShell automation” show senior-level contribution.

Cost impact is quantified. $15,000 monthly savings is concrete. 40% cost reduction is memorable. These numbers get repeated in conversations between recruiters and hiring managers.

Career progression is visible. Starting at IT Support Specialist and progressing to Senior Systems Administrator at the same company demonstrates growth and retention—both positive signals.

GitHub presence adds credibility. Linking to actual code samples shows the PowerShell skills are real, not theoretical.

What Senior Roles Require

At senior levels, hiring managers want evidence that you can:

  • Make independent technical decisions
  • Handle complex projects with multiple stakeholders
  • Mentor others and elevate team capability
  • Think about cost, security, and business impact—not just technical implementation
  • Document and create institutional knowledge

Your resume needs to prove all of these with specific examples.

Specialized Role Examples

Different IT specializations require different emphasis. Here’s what works for some common paths.

Cybersecurity Analyst Resume Focus

If you’re targeting security roles, emphasize:

  • Incident response experience: Even small-scale incidents count
  • Security tools: SIEM platforms, vulnerability scanners, EDR solutions
  • Compliance frameworks: SOC 2, HIPAA, PCI-DSS, NIST
  • Certifications that matter: Security+, CySA+, CEH, eventually CISSP
SECURITY-FOCUSED SKILLS SECTION EXAMPLE
--------------------------------------
SIEM: Splunk, Microsoft Sentinel, log analysis
Endpoint: CrowdStrike, Carbon Black, Windows Defender ATP
Vulnerability Management: Nessus, Qualys, remediation tracking
Frameworks: NIST CSF, CIS Controls, SOC 2 compliance
Incident Response: Phishing investigation, malware analysis, containment procedures

Cloud Engineer Resume Focus

Cloud engineers need to show infrastructure-as-code experience and architectural understanding:

CLOUD-FOCUSED SKILLS SECTION EXAMPLE
------------------------------------
AWS: EC2, S3, VPC, IAM, Lambda, CloudFormation, RDS
Azure: VMs, Blob Storage, AKS, Azure AD, ARM templates
IaC: Terraform, Ansible, CloudFormation, ARM
Containers: Docker, Kubernetes, ECS, AKS
CI/CD: GitHub Actions, Azure DevOps, Jenkins basics
Monitoring: CloudWatch, Azure Monitor, Prometheus, Grafana

Your experience bullets should emphasize cost optimization, automation, and migration projects.

DevOps Engineer Resume Focus

DevOps roles bridge development and operations. Emphasize:

  • CI/CD pipeline ownership
  • Infrastructure automation
  • Monitoring and observability
  • Container orchestration
  • Collaboration with development teams
DEVOPS-FOCUSED EXPERIENCE BULLET EXAMPLES
-----------------------------------------
• Designed and maintained CI/CD pipelines processing 50+ deployments daily
• Reduced deployment time from 2 hours to 15 minutes through automation
• Implemented GitOps workflow using ArgoCD and Kubernetes
• Built infrastructure-as-code modules reducing environment provisioning from days to hours

Resume Templates and Formatting

Your content matters more than your design, but formatting can still sink an otherwise strong resume.

ATS-Friendly Formatting Rules

Use standard section headers. “Professional Experience” works better than “Where I’ve Made Impact.” ATS systems look for conventional headers.

Avoid tables and columns. Many ATS systems read left-to-right across the entire page, mixing up column content. Use simple stacked sections instead.

Stick to standard fonts. Arial, Calibri, Georgia, or Times New Roman. Fancy fonts may not render correctly.

Use .docx format when possible. Despite common advice, many ATS systems handle Word documents better than PDFs. When PDF is required, ensure it’s text-based (you should be able to select and copy text).

Include the exact job title and keywords. If the posting says “Systems Administrator,” don’t just write “Sysadmin” everywhere. Mirror their language.

Length Guidelines

Experience LevelRecommended Length
Entry-level (0-2 years)1 page max
Mid-level (3-7 years)1-2 pages
Senior (8+ years)2 pages max
Executive/specialized2-3 pages acceptable

One strong page beats two mediocre pages. Cut ruthlessly. If your bullet point doesn’t demonstrate relevant value, remove it.

What Your Header Should Include

GOOD HEADER EXAMPLE
-------------------
SARAH JOHNSON
Seattle, WA | [email protected] | (206) 555-1234 | linkedin.com/in/sarahjohnson-it
GitHub: github.com/sjohnson (if relevant)

BAD HEADER EXAMPLES
-------------------
❌ 123 Main Street, Apt 4B, Seattle, WA 98101 (too much detail)
❌ [email protected] (unprofessional domain, birth year exposed)
❌ linkedin.com/in/sjohnson-83729481-tech-professional (ugly URL, didn't customize)

The Professional Summary That Works

Your summary is prime real estate—the first thing human readers see after your name. Most summaries waste this space on generic fluff.

What Doesn’t Work

“Motivated IT professional with excellent communication skills seeking challenging opportunities to grow and develop in a dynamic environment.”

This says nothing. It could apply to anyone. It doesn’t differentiate you or connect to the job.

What Works

“Windows Systems Administrator with 5 years managing enterprise infrastructure and a track record of reducing downtime through automation. Migrated 200-server environment to Azure, cutting infrastructure costs by 30%. Looking to bring infrastructure and security expertise to a senior role at a security-focused organization.”

This summary:

  • States specific experience level and focus area
  • Includes a quantified achievement
  • Names specific technology (Azure)
  • Shows what’s wanted and why you’re qualified

Summary Formula

Try this structure:

[Title] with [X years] experience in [specialization]. [Biggest achievement with numbers]. [Relevant skill or current focus]. [What you bring to this role].

Keep it to 3-4 sentences maximum. This isn’t a cover letter—it’s a hook.

Customizing for Every Application

The biggest resume mistake is sending the same document to every job. The second biggest is making tiny changes that don’t matter.

Here’s the efficient approach:

Create a Master Resume

Build one comprehensive document with everything—all skills, all projects, all experience bullets. This is your source material. It might be 3-4 pages. You’ll never send this anywhere.

Build Role-Specific Versions

Create 2-3 versions optimized for different job types:

  • Help Desk / IT Support version
  • Sysadmin / Infrastructure version
  • Security / Compliance version (if relevant)

These are your base templates.

Customize for Specific Applications

When applying to a specific job:

  1. Read the job description carefully. Highlight required skills, technologies, and responsibilities.
  2. Mirror their language. If they say “systems administration,” don’t just write “sysadmin.”
  3. Reorder your skills section. Put their requirements first.
  4. Adjust your summary. Reference their specific needs.
  5. Emphasize relevant experience. Your most relevant bullets should come first.

This takes 10-15 minutes per application. It’s the difference between 5% callback rate and 25%+ callback rate.

What Hiring Managers Actually Look For

After reviewing thousands of resumes (and talking to people who review even more), certain patterns emerge.

The First 10-Second Scan

Hiring managers look for:

  1. Relevant job titles - Has this person done something similar?
  2. Company recognition - Do I recognize any employers?
  3. Tenure - Job hopping red flags (less than a year at multiple jobs)
  4. Key skills match - Do the right technologies appear?
  5. Education/certs - Minimum requirements met?

The Deeper Review

If you pass the initial scan:

  1. Achievement vs. responsibility - Did they do things, or just have jobs?
  2. Progression - Have they grown over time?
  3. Technical depth - Can they actually do what they claim?
  4. Communication quality - Is the resume well-written?
  5. Culture signals - Does this person seem like a fit?

Red Flags That Trigger Rejection

Based on conversations with IT hiring managers, these trigger immediate skepticism:

  • Unexplained gaps (address them briefly if longer than 6 months)
  • Buzzword stuffing (claiming expert-level skills in 40 technologies)
  • No achievements (all responsibilities, no outcomes)
  • Typos and formatting errors (if you’re careless here, where else?)
  • Objective statements (outdated format signals you haven’t updated your approach)
  • Generic applications (when it’s obvious you didn’t read the job description)

Building Skills That Resume Well

Some skills are easier to demonstrate on paper than others. If you’re building toward your next role, focus on skills that show clearly.

High-Resume-Value Skills

  • Certifications: Objective proof of knowledge. Focus on certs that match your target roles.
  • Automation projects: Scripts you’ve written, processes you’ve automated—these show initiative and save companies money.
  • Migrations and deployments: Large-scale projects demonstrate ability to handle complexity.
  • Documentation: Creating knowledge bases shows communication skills and institutional thinking.
  • Metrics: Track numbers before you need them—tickets resolved, time saved, users supported.

Hard-to-Show Skills

  • Troubleshooting ability: Can be demonstrated through examples, but harder to quantify
  • Customer service: Satisfaction ratings help, but this often comes across better in interviews
  • Teamwork: References can speak to this; resumes struggle to prove it

For hands-on skill building, especially Linux and command line expertise, platforms like Shell Samurai let you practice real scenarios. TryHackMe and HackTheBox work well for security skills you can list on your resume.

Handling Resume Challenges

Career Gaps

If you have employment gaps:

  • Gaps under 6 months usually don’t need explanation
  • Longer gaps: briefly explain in cover letter, not resume
  • Frame positively: “Family care responsibilities” or “Career development period” work better than silence
  • Show what you did: certifications earned, home lab projects, freelance work

Career Changes

Coming from another field (see our guide on switching to IT):

  • Lead with transferable skills and IT credentials (certs, projects)
  • Previous experience goes toward the end
  • Extract IT-relevant work from non-IT roles (any system administration, troubleshooting, training)
  • Use your summary to bridge the gap: “Former [old role] with [transferable skill] transitioning to IT with [certification] and [project experience].”

Job Hopping

Multiple jobs under 1-2 years each:

  • Contract roles can be grouped: “Contract IT Specialist | Various Clients | 2023-2024”
  • If layoffs were common in your industry, this is understood—no need to apologize
  • Focus on achievements at each role, not why you left
  • One long tenure can offset several short ones

Overqualification

If you’re applying to roles below your level:

  • Adjust your title presentation (Senior Systems Administrator applying for sysadmin role might use Systems Administrator in summary)
  • Focus summary on why this role interests you
  • Don’t hide experience—but don’t lead with intimidating titles
  • Address in cover letter: genuine interest, career refocus, or lifestyle changes

Final Checklist Before Sending

Run through this before every application:

Content Checks

  • Summary is customized for this specific job
  • Skills section mirrors job requirements
  • Achievement bullets include numbers where possible
  • Most relevant experience bullets appear first
  • No typos or grammatical errors (read aloud to catch mistakes)

Format Checks

  • Clean, consistent formatting throughout
  • Standard fonts (Arial, Calibri, Georgia)
  • No tables or columns
  • Appropriate length for experience level
  • Contact information is current and professional

Targeting Checks

  • Job title matches or closely aligns with posting
  • Key technologies from job description appear in skills
  • Summary addresses what this employer needs
  • Nothing irrelevant that could distract from your fit

Making Your Resume Work For You

Your resume isn’t a historical document—it’s a sales tool. Its only job is to get you interviews.

That means:

  • Every bullet should serve a purpose
  • Every word should earn its space
  • Every version should target a specific type of role

The examples and templates in this article give you frameworks. But the real work is taking your experience and positioning it to solve specific hiring problems.

Start with one strong version. Get feedback from people in roles you want (not just friends who’ll say “looks good”). Test and iterate based on callback rates. Track what works.

And remember: even the best resume only gets you the interview. From there, you need to avoid common interview mistakes and prepare effectively to close the deal.

Your experience matters. Your skills are real. The resume’s job is to prove it—in 7.4 seconds.

Frequently Asked Questions

Should I include a photo on my IT resume?

No. In the United States and UK, including a photo opens you up to unconscious bias and is considered unprofessional for technical roles. The only exception is if you’re applying in countries where photos are culturally expected (some parts of Europe and Asia). Even then, use a professional headshot—never a casual photo.

How do I list certifications in progress?

Include them with “In Progress” or your expected completion date: “CompTIA Security+ | In Progress (Expected April 2026).” This shows initiative and gives hiring managers context on your learning trajectory. Just be honest—don’t claim expected dates you can’t meet.

Should I include my home lab on a professional resume?

Yes, especially if you’re early in your career or transitioning into IT. A well-documented home lab demonstrates initiative, hands-on skills, and genuine interest. Present it professionally: “Home Lab Environment | Ongoing” followed by specific technologies deployed and skills demonstrated.

How far back should my work history go?

Generally, 10-15 years maximum. Anything older than that is unlikely to be relevant and dates you unnecessarily. If you have early-career experience that’s directly relevant to your target role, you can include it—but most hiring managers focus on recent experience. Entry-level candidates should include all relevant work history.

Is a one-page resume really required for entry-level?

Strongly recommended, yes. With limited professional experience, a one-page resume forces you to be concise and focus on what matters. If you’re padding to reach two pages, you’re probably including irrelevant information. One focused page beats two pages of filler every time.