How to Apply for the VA Office of Information and Technology IT Specialist Job (GS-14)

Landing a GS-14 IT Specialist Role at the VA: What You Actually Need to Know

A few years back, a buddy of mine — sharp guy, 15 years in enterprise infrastructure — applied for a federal IT job and got disqualified before anyone even read his resume. Not because he lacked skills. Because his resume was three pages long.

That one small formatting mistake cost him the shot. The VA’s OIT (Office of Information and Technology) has a hard two-page resume limit, and they mean it. No exceptions.

I’ve been helping people navigate federal job applications for a while now, and the VA’s current opening for an IT Specialist (GS-14) under the Office of Information and Technology is one of the more interesting ones I’ve seen recently. The pay range alone — $125,776 to $163,514 per year — makes it worth a serious look. But getting there requires understanding how federal hiring actually works, not just how you wish it worked.

Let me walk you through what this job is, who it’s really for, and how to give yourself a fighting chance at getting selected.

What This Job Actually Is (Not the HR-Speak Version)

The title says “IT Specialist,” but don’t let that fool you into thinking it’s a help desk gig. This is an expert-level infrastructure engineering role inside one of the largest IT organizations in the federal government.

The VA supports over 400,000 employees, runs hundreds of facilities across the country, and manages IT infrastructure that handles everything from veteran healthcare records to benefits processing. When something breaks — or when they’re trying to modernize a 30-year-old system — these are the people in the room making the technical calls.

Your job, if selected, would include things like:

• Designing and architecting large-scale IT infrastructure (compute, storage, networking, hybrid cloud, data centers)
• Leading cross-functional engineering projects from concept through deployment
• Translating complex technical decisions into plain English for senior leadership
• Applying capital investment analysis — cost-benefit, total cost of ownership, return on investment — to infrastructure proposals

That last one trips people up. A lot of strong infrastructure engineers have never had to defend a $10 million storage refresh in business terms to a deputy secretary. If you haven’t done that kind of analysis before, start thinking about how to frame your experience in that language.

The Salary Is Adjustable (and That Matters)

The posted range ($125,776 – $163,514) reflects the Rest of U.S. salary table. If you end up placed in Los Angeles, San Francisco, or Washington DC, your actual salary gets adjusted upward to reflect the locality pay for that area.

That means if you’re assigned to the LA or Bay Area locations, you could be looking at compensation that’s meaningfully higher than what’s advertised. Worth factoring into your decision.

Speaking of locations — there are 27 possible duty stations listed, from Anaheim to Salt Lake City to Pittsburgh. You negotiate the location after selection, not before. Don’t count on getting your first choice, but having a few options you’d genuinely accept is smart.

The Selective Placement Factor: Where Most People Get Knocked Out Early

Here’s the thing about this posting that people overlook: there’s a Selective Placement Factor (SPF) that’s a hard gate before they even look at your specialized experience.

You must have:

Experience with enterprise infrastructure engineering — platforms, storage, hybrid cloud, cloud and/or data center and telecommunications infrastructure engineering — at a large enterprise or government agency with over 200,000 employees, over 100 facilities, and over 20,000 servers.

If you’ve worked at a mid-size company or a smaller agency, even if you were the most senior engineer there, this SPF may disqualify you. The scale requirement is specific and intentional. The VA’s infrastructure is enormous, and they want someone who has operated at that scale before.

If you do meet this threshold, make sure your resume says so explicitly. Don’t make a reviewer infer it. State the size of the organization, the number of facilities, and the scale of the environment. Spell it out.

How to Write a Two-Page Federal Resume That Actually Works

This is the part nobody tells you clearly enough.

A federal resume is not a traditional resume. It needs far more detail than what you’d send to a private employer — job duties, hours per week, start and end dates (month and year, not just year). But here, you’re also constrained to two pages.

That tension — more detail, less space — requires discipline.

What to cut:

• Objective statements
• References section
• “Skills” lists that just name software (put those in context within your job descriptions)
• Fluff like “results-driven professional.”

