The Most Important Jobs Don’t Exist Yet

Applying for jobs feels increasingly downstream. By the time a vacancy appears, the company has already noticed a problem, discussed it internally, translated it into a familiar role, approved a budget, written a job description and decided what kind of person is allowed to apply. The applicant enters at the end of a long chain of decisions. Hundreds of people then compete inside a box that has already been drawn.

The more interesting opportunity may be earlier, before the company has named the problem and before the job exists. Companies are usually described through what they have. Their founders, employees, departments, products, customers, investors and job openings are visible. These things appear on websites, LinkedIn pages, company registries and organisational charts. What a company is missing is harder to see.

An absence has no profile. It has no title. It does not appear in the headcount. There is no empty chair labelled with the work that should be happening. Instead, the missing role appears indirectly. It appears when a founder still has to join every important sales call, when engineers repeatedly answer customer-support questions because nobody owns technical onboarding, when a company keeps launching features but cannot explain its product clearly, or when feedback is collected across Slack, email, sales calls and support tickets while nobody is responsible for turning it into product decisions.

These gaps can remain hidden for years because companies adapt around them. Existing employees absorb the additional work. Founders compensate through longer hours. Customers develop workarounds. Meetings multiply. Small failures are treated as separate incidents instead of symptoms of a missing capability. The company continues operating, so the absence never becomes urgent enough to name.

This creates a strange labour-market problem. There may be valuable people looking for work. There may be companies that need exactly what those people can do. Yet no match occurs because the company has not converted its need into a vacancy. Recruitment systems cannot match someone to a role that does not exist.

Job platforms mostly begin after demand has been formalised. Their job is to distribute the vacancy, rank applicants and reduce the number of people a hiring manager has to examine. Even increasingly intelligent recruitment tools remain focused on describing candidates, extracting skills and matching people to existing titles. The supply side of the labour market is becoming extremely legible. The demand side is still surprisingly primitive.

A company says it needs a product manager, designer, salesperson or developer. The title becomes a rough container for a much more complicated organisational problem. Candidates are then evaluated according to how closely their experience resembles that container. But companies rarely need a title in the abstract. They need someone to make enterprise onboarding repeatable, turn scattered customer complaints into a clear product direction, build trust around an AI system making decisions users cannot understand, or stop every decision from passing through the founder.

The real unit of hiring should be the unresolved mission. A role is only one possible structure for owning that mission.

This is the idea behind Missing. Missing would analyse companies as incomplete systems. It could begin with public signals such as company-registry data, funding rounds, recent hires, new markets, product launches, customer reviews, pricing changes, job listings and visible changes in the composition of the team.

A company that has just raised money is expected to grow, but growth rarely happens evenly. Engineering may expand faster than product operations. Sales may grow faster than implementation. New markets may create localisation, compliance or customer-support problems that nobody owns yet. The system would look for these imbalances. It would ask what the company is trying to become, which capabilities that future requires and which parts of the organisation are likely to break first.

It would then produce something closer to a consulting diagnosis than a recruitment recommendation. The report might observe that a software company has doubled its engineering team, entered the enterprise market and added several salespeople, while the founders still appear to lead onboarding and product demonstrations. The missing capability might be solutions engineering, customer enablement or implementation operations.

The exact title would matter less than the mandate. Reduce founder involvement in onboarding. Standardise implementation. Improve technical documentation. Shorten the time between signing a customer and delivering value. Make enterprise deployment repeatable. Once the mission is clear, Missing could design the role and identify people who have solved the same problem elsewhere.

The pitch to the company would begin with the problem. We noticed that your company is moving toward larger customers, but onboarding still appears dependent on the founding team. We believe this will become a constraint on growth. Here is the evidence, the role we would create, the outcomes it should own during its first 90 days and three people capable of building the function.

This creates a different relationship between a person and a company. The candidate is no longer asking to be allowed into an existing process. The candidate arrives as part of a business thesis. Their experience becomes evidence that a neglected problem can be solved.

This already happens informally at the highest levels of recruitment. Executive-search partners advise companies on leadership structures, challenge role definitions and sometimes convince a board that it needs a different kind of executive. Venture-capital talent partners help founders understand which capability their company needs next. Recruiters occasionally introduce an exceptional person and persuade a company to create a position around them.

Missing would turn that expensive, relationship-driven intuition into a repeatable system. It could bring executive-search-level thinking to smaller companies, earlier-stage roles and problems that are too specific to fit standard job categories.

The system would also need the freedom to conclude that hiring is unnecessary. A company might need to redesign an existing person’s responsibilities. It might need a fractional specialist for six months, a small consultancy project, or an automated workflow supervised by one existing employee.

A recruitment company is usually rewarded when someone is hired. Missing should be rewarded when the missing capability is successfully created. That distinction could become the foundation of the business.

The valuable dataset would not be a larger collection of CVs. It would be a growing map between organisational signals, hidden problems, proposed interventions and real outcomes. Which hiring patterns predict founder overload? Which customer complaints indicate a missing operational function? When does a company need its first product-operations person? Which responsibilities should be combined into one role, and which should remain separate? When does adding another employee solve the problem, and when does it create more coordination?

Over time, Missing could learn from what happened after each intervention. The company signal led to a diagnosis. The diagnosis led to a proposed mandate. The mandate led to a person, team or workflow. The intervention either improved the company or it did not. That feedback loop could become more valuable than the initial matching technology.

Most professional platforms ask people to explain what they can do. Missing would ask companies what they are failing to do, even when they do not yet know how to answer. The name becomes the central interface. Open any company and ask what is missing here. What work has no owner? Where are people compensating for a broken structure? Which customer problem keeps repeating? What will break when the company doubles? Which person could create so much value that the company would build a role around them?

The hidden job market is usually described as jobs that exist but were never advertised. There is another hidden market underneath it. It contains work that is necessary but unnamed, valuable but unbudgeted, visible through symptoms but absent from the organisational chart. These are the jobs that have not been imagined yet.

The most important career opportunity may no longer be finding the right vacancy. It may be finding the work that should exist and giving it a name.

Missing is a search engine for that work.

Connected reading

• The Problems Companies Admit They Have
• The Person Who Decides What Counts as Work
• The AI Was Easy. Understanding the Company Was Hard
• What Kind of Worker Is AI Allowed to Become?
• Why Is AI Making Me Think About Business Strategy?

AI authorship note

This essay began with Kris Haamer’s observation that applying for jobs happens after a company has already understood a problem, approved a budget and designed a role. AI supported the market mapping, differentiation from recruitment and executive search, development of the Missing concept, drafting and implementation. Kris chose the name, established the upstream framing and approved the article for publication.