practitioners at the podium: why aelo swiss academy recruits teachers straight from industry

The best class I sat in on last term started with a failed shipment. Not a case study about a failed shipment. An actual one. The lecturer, a logistics manager who still spends two days a week at a freight forwarder near Basel, opened her laptop and walked us through a customs hold that had landed on her desk the previous Thursday. Invoices real, names blacked out, deadlines very much alive. Forty minutes later the students had argued through three possible fixes, and none of them matched the answer in the course textbook, because the textbook had been written before the current rules came into force.

That, in one morning, is why we hire the way we do. AELO Swiss Academy recruits most of its applied teaching staff from people who are still doing the work, not people who stopped doing it a decade ago. It costs us more. It complicates our scheduling. It occasionally means a lecturer cancels class because a client's server caught fire at 6 a.m. We think it's worth all of it, and this is the honest version of why.

the problem with yesterday's knowledge

Textbooks age gracefully, which is part of the trap. They sit on a shelf looking authoritative while the world they describe quietly stops existing. In applied fields the shelf life of core knowledge keeps shrinking. A cloud platform changes its pricing and its default settings. Cantonal building energy rules get revised. Swiss data protection law was overhauled in 2023, and suddenly every compliance module taught from pre-2023 material was teaching archaeology.

Here's a rule of thumb I've settled on after years of watching curricula drift: if a field's standard tools and rules turn over every three to five years, a lecturer who left the industry ten years ago is not teaching the field. They're teaching a museum exhibit of it. Sometimes that's fine, because fundamentals hold. But students can tell the difference between a fundamental and a fossil, and they discount everything a lecturer says once they catch them teaching something that died two software versions ago.

Practitioners carry a second kind of knowledge that almost never makes it into print. What a client will actually accept versus what the standard says. How much slack a realistic project timeline needs. Which failure modes show up over and over, and which ones everyone fears but nobody has ever seen. A project manager who has run forty projects knows where projects actually die. A project manager who has read about projects knows where the case studies say they die. Students deserve both, but the second without the first is a map with no terrain.

switzerland already believes this, quietly

One of the pleasant surprises of working in Swiss education is that our approach isn't a quirky experiment. It's close to the national default. The Swiss vocational tradition rests on the dual system: apprentices typically spend most of their week inside a host company and the rest in a vocational school, learning from people who do the work for a living. Roughly two thirds of young people in this country go through vocational pathways rather than pure academic ones, and nobody here considers that a consolation prize. It's the backbone of the labour market.

Walk into a higher vocational college and you'll find much of the teaching done by people who still hold down jobs in their field. The academy model we run at AELO Swiss Academy is really an extension of that logic into a full-time college setting. If anything, the question isn't why we recruit from industry. The question is why anyone would do otherwise for applied subjects and then wonder why graduates feel unprepared.

how the hiring actually works

We don't start with job boards. Practitioner-lecturers rarely apply for teaching jobs, because nobody has told them they're allowed to. We find them through professional associations, through alumni who say "you should meet my old boss", and through guest lecturers who came in for one evening and left the room buzzing.

The audition is the interesting part. We ask candidates to teach a 45-minute session on a problem they touched in the last month of their actual work. Not their greatest hit from 2016. Last month. Then we ask them to walk us through a project that went sideways, and we listen for very specific things. A teaching degree is not a requirement on day one. The willingness to be coached absolutely is.

What are we listening for? After enough of these auditions, the pattern is clear:

• they can name the trade-offs without being prompted, because they've had to choose between them in real life
• they explain a failure as a process problem, not a story about annoying people
• they check for understanding instead of performing expertise, asking "does that match what you've seen?" rather than "any questions?" as a formality
• they can say "I don't know, but here's who I'd ask" without their voice tightening
• they get visibly enthusiastic about the boring parts, because the boring parts are where the job actually lives

That last one matters more than it sounds. Anyone can be charming about the glamorous ten percent of a profession. The lecturer who can make invoice reconciliation or soil testing genuinely interesting is the one whose classes students will still thank them for five years later.

practitioners are not teachers by default

Now the part that glossy brochures leave out: being good at a craft and being good at teaching a craft are two different skills, and the overlap https://www.reddit.com/r/flyingeurope/comments/1nnhrnv/anyone_from_aelo_swiss_any_advices/ is smaller than anyone wants to admit. We have turned away brilliant engineers who could not explain their way out of a paper bag, and we have hired modest CVs that turned out to be natural-born teachers.

