For Employers

Hiring for TMS Fluency Without Getting Burned

"Five years of CargoWise" can mean five very different things. Here is how to find out which one you are hiring.

August 14, 2026 · 5 min read · By the TRYSTUM team

System experience has become the first filter in logistics hiring, which means it has also become the thing candidates are most likely to overstate — usually not dishonestly, but because "I know CargoWise" feels true to someone who has used three of its modules competently for years.

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

Define the level you actually need first

• User. Runs daily transactions competently — bookings, rating, documentation. This is what most operations roles genuinely require.
• Power user. Builds and interprets reports, understands the data structure, is the person colleagues ask. Command a premium.
• Configuration. Sets up workflows, coding, templates, integrations. 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 and raises your range for capability you will never use.

Questions that actually separate levels

Replace "do you know CargoWise?" with:

• Which modules were you in daily, and which have you never opened?
• Walk me through booking a consol from creation to documentation in the system.
• What reports did you run, and did you build any of them yourself?
• What is the most annoying thing about the platform? (Real users always have an answer, and it is specific.)
• What did your company configure differently from the standard setup?
• Have you been through an implementation or migration?

The "what is annoying about it" question is the most reliable single tell. Someone who has genuinely lived in a platform has strong, specific opinions about it. Someone who has been shown it a few times gives a generic answer.

A short practical beats an hour of questions

Ten minutes of screen-share is worth more than any amount of self-description. Ask them 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.

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. 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 slows everything down while it is missing.

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. There, take the lanes and budget for system training.

Budget for the ramp either way

Even an experienced user needs to learn your configuration — your coding, branch structure, naming conventions and reports. Plan a week of that explicitly rather than assuming platform familiarity covers it. Hires who are assumed to already know it are the ones who quietly develop bad habits in month one.