"Business Operations" Is in 70% of Job Postings. That's a Code, Not a Skill.

Networking for job seekers in 2026 works like strategic DMing, because “business operations” skills show up in more than 70% of U.S. job postings and no longer tell you what a role requires. Indeed Hiring Lab’s April 9 skill breakdown found that more than 70% of postings in Q4 2025 mention at least one business operations skill, and the only way to learn the real role is to talk to the person who owns it.

Healthcare and caregiving skills are the top skill category in 25 states. Business operations tops 20 more. Taken together, those two categories dominate what employers say they’re looking for.

That’s useful as macro data. It’s weak as a search signal. When a single skill category shows up in seven of every ten postings, it stops discriminating between roles. A “business operations” requirement in a listing tells you little, because the range of what an actual employer wants under that umbrella runs from “we need someone to clean up our Zendesk queue” to “we need a COO.” The posting doesn’t tell you which one it is. Neither does the application. The only way to figure out what a role actually requires is to talk to the person who owns it, which is why networking for job seekers in 2026 looks less like attending events and more like strategic DMing.

What does Indeed’s data actually tell us?

That business operations is a catch-all category that most postings touch, not a requirement that sets a role apart. The Hiring Lab analysis covers job postings published on Indeed from October 1 to December 31, 2025, drawn from millions of U.S. postings. It sorts more than 3,000 skills into 47 categories. The dominance of business operations says something about how employers write postings.

A few things are likely going on underneath the 70% number. These are our interpretation, not findings from the Indeed analysis.

First, many employers don’t spell out exactly what they want. They know they need someone to “run things,” a vague function that touches project management, process design, cross-team coordination, vendor management, and ad-hoc firefighting. Rather than try to nail down the specific mix for a given role, postings default to broad operational language that covers everything without committing to anything.

Second, postings are often written by HR or recruiting, not by the hiring manager. The manager asks for a person. HR translates that ask into a posting using a library of standard phrases. The real job requirements, the ones the manager cares about, often don’t make it into the final text.

Third, postings are written to surface in candidate searches, so broad terms that hit a wide audience get included. It’s the keyword equivalent of a blank business card.

The BLS March 2026 report showed payrolls up 178,000, with job gains concentrated in health care (+76,000), construction (+26,000), and transportation and warehousing (+21,000). Those sectors have specific skill demands that don’t flatten easily into generic operations language. The gap between what postings say and where the actual hiring happens is worth paying attention to.

Why does this break the standard job search advice?

Because tailoring assumes a posting with enough signal to tailor to. Career coaches and LinkedIn thought leaders have been saying “tailor your resume to each job” for twenty years. That advice assumes the job posting has enough signal to tailor to. When a posting leans on generic operations language, what exactly are you tailoring toward?

The tailoring advice made sense when postings were specific. A hypothetical 2012 posting for a “Senior Operations Analyst at a Series B SaaS startup in Austin” gave you real material to work with. A typical 2026 version of that posting reads: “We’re looking for a proactive problem-solver with strong business operations skills, comfort with ambiguity, and the ability to partner cross-functionally.” Plenty of SaaS companies use some version of this text. Tailoring your resume to it means guessing what they actually want and hoping the guess matches.

This is where most job search advice fails. Volume-based application strategies crash against low-signal postings. An AI mass-apply tool that tunes your cover letter to the posting just tunes it to noise. You’re not more likely to get a response, because the posting doesn’t actually describe the role the manager is trying to fill.

Hires happen through conversation because conversations produce signal that postings don’t. A 15-minute call with a hiring manager tells you more about a role than reading the posting 20 times.

How do you decode a “business operations” posting?

When you read a posting that leans on business operations language, the useful move is not to guess what the role is. The useful move is to find out who’s hiring for it and ask them.

Start with the posting itself. Skip the skill section. Read the company-context sentences carefully: what’s the team, who do they report to, what’s the primary outcome they care about? If the posting mentions a specific project, product line, or client segment, that’s your first anchor. If it’s generic all the way through, you need to get the context elsewhere.

Move to the company’s careers site and their recent news. Are they launching a new product? Expanding into a new market? Did they just raise a round, or cut staff? That context tells you why they’re hiring. A Series B company that just raised and is hiring for operations usually needs someone to set up finance and ops scaffolding. A mature company hiring for operations often needs someone to clean up a mess. Same title, totally different job.