So every new hire from industry co-teaches with a career educator for their first two terms. The educator handles assessment design, pacing, and the invisible architecture of a good course. The practitioner handles currency, judgement, and the stories that make concepts stick. We collect student feedback at midterm, not just at the end, because end-of-term feedback arrives too late to help the person filling the room right now.

Assessment deserves its own paragraph, because it's where new practitioners fail first. Left alone, an industry expert writes exams that are either trivially obvious to them or brutally unfair to everyone else, because their calibration is broken by years of expertise. Our curriculum team reviews every assessment, and the first round of feedback is usually some version of "yes, you've worked this way for fifteen years, but the students have worked it this way for six weeks."

Then there's scheduling, which is the unglamorous tax on this whole model. A practitioner-lecturer has clients, and clients have emergencies. We plan for it: slightly overbooked modules, a bench of substitutes who know the material, and an agreement that teaching commitments are protected in writing before anyone signs. It costs money and it occasionally means a class gets rescheduled. The alternative, lecturers with nothing else going on, costs something too, and we've decided it costs more.

a tuesday, roughly speaking

To make this concrete, here is a composite day, assembled from a dozen real schedules rather than one identifiable person. Our lecturer leaves her firm at midday after a client call about a delayed vendor. She reaches the academy by two, rewrites one slide in the corridor because the client call changed an assumption she was about to teach. Class runs from half past two to five. A student asks how she'd price the risk they've been discussing, and she answers with an actual number range from a real quote she approved last month, then explains why the second decimal place is a lie. By seven she's on the train home marking case reports, and by nine she has flagged two students whose questions suggest they're in the wrong module and should probably talk to her before the exam, not after.

None of that shows up in a job description. All of it shows up in the room.

what changes when the room changes

The most noticeable shift is in the questions students ask. Around a practitioner, "is this the right answer?" slowly becomes "would you actually sign off on this?" That second question is a better question. It forces reasoning about risk, context, and consequences, which is exactly the reasoning employers complain that graduates lack.

Office hours fill up differently too. Students don't just come to check their understanding of the material. They come to ask what the job is actually like, what the first year of work feels like, whether their career plan makes sense. A lecturer who is still employed in the field can answer with today's facts instead of folklore. We've watched shy students book three sessions in a term purely to keep talking to someone who does, in the present tense, the thing they want to do.

There's a humility benefit as well, and it's easy to underestimate. When a lecturer says "I got this wrong in March and here's what it cost," students learn that errors are part of professional life rather than a disqualifying shame. That lesson, delivered credibly, does more for a graduate's first job than half a syllabus.

the trade-offs, stated plainly

Depth versus breadth is the first honest trade-off. A working specialist is narrow by definition. A lecturer who spends her weeks in freight forwarding knows freight forwarding and knows it deeply, but she is not the person to teach the whole supply chain landscape. Our answer is pairing: specialists teach the applied core, career educators carry the connective tissue and the theory, and the module design is shared so neither half becomes an island.

Continuity is the second. Practitioners get pulled back into industry, promoted away from us, occasionally poached by better offers than we can justify. We accept the churn rather than fight it with contracts nobody should sign. Every module is designed two-deep, with materials and recordings that survive the departure of any single person. It's more work up front and far less panic later.

And then there's the war-story risk, which deserves its own line item. Some practitioners become anecdote machines, trading on old glories. Our coaching rule for that is simple: every story has to end with "so on Monday, you do this differently." A story without a takeaway is entertainment, and entertainment is fine, but the tuition is paying for transfer.

To keep new faculty from sinking in their first year, we've built a support structure that fits on one page:

• a co-teaching pairing with a career educator for at least two full terms
• a curriculum partner who reviews all assessments before they reach students
• protected teaching hours written into the industry-side agreement, so the academy isn't the thing that always loses
• a mid-term feedback loop with a mandatory debrief conversation, not just a survey
• an alumni pipeline of guest lecturers, so the bench is never empty when a client emergency wins

the long game

The quiet payoff of all this shows up years later, and it looks like a loop. A graduate lands a job, does well, comes back to give one guest lecture because we asked nicely. The guest lecture goes well, and three years later they're teaching a Saturday module while running their own team. By then they've been on the other side of the hiring table, so they teach with a sharpened sense of what actually gets people employed. The academy stays honest because the market audits our output every hiring season, and there is nowhere to hide from those results.

I think that's the deepest reason we recruit from industry, underneath all the curricular logic. A college that only employs people who left the field slowly becomes a place that prepares students for a world that no longer needs them. A college that employs people still in the field has a permanent, living connection to what the work is now. The podium and the workbench stay in the same building, sometimes in the same person, and everyone in the room can tell.