Apprentice, Journeyman, and Master

Partway through my career, I started wondering what the path actually was, and where it was supposed to go. At some point it clicked: the whole thing is less a path than a marathon. Everyone starts off running in a pack. Some wander off looking for shortcuts. Some stay heads-down on the track they picked. Others find a completely different race partway through and just switch.

People change vocations along the way, moving from high-intensity execution work into mentoring, planning, or leadership. Watching that happen, in myself and in people I’ve worked with, I’ve come to think most people aren’t actually chasing more experience in the singular sense. They’re chasing more experiences, plural: interesting projects, good people to work alongside, and the willingness to move on once a place stops offering either.

“Keep moving, keep learning”, “stay hungry”, that sort of thing gets said a lot, and it’s not wrong, but it skips the actual question: what do you do when you keep moving? What actually stays with you, from job to job, team to team? For me, the answer is your craft: the skill and judgment you carry with you regardless of who’s paying you this year. That’s the part worth asking about honestly. Are you close to mastering it, or are you still early in the apprenticeship, whether or not your job title admits it?

That question is exactly what the medieval guild system was built to answer, and I think it maps onto engineering careers better than most modern career ladders do.

Apprentice

An apprentice bound themselves to a master for a fixed term, usually around seven years, learning the trade in exchange for labor. Most hoped to become master craftsmen themselves eventually; plenty spent time as a journeyman instead, and a real share never ran their own workshop at all. It wasn’t a guaranteed pipeline. It was a real bet on whether the craft would take.

The engineering equivalent is obvious once you say it out loud: the first several years where you’re learning to actually build things that work, under someone more senior, and most of what you produce needs review before it ships. Not everyone who starts here ends up leading a team or an architecture. That’s fine. It was never guaranteed for the apprentice either.

Journeyman

“Journeyman” comes out of the medieval trade guilds. Journeymen were paid by the day; the word itself comes from the French journée, meaning “day”. Crucially, a journeyman could leave. Unlike an apprentice bound to one master, a journeyman traveled between workshops and towns, picking up different masters’ techniques before settling anywhere.

This is the stage most working engineers actually spend the most time in, whether or not anyone calls it that. You’re competent enough to be trusted with real work and paid properly for it, but you’re still deliberately moving, company to company, stack to stack, picking up how different teams solve the same problems differently. The mobility isn’t a red flag on a resume. It’s the point of the stage.

Master

In the European guild system, only masters and journeymen could be full guild members. Getting elected to master meant having actually walked the whole chain: apprentice, then journeyman, before a guild would recognize the craft as fully yours.

The part of mastery that’s easy to miss, looking at it purely as a rank, is that a master’s real job shifts to training the next apprentice. Mastery that stays locked inside one person’s head is a dead end for the craft; mastery that gets passed down is what actually keeps a guild, or an engineering org, or a discipline, alive past one career. That’s most of what mentoring is, in practice: less lecturing, more standing next to someone while they make the mistakes you already made, so they make them faster and recover better.

A Cycle, Not a Ladder

So: everyone starts on a journey. I’ve stopped thinking of it as a straight path with a top, and started thinking of it as a cycle instead. There’s a line from Zen practice that’s stuck with me here: the beginner’s mind gains the most, and the early stretch of any new pursuit, apprentice again at something, is usually the most enjoyable part of the whole cycle. Mastery in one craft is often just the apprenticeship for the next one, if you let it be.

If you’re somewhere in that cycle and want a second opinion on the craft, or want someone to think through mentoring, for you or your team, say hello.