Now find the hiring manager. LinkedIn is the fastest path. Filter the company’s employees by the function named in the posting. Look for someone with “Director of,” “Head of,” or “VP” in their title whose team lines up with the role. If the posting mentions reporting to “the COO,” find the COO. If it mentions a specific team, find the person leading that team. Usually the hiring manager is two or three filter-clicks away from the company page. The full walkthrough lives in how to find the hiring manager for any job posting.

Finally, read the manager’s last 10 LinkedIn posts or public activity. What are they complaining about? What are they celebrating? What questions are they asking? That content is the real job description. If the manager keeps posting about “needing better reporting infrastructure,” the role is probably going to be heavy on analytics. If they keep posting about “scaling our partnerships program,” the role is partnerships-adjacent.

What should you say when you reach out?

Name something specific, tie it to one piece of your experience, and ask for a short conversation. The mistake most candidates make is treating a cold message like a short cover letter. Cold messages that read like cover letters arrive dead.

A good outreach message to a hiring manager on LinkedIn or over email does three specific things:

1. Names something specific about their work or company that shows you actually paid attention.
2. Connects one piece of your experience to that specific thing in one sentence.
3. Asks for a short conversation, not a job.

That’s it. No “I saw your posting.” No “I’m very interested in the opportunity.” No credentials dump. The manager can see your LinkedIn; they know what you’ve done.

The message should be 100 words or fewer. Too short feels spammy. Too long feels like you’re trying to sell them something. Somewhere between three and five sentences, one of which references their specific situation, is the range that works.

The reason this format tends to outperform polished applications is that it demonstrates judgment. You picked this person. You understood their context. You wrote something only they could have received. Every AI mass-apply tool struggles to do any of those three things, which is exactly why doing them manually is now worth a disproportionate amount of your search time.

How to contact hiring manager on LinkedIn has become a whole category of career advice, mostly bad. The specific mechanics aren’t complicated: connect with a brief note, or send a direct message if you share a group or connection. What matters more than the channel is the content. A LinkedIn message that names their recent product launch and connects it to your experience running a similar launch at a prior company will beat a generic InMail.

Is networking for job seekers in 2026 still a numbers game?

Yes, but the volume belongs on the outreach side, not the application side. The volume-is-king model of job searching has stopped working for most people, and many haven’t updated their strategy.

Here’s an illustrative plan. Pick 30 to 40 companies where your skills map. Identify the likely hiring manager at each. Send 5 to 10 targeted messages per week. If you assume a 10% reply rate, which is our assumption for well-researched outreach rather than a published benchmark, that’s 10 to 15 real conversations per month. Of those, maybe 3 to 5 turn into interviews. Of those, 1 to 2 turn into serious opportunities. The timeline is weeks to months, not days.

Networking for job seekers, stripped of the conference-and-coffee framing, is just doing this at a reasonable pace. You’re not “building relationships” in some abstract career-coach sense. You’re writing specific, well-researched messages to specific people with specific jobs to fill. The relationships happen as a byproduct. The goal is the conversations, and the conversations happen because the messages are good enough that a busy manager replies.

Public postings are one channel, and for roles described in generic operations language they carry even less signal than usual. A lot of the real hiring decisions get made in inboxes and Slack threads.

What should you do this week?

If you’re in an active search right now, the practical sequence is:

• Pick 10 companies you’d actually want to work at. Not 100. Ten.
• For each, find the hiring manager most likely to own the role you’d want.
• Read their last 10 LinkedIn posts and the company’s last 3 press releases.
• Write one specific, short message to each.
• Send them. Follow up once a week later. Then move on.

That’s one week of work. It’s more effort than firing off 100 applications, but the results compound in a way that the application-pile strategy never does. Each manager who replies becomes a node in your network. Each conversation teaches you what that market actually wants. The operations postings that read identically start to differentiate themselves in your head because you’ve talked to humans who live inside them.

The research part, finding the right manager, pulling their recent activity, surfacing the one specific thing to reference, is where the time goes. Angld.ai compresses that pipeline into roughly a minute per target, so the bottleneck moves from research back to where it belongs: you deciding which conversations are worth having. The job market isn’t going to get more specific on its own. Your outreach has to be.

Related: Read how the demographic squeeze changes your job search math and see how to find the hiring manager for any job posting.