DeskForge Academy

Build a help desk career with practical IT support training

This page is the slow tour: how tracks stack, how labs feel on your calendar, and what “career outcome” means in plain operational language without inventing guarantees.

Program tracks

Foundations cover first-shift rhythm, then ticketing depth, then communication studios, then device triage, then career-adjacent modules. You can enter at foundations or jump to ticketing if you pass a short readiness writing sample.

Each track ends with a capstone artifact: a sanitized ticket journal, a short voice sample with self-critique, or a device triage log your facilitator signs off as “credible for interviews.”

Notebook and keyboard on a desk during a writing exercise

Live lab experience

Labs are timed, slightly uncomfortable, and observed. We want you to feel the mild panic of a real queue before you meet one at work—then we decompress with structured feedback cards instead of open-ended rambling.

Audio and chat labs rotate facilitators so you hear more than one coaching voice. Device labs stay in VMs unless your employer sponsors a supervised hardware window.

Career outcomes

Outcomes here mean artifacts and vocabulary you can defend in an interview: activity logs, triage rationales, and calm customer language. We track cohort satisfaction with varied scales and sometimes skip numbers entirely in favor of qualitative themes.

We do not publish placement percentages as marketing levers; employers change budgets too fast for that to stay honest season to season.

Flow sketch — how weeks reinforce each other

Linear flow from foundations to capstone with feedback loops Foundations Tickets Voice Capstone Feedback loop into next lab block
Diagram is schematic; your cohort calendar may reorder blocks for holidays.