# Veteran technician ramp-up time: O*NET crosswalk vs 90-day benchmark in 2026

Daniel Okonkwo · November 8, 2026

> The O*NET crosswalk maps a veteran's MOC to an occupation, not a ramp time. Use day-30/60/90 working-day evidence gates; flat 90 days only as fallback.

In 2026 the O*NET military crosswalk tells you which O*NET-SOC occupation a veteran technician's MOC maps to — it does not tell you how long that occupation takes to ramp.

The defensible benchmark is an occupation-specific day-30/60/90 evidence gate counted in working days, with the flat 90-calendar-day figure reserved only for hires where no occupation-specific checkpoints exist.

![In 2026 the O*NET military crosswalk tells you — Veteran technician ramp-up time](https://static.mm-ais.com/article-images-ai/veteran-technician-ramp-up-time-o-net-cr-ai-2fd79b13.jpg)

## How an MOC becomes an O*NET-SOC code

Start with O*NET's Military Crosswalk Search and enter the MOC by code or by title — either field works as an entry point. What comes back is a list of O*NET-SOC occupations, each with a numeric code and an occupation title. That list is the entire output. The crosswalk returns a set of O*NET-SOC occupation codes and titles with no duration, proficiency, or credential field attached — no time-to-competence estimate, no skills score, no certificate requirement. Treat the result as an address, not an assessment.

Read the list against the work the technician actually performed, not against the rank or the training pipeline. When the search returns more than one occupation, the tiebreaker is the task inventory: the equipment they maintained, the diagnostics they ran, the records they signed. Write that reasoning beside the selected code, because the next reviewer will otherwise re-run the same query and land somewhere else. A returned occupation is a classification, and a classification by itself says nothing about how long a person needs to reach independent work in it.

For volume — a requisition batch, an HRIS load, a separation roster — move to the Crosswalk Files published at the O*NET Resource Center and join on the O*NET-SOC code. Join on the code, never on the job title. Military occupational titles and O*NET occupation titles diverge often enough that title-only matching silently drops veterans out of the result set, and a dropped record looks exactly like a veteran with no transferable occupation. Keep titles as display columns only.

Build the join to survive fan-out. Two different MOCs can land on the same O*NET-SOC occupation, and a single MOC frequently maps to several O*NET-SOC occupations. Model the relationship as many-to-many, deduplicate at the requisition level rather than inside the mapping table, and spot-check the batch in both directions — one MOC outward, one occupation inward — before you trust it.

Once the code is fixed, it becomes the anchor for the ramp gate. Because the crosswalk supplies no duration field, the day-30, day-60, and day-90 working-day checkpoints have to be written from that occupation's own countable deliverables, and reviewed by whoever supervises the work. Log the query in the requisition file — code or title searched, date, codes returned — so the mapping can be reproduced and defended later.

![How an MOC becomes an O*NET-SOC code — Veteran technician ramp-up time](https://static.mm-ais.com/article-images-ai/veteran-technician-ramp-up-time-o-net-cr-ai-8e316207.jpg)

## Three independent onboarding cost figures

Before you commit any dollar figure to a hiring plan, count how many different onboarding cost numbers are in circulation — because there are at least three, and they do not agree. Stealth Agents, in a May 23, 2026 analysis, reports an average onboarding spend of $4,100 per new hire. SHRM's widely cited figure, as reported in the same coverage, is $5,475. That is a $1,375 gap between two sources answering the same question about the same concept. Treat neither as a cap; treat both as evidence that a single flat number is the wrong instrument for budgeting a veteran technician's first quarter.

The third figure changes units entirely. Onboardingcost.com reframes the spend as a percentage of salary: 15 to 30 percent of annual pay for an hourly retail hire, and 45 to 90 percent for a knowledge worker, once manager time and the productivity ramp are counted. That reframing matters for veteran technicians, whose salary band varies widely by trade and region. A percentage-of-salary band lets you scale the estimate to the actual offer; a flat per-hire fee cannot.

The convergence across these three sources is the site's cost evidence, and it points one direction: administrative per-hire spend clusters in the low thousands, but the true cost of onboarding a technician is dominated by manager time and the productivity ramp — exactly the ramp period the day-30/60/90 gate is built to measure. Two flat fees and one salary band, three sources, one conclusion.

| Source | Figure | Unit | Use it for |
| --- | --- | --- | --- |
| Stealth Agents (May 23, 2026) | $4,100 | Average spend per hire | Administrative cost floor |
| SHRM, as reported | $5,475 | Cost per hire | Upper administrative check |
| Onboardingcost.com | 15–30% (hourly retail) / 45–90% (knowledge worker) | Percent of salary | Scaling to the actual technician offer |

Practical check for your budget: run the estimate twice. First as a per-hire figure anchored between the $4,100 and $5,475 administrative numbers, then as a salary band using the appropriate percentage range for the hire type. If the two estimates diverge sharply, the difference is your manager time and productivity ramp — the portion the crosswalk's occupation code cannot price and the flat 90-day figure cannot schedule.

Keep the units honest when you report the number upward. Administrative spend is a one-time per-hire cost; ramp cost accrues across the working days of the gate. Mixing the two into a single 90-day budget line is how onboarding programs look cheap on paper and expensive in the field.

## Crosswalk-only, 90-day gate, or role clock

Three ways to turn a crosswalk result into a hiring decision are in circulation, and they are not interchangeable. The table below is the comparison this site uses, and it names the winner up front: the role clock.

## Frequently Asked Questions

**Does the O*NET Military Crosswalk give me a time-to-competence estimate for a veteran's MOC?**

No — the crosswalk returns only O*NET-SOC occupation codes and titles, with no duration, proficiency, or credential field attached.

**Can I search the crosswalk by job title instead of the MOC code?**

Yes — O*NET's Military Crosswalk Search accepts the MOC by code or by title, and either field works as an entry point.

**What should I do when the crosswalk returns more than one matching occupation?**

Use the task inventory as the tiebreaker — the equipment the technician maintained, the diagnostics they ran, and the records they signed.

**Why do I need to write my reasoning next to the selected O*NET-SOC code?**

Because the next reviewer will otherwise re-run the same query and land somewhere else.

**When is a flat 90-calendar-day ramp figure defensible?**

Only for hires where no occupation-specific checkpoints exist; otherwise use an occupation-specific day-30/60/90 evidence gate counted in working days.

**Should I match the returned occupation against the veteran's rank or training pipeline?**

No — read the list against the work the technician actually performed, and treat the returned occupation as an address, not an assessment.

## Quick answers

| What does the O*NET military crosswalk tell you about a veteran technician's MOC? | It tells you which O*NET-SOC occupation the MOC maps to, but not how long that occupation takes to ramp. |
| --- | --- |
| What is the defensible benchmark for ramp-up time in 2026? | An occupation-specific day-30/60/90 evidence gate counted in working days, with the flat 90-calendar-day figure reserved only for hires where no occupation-specific checkpoints exist. |
| How do you start converting an MOC into an O*NET-SOC code? | Start with O*NET's Military Crosswalk Search and enter the MOC by code or by title, since either field works as an entry point. |
| What fields does the crosswalk return with each occupation? | It returns occupation codes and titles with no duration, proficiency, or credential field attached—no time-to-competence estimate, no skills score, no certificate requirement. |
| What is the tiebreaker when the search returns more than one occupation? | The task inventory—the equipment they maintained, the diagnostics they ran, the records they signed—and the reasoning should be written beside the selected code. |

Also worth reading: **Caregiving and veteran job search: verify time-to-first-job data first**: [Caregiving and veteran job search:](https://vetwork.app/blog/caregiving-and-veteran-job-search-verify-time-to-first-job-data-first.php) · **Skills-based hiring for veteran entry roles: a verify-before-you-commit guide**: [Skills-based hiring for veteran entry](https://vetwork.app/blog/skills-based-hiring-for-veteran-entry-roles-a-verify-before-you-commit-guide.php) · **What a connected veteran workforce strategy looks like in practice**: [What a connected veteran workforce](https://vetwork.app/blog/what-a-connected-veteran-workforce-strategy-looks-like-in-practice.php)

### Related reading

- [Caregiving and veteran job search: verify time-to-first-job data first](https://vetwork.app/blog/caregiving-and-veteran-job-search-verify-time-to-first-job-data-first.php)
- [Veteran Cyber Jobs Without Degree: Skills Hiring Cuts Time-to-Fill 30% vs 90-Day Retention](https://vetwork.app/blog/veteran-cyber-jobs-without-degree-skills-hiring-cuts-time-to-fill-30-vs-90-day-retention.php)
- [Veteran retention in 2026: SkillBridge vs direct hire for 500–5,000 staff](https://vetwork.app/blog/veteran-retention-in-2026-skillbridge-vs-direct-hire-for-5005000-staff.php)
- [2026 Federal Veteran Hiring Preference: 5 vs 10 Points, 30% Disability Rank](https://vetwork.app/blog/2026-federal-veteran-hiring-preference-5-vs-10-points-30-disability-rank.php)
- [PCS Veteran Onboarding: 30/60/90-Day Artifact Checkpoints, Not an 82% Claim](https://vetwork.app/blog/pcs-veteran-onboarding-306090-day-artifact-checkpoints-not-an-82-claim.php)
- [Veteran Reemployment Rights: USERRA 15-Week Window—Act to Restore](https://vetwork.app/blog/veteran-reemployment-rights-userra-15-week-windowact-to-restore.php)

### Latest

- [Veteran retention in 2026: SkillBridge vs direct hire for 500–5,000 staff](https://vetwork.app/blog/veteran-retention-in-2026-skillbridge-vs-direct-hire-for-5005000-staff.php)
- [Moving after a PCS: DoD SkillBridge 180-Day Window vs Starting Over](https://vetwork.app/blog/moving-after-a-pcs-dod-skillbridge-180-day-window-vs-starting-over.php)
- [Caregiving and veteran job search: verify time-to-first-job data first](https://vetwork.app/blog/caregiving-and-veteran-job-search-verify-time-to-first-job-data-first.php)

Canonical: https://vetwork.app/blog/veteran-technician-ramp-up-time-onet-crosswalk-vs-90-day-benchmark-in-2026.php
Markdown: https://vetwork.app/blog/veteran-technician-ramp-up-time-onet-crosswalk-vs-90-day-benchmark-in-2026.php/index.md