What to keep and expand:

• Specific accomplishments tied to scale (number of servers, petabytes of storage, facilities supported)
• Evidence of capital planning, cost analysis, or business case work
• Examples of leading cross-functional teams through full project lifecycles
• Any mention of healthcare IT or federal compliance environments (a big plus here)

Every bullet should answer: What did I do, at what scale, and what was the result?

If you’ve managed a hybrid cloud migration for a 50,000-person organization, say that. If you’ve presented a $5M infrastructure investment recommendation to C-suite executives, say that too.

The USA Hire Assessments: Don’t Sleep on These

After you submit your application, you’ll get a link to complete USA Hire Assessments — competency-based tests that measure things like problem-solving, customer service, attention to detail, and oral communication (in written scenario form).

These assessments have a cut score. If you don’t hit it, you’re out regardless of your resume.

A few things I’ve seen people mess up:

1. Rushing through them. The system says to set aside three hours. Most people finish in less. But “finishing fast” and “finishing well” aren’t the same thing. Read every scenario carefully. Federal assessment questions often test whether you’d escalate appropriately, collaborate before acting unilaterally, or follow process even when you know a shortcut.

2. Picking the “most competent” answer instead of the “most appropriate” answer. There’s a difference. A question about how you’d handle a data center outage isn’t asking if you can fix it — it’s asking if you communicate with stakeholders, document the incident, and follow the right chain of command.

3. Not completing them in time. The deadline is tight after the announcement closes. Check your email obsessively after submitting your application.

Travel, Telework, and the Physical Reality of This Job

Let’s be real about the working conditions: this is not a remote job. There’s occasional telework at management discretion, but if you’re expecting to work from home full-time, this isn’t it.

There’s up to 25% travel in the job description (another section says up to 10% — they’ll clarify at the offer stage), which means you’ll be flying out to VA facilities, OIT offices, and potentially Washington, DC, for meetings. If you have family commitments or health reasons that make travel difficult, factor that in.

The work schedule is Monday through Friday, 8 am–4:30 pm, with the realistic expectation of longer hours during project crunches. That’s standard for senior federal IT roles.

Veterans: You Have Standing Here

The VA specifically encourages veterans to apply. While this position uses Direct Hire Authority (which means traditional veterans’ preference points don’t apply the same way), the job posting explicitly states that qualified veterans receive full consideration.

If you’re a veteran with a service-connected disability of 30% or more, there’s a Schedule A hiring pathway worth exploring. Contact the agency’s Selective Placement Coordinator about that route.

Common Mistakes That Get Applications Tossed

After watching a lot of people go through this process, the patterns are pretty clear:

• Resume over two pages — automatic disqualification
• No month/year dates or hours per week — they can’t verify time-in-grade or credit your experience
• Vague language — “managed infrastructure” tells them nothing; “led a team of 8 engineers supporting 12,000+ endpoint devices across 35 locations” tells them something
• Not addressing the SPF directly — if the scale of your experience isn’t explicit, reviewers won’t assume it
• Missing supporting docs — if you’re a current or former federal employee, your SF-50 is required

Is This the Right Move for You?

If you’ve spent years building infrastructure at scale — managing massive storage environments, leading data center migrations, dealing with hybrid cloud headaches, and explaining technical decisions to executives who just want to know what it costs and when it’ll be done — this role was built for people like you.

The pay is competitive for federal work. The mission is meaningful (supporting veterans’ healthcare and benefits systems isn’t abstract). And a GS-14 in OIT puts you in a position to actually shape how the VA modernizes its infrastructure over the next decade.

The application closes on June 3, 2026. That’s tight. If you’re qualified and serious, start on your resume today — not tomorrow.

Two pages. Month and year dates. Hours per week. Scale, scale, scale.

Get that right, and you’ve got a real shot.

If you’re ready to turn your skills into income, check out our full guide on FIFA World Cup 2026 Event Staff Recruitment.