Day One

You woke up before your alarm.

It's dark outside and cold enough that your breath makes small clouds in the driveway. Your fire rated uniform is clean and pressed — you made sure of that last night. New Red Wings, still stiff, not yet broken in. You've got your laptop, company phone, backpack, a rolled up submittal drawing, and forty-five minutes of highway between you and the job site.

You've been waiting for this.

You find the right gate. Of course. It's obvious now — contractor trucks everywhere, a whole ecosystem of work vehicles parked in loose rows. You spot your mentor's Transit Connect and pull in next to it. He's already inside.

You call him. He tells you where he is. You put on your clean new high-vis vest and spotless hard hat, grab your stuff, and head in.

The smell hits you first. Dust and drywall and something electrical you can't quite name. Then the noise — not one sound but twenty sounds layered on top of each other. The building is alive with people and none of them are there for the same reason.

Demo crew ripping out wire. Plumbers running pipe. Electricians everywhere — more than you expected. Fire alarm crew. Painters. Pipe fitters. Ceiling crews. Drywall crews. Flooring crews. Concrete crews. It goes on.

You find your mentor in the middle of it. He hands you two rolls of colored electrical tape.

You spend the morning doing exactly that. Tracing wire you don't understand in a building you've never been in, helping demo guys cut the right ones and leave the rest. The building had an existing controls system. These wires are probably related to that.. probably.

It's loud and dusty and disorienting and you're doing your best to look like you belong here.

By mid-morning things get quieter.

You follow your mentor up to a mezzanine in the back of the building — AHU-3, smaller than the others, tucked away from all the chaos. Brand new unit, factory mounted controls. Your job is to program it.

But first — the wiring doesn't match the submittal. And the wiring diagram on the unit itself isn't quite right either.

You ask the question out loud before you can stop yourself.

You file that away somewhere. The world just got a little less predictable.

You're eager to jump in. Excited to start programming. Your mentor climbs down the ladder and then stops.

And then he's gone.

All by yourself on a mezzanine in a building you never saw before this morning. Safety vest, hard hat, FR clothing looking not so new anymore. Holding a submittal and a pen, no one to call for help, and it’s not even time for lunch.

You look at the paper.

You look at the unit.

You look at the paper again.

What's actually happening here

Nothing about this moment was designed to trick you or embarrass you. Your mentor wasn't testing whether you already knew the answer. He was doing something more important — he was finding out how you handle not knowing.

That's the first real skill of this job. Not wiring. Not programming. Not troubleshooting. It's what you do in the moment between being handed something you don't know how to do and the moment you figure it out.

Because that moment is coming. Over and over again for the rest of your career. The job site doesn't pause while you get comfortable. The building doesn't care that it's your first week. And nobody — no certification, no course, no amount of classroom time — can fully prepare you for the feeling of standing in front of something real and being responsible for making it work.

What your mentor gave you on that mezzanine wasn't a problem. It was a gift. A chance to sit with the uncertainty, look at what you actually knew, and take a first step.

The safety circuit got drawn. Maybe not perfectly. Maybe with a little help. But it got drawn, and then it got wired, and then the unit ran.

And you never forgot how to draw one again.