Hiring for TMS Fluency Without Getting Burned

System experience has become the first filter in logistics hiring. That is rational: a candidate who has lived in your platform is productive in days, and one who has not costs three to six months of supervision. It has also made system experience the thing candidates are most likely to overstate — usually not dishonestly, but because "I know CargoWise" feels completely true to someone who has used three of its modules competently for six years.

The fix is to stop asking whether they know it and start asking what they did in it.

Why the stakes went up

The platforms are consolidating and getting deeper. WiseTech's CargoWise revenue reached $756.9 million in the year to June 2026, up 11%, inside a group that grew 79% after absorbing e2open. Descartes' ninth annual Transportation Management Benchmark Survey, fielded across 616 shippers and logistics providers in July 2025, found 80% planning to increase TMS spending and 96% already using generative AI somewhere in transportation management — data entry, load optimization, forecasting. Only 17% described their processes as fully automated, but among companies with industry-leading financial performance that figure was 51%, against 5% for below-average performers.

Read that as an employer and the implication is plain: the gap between a user and a power user is now a gap in your P&L. The person who can build the report, configure the workflow and clean the data feeding the AI is worth materially more than the person who books shipments in a screen someone else built. Most job descriptions still price them the same.

Define the level you actually need first

• User. Runs daily transactions competently — bookings, rating, documentation, milestone updates. This is what most operations desks genuinely require.
• Power user. Builds and interprets reports, understands the data structure, knows which fields drive which downstream behaviour, is the person colleagues ask. Commands a premium and earns it.
• Configuration. Sets up workflows, coding, templates, EDI and integrations; has been through an implementation or migration. Rare, and priced accordingly.

Writing "configuration experience" into a job description you only need a user for is one of the more expensive habits in freight hiring. It shrinks your pool dramatically, lengthens the search, and raises your range for capability you will never use. The reverse mistake is cheaper but slower: hiring a user into a seat that needs a power user, then discovering it in month three when nobody can explain why the margin report is wrong.

Six questions that actually separate levels

Replace "do you know CargoWise?" with:

1. Which modules were you in daily, and which have you never opened? The second half of the question is the one that matters.
2. Walk me through booking a consol from creation to documentation. Listen for the order of operations and the fields they check without being prompted.
3. What reports did you run, and did you build any of them yourself? Running is user level. Building is power-user level.
4. What is the most annoying thing about the platform? Real users always have an answer, and it is specific.
5. What did your company configure differently from the standard setup? People who know the system know where their shop deviated from it.
6. Have you been through an implementation or migration? If yes, what broke, and what did you do about it?

Question four is the most reliable single tell we have found. Someone who has genuinely lived in a platform has strong, specific opinions about it — the screen that takes four clicks when it should take one, the field that resets, the report that times out. Someone who has been shown it a few times gives you a generic answer about the interface.

A ten-minute practical beats an hour of questions

Ten minutes of screen-share is worth more than any amount of self-description. Ask the candidate to walk through a familiar workflow while narrating — where they would go, what they would check, what they would do if a field errored. You are not testing memory of your configuration. You are watching whether the navigation is automatic.

Keep it short and make it relevant to the actual desk. Long unpaid exercises lose good candidates, and the strong ones have other conversations running. Ten minutes on a live screen, or a two-page scenario with three questions, is enough.

Reward honesty about limits

The best answer you can get is: "Six years in operations and documentation, never touched accounting." That candidate knows their own scope — which is exactly the trait you want in someone handling your files and your customers' money. Do not penalise it. The alternative is someone who claims everything and gets found out in month two.

Make it easy to say by asking directly: "What parts of the system have you not worked in?" Asked plainly, most people answer honestly.

Systems versus lanes: which to trade

You will regularly choose between a candidate with your exact system and adjacent lanes, and one with your exact lanes and no system experience.

For most operations roles, the system candidate ramps faster. Lane knowledge is learnable on the job with a competent team around them. System fluency has to be built through repetition, and while it is missing it slows every file on the desk.

The exception is where lane expertise is the job — a trade lane manager, a specialist desk where carrier relationships and customs nuance carry the role, a pricing seat built on Transpacific routing guides. There, take the lanes and budget for system training.

Platform-specific notes

• CargoWise One. The widest capability range of any platform in freight. Always ask about modules and about whether they worked in a heavily customised instance — a power user in one shop can be a user in another.
• Descartes and Magaya. Common in mid-size forwarders and customs brokers. Ask specifically about customs filing and compliance modules if that is part of the seat.
• SAP TM and Oracle OTM. Shipper-side and large 3PL. Experience here often means working inside a wider ERP landscape; ask what sat upstream and downstream of the TMS.
• Migrations. Anyone who has been through a platform migration — in either direction — has seen the data model from both sides. That experience transfers across platforms far better than module-level familiarity does.

Budget for the ramp either way

Even an experienced user needs to learn your configuration, your coding, your branch structure and your customers. Two to four weeks for a strong system match; longer for anyone else. Build it into the plan, put a 30-day and a 90-day check in the calendar before they start, and ask on day 30 whether the job is what they were told it would be. That question saves hires.

Sources

• WiseTech Global FY2026 results (year to 30 June 2026), reported by Air Cargo Week, 26 August 2026 — CargoWise revenue $756.9M, +11%; group revenue $1.396B, +79%.
• Descartes, 9th Annual Global Transportation Management Benchmark Survey, fielded July 2025 (616 respondents), reported by DC Velocity, 18 September 2025 — 80% increasing TMS spend; 96% using generative AI; 17% fully automated; 51% of financial leaders fully automated vs 5% of laggards.