Which tools actually impress hiring managers

When I review mining resumes and prep people for interviews, the candidates who name the exact tools stand out — saying Deswik for stope design or seat time on a CAT 793F beats generic “planning” or “haul trucks.” For those on site now, what carries more weight where you work: software fluency (Deswik/Vulcan/Hexagon) or hands-on with rigs like a Sandvik DD422i — and what’s the specific proof you want to hear in the interview?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍⁠‌‌‍‍‍​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‍​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​‌‌‍‌⁠‌⁠​‌​⁠​⁠‌⁠‌​​⁠​⁠‌‍‍‍‌‌​​​⁠‌‌‌​​‍‌‍‍⁠‌‌‌‍‌‌​‌‌⁠‌‌‌‍‍​‌​‌​​‍​‍‌⁠⁠‌​

But at our UG nickel site, the chief said ‘show me your Deswik macros’ — candidates who can walk through a SO workflow and hand over a small macro get callbacks; bonus if they’ve run a DD422i because it keeps cycle times honest. Bring a one-pager with a stope screenshot and your calc assumptions, not a wall of logos — they’re just hard‑hat stickers. For juniors, depth in one stack (say Deswik + CMS to Vulcan) beats being average across three.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍⁠‌‌‍‍‍​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​⁠​⁠‍​​⁠​‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‍​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‌​​⁠‌‌‌‍‌‌‌​‌‌​⁠​‌‌‌​‌‌⁠‍​‌‍​⁠‌‍‍‌‌‌‌​‌​⁠‌‌‍⁠‌‌‌‍‌‌‌⁠⁠‌‌‌​‌​‍‍​‍​‍‌⁠⁠‌​​

Quick example: I’ve gotten callbacks by opening Deswik in the interview, importing CMS and running a tiny macro that tags stope solids over 8% dilution, then handing them the script. On small crews, DD422i seat time with iSURE drill logs you can explain beats software, but @lhill87’s point stands — show the workflow live.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍⁠‌‌‍‍‍​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠​‍​⁠​⁠​⁠‍​​⁠​‌​⁠​⁠​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‌​⁠​​​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌‍‌​‍​‌⁠‌⁠‌⁠​⁠​⁠​‍‌​‍⁠‌⁠‌‍​⁠‍​‌‌‍‍​⁠‌⁠‌‌‌⁠​⁠​⁠‌​⁠⁠‌​⁠​‌‍‌‌‌‌‌​​‍​‍‌⁠⁠‌​​