The Swiss EFZ Path: What an Apprenticeship Really Teaches You (That Uni Often Doesn't)
In July 2025 I received my Eidgenössisches Fähigkeitszeugnis. the Informatiker EFZ, Switzerland's federal certificate for software developers. It was my second EFZ, actually; my first was as a Spengler. So I've now gone through the Swiss vocational system twice, in two very different trades, which gives me an unusual vantage point on what it does well and where it genuinely has holes.
Since most of the internet's career advice assumes the American "college then job" pipeline, I want to explain how the Swiss path actually works, from the inside, and make the case for what apprenticeship teaches that a lecture hall usually can't. If you're considering it. or comparing it against a university route. this is the post I wished I could have read.
Roughly 70 percent of Swiss students choose vocational training over direct university enrollment. The reason is structural efficiency. The following outlines the realities of the EFZ compared to traditional academic routes.
How the system actually works
The EFZ is built on the dual system: you split your week between a vocational school and a real company. In my case, the school side was Computerschule Bern AG, but the model is the same everywhere in Switzerland. You're not a student pretending to work, and you're not an employee pretending to study. You're contractually both, at the same time, from day one.
An Informatiker EFZ is a four-year program in the traditional form, though shorter compressed variants exist for adults and career changers like me. The curriculum is federally standardized. the same certificate in Bern means the same thing in Zürich or Lugano. and it ends with the IPA, the Individuelle Praktische Arbeit: a real project, done largely alone, under time pressure, documented, and defended in front of experts. Think of it as a miniature thesis crossed with a production deadline.
Two structure points matter a lot:
You practice immediately, not eventually
A computer science student might spend two years on theory before touching a meaningful practical project. As an EFZ apprentice, I was writing code that had to actually work. for actual users, against actual deadlines. within weeks. Theory arrived on schedule at school, but it always landed on ground that practice had already prepared. When we covered database normalization, I had already felt the pain of a badly normalized database. Theory that answers a question you're already asking sticks. Theory that answers a question you'll only ask in three years mostly evaporates.
You're paid to learn
This is not a detail. Apprentices earn a salary. modest, but real. I financed my retraining without accumulating debt, which changes the entire risk calculation of a career change. Compare that with pausing your income for years to study full-time. For adults considering a switch into software, the Swiss apprenticeship is, financially, one of the most rational paths into the industry anywhere in the world.
What the EFZ teaches that university often doesn't
I want to be careful here: this is not an anti-university post. I'm planning a CS degree myself (more on that in another post). But there are things the apprenticeship format teaches structurally. not through any single brilliant teacher, but through the shape of the system itself.
Working inside constraints you didn't choose
School projects let you pick the stack, the scope, the style. Real companies don't. During my apprenticeship I worked in codebases with history, naming conventions I disliked, tooling decisions made before I arrived, and requirements negotiated between people who both mattered more than me. Learning to be effective inside that. without complaining, without rewriting everything. is a professional skill, and it took real time to develop. Many university graduates meet their first legacy codebase on their first job. I met mine in year one.
Documentation as a survival skill
The IPA forces you to document a project in a structured, externally-auditable way: requirements, planning, decisions, testing, handover. It feels bureaucratic until the day you inherit someone else's undocumented system and silently thank every teacher who ever made you write things down. Swiss vocational education treats documentation as part of the craft, not as homework. The industry agrees. it just usually agrees too late and too quietly.
The customer is a person, not a spec
Because apprentices get exposed to real stakeholders early. internal users, external clients, the accounting department that needs its export by Friday. you learn to translate. What a non-technical person says they want, what they actually need, and what is feasible in the time available are three different sets, and the overlap is discovered through conversation, not documentation. That translation skill is, in my experience, one of the rarest things in junior engineers, and the apprenticeship drills it constantly.
Professional tempo
University teaches you to work toward exams: long valleys, huge peaks. Work teaches you to deliver constantly at a sustainable pace. The EFZ, by embedding you in a company, installs the second rhythm. Four years of "show up, be useful, every week" is a different kind of discipline than any semester, and employers can feel the difference in the first month of a new hire.
Where the system falls short
Honesty time.
Depth of theory. The EFZ teaches you to build software well; it does not teach you most of computer science. Algorithms beyond the basics, complexity theory, compiler design, formal methods, advanced mathematics. these are either shallow or absent. I finished my apprenticeship as a competent practitioner with real gaps beneath my feet, and I knew it. That's precisely why a part-time CS degree is on my 2027 roadmap: not because the EFZ failed, but because it was never designed to cover that ground.
Quality variance between companies. Your education depends heavily on which company trains you. A great training company with a dedicated Berufsbildner will grow you enormously. A bad one will use you as cheap labor. The school side can't fully compensate. Choose the company at least as carefully as the school. this is the single highest-leverage decision in the whole path.
The ceiling, if you stop there. In Switzerland the EFZ is a respected qualification and you can build a whole career on it. many do. But it is also deliberately a floor, not a ceiling. The system expects you to keep climbing afterward: professional certifications, a Höhere Fachschule, or a university path via the passerelle or, in my case, direct admission routes for experienced professionals. The EFZ is the start of the track, not the track.
What having two EFZs taught me about the system itself
Going through vocational training twice. once in metalwork, once in software. showed me the system's real design. The EFZ doesn't primarily teach a trade's facts. It teaches a standardized way of working: plan before you execute, document what you decided and why, verify your result, hand over something others can maintain. The sheet metal and the source code were almost interchangeable as teaching material. The craft being taught, underneath both, was disciplined execution.
Once I saw that, a lot of Swiss engineering culture clicked into place. The country's reputation for reliability isn't an accident of national character. It's manufactured, apprentice by apprentice, through a system that treats process quality as the product.
Would I choose it again?
Yes. without hesitation, especially as a career changer. The EFZ got me from a construction site to a professional software job with no debt, real experience on my CV, and a nationally recognized qualification. Its gaps are real but well-defined, and well-defined gaps can be filled deliberately. which is exactly what my next steps are about.
If you're weighing apprenticeship against university: don't ask which is "better." Ask which one matches how you learn and where you're starting from. For me, at this point in life, learning by doing real work, in a real company, while getting paid. nothing else came close.
Member discussion