> ## Content Index
> Fetch the complete content index at: https://www.missionsforhumans.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# The Job That Didn't Exist Yet
- URL: https://www.missionsforhumans.com/the-job-that-didnt-exist-yet/
- Published: 2026-07-15T19:31:00.000Z
- Updated: 2026-07-24T19:32:02.000Z
- Author: Missions For Humans

In 1953, a doctor named John Gibbon connected a patient's circulatory system to a machine for the first time in history, and for eighty minutes, that machine did the work of a heart and a pair of lungs while surgeons repaired what lay beneath. The patient lived. And somewhere in that operating room, a job was born that had never existed before: someone had to run the machine. Watch it. Understand it well enough to know the difference between working and failing, in real time, with a human life suspended in the gap.

Nobody trained for that job before it existed, because there was nothing to train for. The perfusionist came after the machine, not before it. The skill had to be invented at the same speed as the need.

We tell this story to fourth graders because it is, quietly, the most honest thing you can tell a child about the future of work. Not "learn to code" or "these are the safe careers" or any of the other confident predictions adults have made about the job market and gotten wrong within a decade. The honest thing is this: nobody knows exactly which jobs will exist when you're an adult, including the ones that will matter most, and the ability to adapt when the answer changes is worth more than any single skill you memorize today.

This is not a comfortable thing to build a curriculum around. Certainty sells better. But certainty about the future of work has a poor track record, and children deserve better than false confidence dressed up as career guidance.

What does hold up, generation after generation, is the underlying pattern. Jobs get created when a real problem meets a real capability. Someone builds a machine, and someone has to run it. A community grows, and someone has to solve the new friction that growth creates. Technology automates a task, and a different, more human task rises up to take its place, usually one involving judgment, care, or the kind of nuance a machine hasn't figured out yet. Understanding that pattern is more durable than memorizing a list of current job titles, most of which will look different, or vanish, or get renamed by the time today's students are old enough to hold them.

[This is the thinking behind the Career Exploration lesson,](https://www.teacherspayteachers.com/Product/Career-Exploration-Jobs-Skills-Wages-Salaries-Commission-Grades-35-17028850?ref=missionsforhumans.com) structured as a job fair that spans time itself. Students meet careers born from genuine need, healthcare, skilled trades, cybersecurity, renewable energy, alongside the story of the perfusionist, a career that quite literally did not exist until a doctor built a machine that made it necessary. They learn to tell the difference between a job that's real and one that only sounds real, and they practice the more useful skill underneath: asking what a job is actually for, what problem it solves, and why someone gets paid to solve it. That question, more than any specific vocabulary list, is the one they'll need to keep asking for the rest of their working lives.

Somewhere in the next decade, a new machine will get built, and a new job will get born to run it, and the child who learned to ask "what problem does this solve" will be better positioned to notice than the child who only learned to fear or worship whatever technology arrives.

**Report Back**

Think about your own work for a minute. Is there a piece of it that didn't exist when you started your career, something you had to learn on the fly because the need arrived before the training did? That's the skill worth naming out loud to the kids in your life. Not the job title. The adaptability underneath it.