Looking through our InterviewPal job listings data and BLS Job openings data this week, one number jumped out. In the last 12 months, there were 162,325 startup openings with "Manager" in the title. Software Engineer? 37,286. Managers outnumber software engineers by more than 4 to 1.

That's not the picture most people have of startup hiring. Scrappy team of engineers building a product, etc. The actual job board looks more like a team of managers and specialists with some engineers mixed in.

Rest of the breakdown, in order: Manager (162K), Engineer (145K, which is a broad bucket covering mechanical, data, all of it), Specialist (56K), Technician (54K), Director (43K), Analyst (43K). Software Engineer doesn't show up until 37K. Customer Service is 33K. Account Executive is around 17K. Account Manager is 15K. Product Manager is 14K. HR is 14K.

Bundle the three customer-facing titles (Customer Service, Account Executive, Account Manager) and you get 67,000 openings. Almost double the Software Engineer count. And if you go look at the interview prep content out there, basically none of it is for those 67,000 jobs. It's all for the 37K.

That's a real gap and honestly part of why I'm writing this. Our content on InterviewPal skews engineer too, because that's who reads tech career blogs and that's who shows up in our search traffic. The jobs are increasingly somewhere else.

What this changes for job hunting and interview prep

The interview prep gap that bothers me most here is the manager one. There are 162K of these jobs and the loops are genuinely strange, and almost nobody is writing useful prep content for them.

A startup manager interview is not what people picture. It's not an hour of "tell me about a time you had a difficult report." You get behavioral questions, but you also get asked to sketch a 90-day plan on the spot, walk through how you'd hire your first three reports, and reason about budget tradeoffs in real time. I've seen candidates walk in primed for conflict-resolution storytelling and get hit with "okay, so what would you actually do in week one" and just fold. They prepared for the job interview. They didn't prepare for the job.

The other one worth flagging quickly: if you're a software engineer with a couple years of experience applying to roles posted as "Software Engineer," the bar has crept up. Look at the ratio. 37K Software Engineer postings, 12.5K Senior Software Engineer postings. What's happening is startups are putting "Software Engineer" on listings they're actually screening at senior bar to widen the applicant pool. You walk in thinking it's mid-level and get system design questions calibrated for staff. Prep accordingly.

The country numbers are weirder than I expected

US is 561,198 jobs over the last year. Fine, expected. After that it gets interesting.

UK 66K, India 60K, Canada 44K, Germany 28K.

India almost matching the UK is the one I'd push on. I have spend a lot of time focusing on India job data and the startup hiring there has clearly been compounding, but seeing it 60K deep on a single tracker still surprised me. If you're prepping for Indian startup interviews using American interview content, you're prepping for the wrong thing. The loops are very different in my opinion. Heavier DSA in the first round at the product startups, much more emphasis on system design under actual cost constraints (compute is expensive, so "just throw more servers at it" never flies), and compensation negotiation that operates on completely different anchors.

Spain is 11K, which I should have guessed higher given how much I see going on in Madrid and Barcelona but I didn't. Mexico at 10K. Netherlands at 9K. Singapore at 7K. Most of the prep content in English ignores all of these markets.

The ghost market problem

Here's something the headline numbers don't tell you. Manager has 162K openings. Software Engineer has 37K. So Manager looks like the better market.

But that ignores who's applying. Every senior IC with five years of experience and a little ambition thinks they're ready to be a manager. So the applicant pool per Manager opening is enormous. I'd guess somewhere in the 150-250 range for any decent Manager role at a reasonable startup. Meanwhile Specialist openings (56K, the second biggest IC bucket) get a fraction of that, maybe 15-30 applicants per role, because the title sounds boring and nobody dreams of being a Specialist.

So your actual odds of landing a given Specialist role you apply to are probably 5-8x higher than your odds of landing a given Manager role, even though there are fewer Specialist listings overall. The big number is a trap. The small number with a thin applicant pool is where the actual opportunity is.

I think of this as the ghost market. The listings exist, they're posted publicly, anyone can apply, but nobody's competing for them because the title doesn't trigger the same career fantasy that "Manager" or "Software Engineer" does. The 56K Specialist roles, the 54K Technician roles, the 43K Analyst roles, these are huge pools of openings sitting there with way better odds than the listings everyone fights over.

If you're job hunting and you keep coming up short, look at what you're applying to. If everything has a glamorous title, you're probably competing against the entire LinkedIn population. Pivot toward the unsexy titles and you're playing a different game.

You're searching for the wrong words

Related to the ghost market thing but worth its own section because it explains why the ghost market exists in the first place.

There's a gap between the words employers use to title jobs and the words candidates type into search bars. It's bigger than you'd think.

Employers post "Specialist" 56,000 times. Candidates almost never search "specialist." They search "junior" or "associate" or "entry-level." Employers post "Technician" 54,000 times. Candidates search "engineer" or "developer." Employers post "Analyst" 43,000 times. Candidates search "data scientist" because that's the title they want, not the title that exists.

What this means in practice: a candidate sets up job alerts for "software engineer" and "developer," gets maybe 60K listings to wade through across boards, and never sees the 56K Specialist roles or the 43K Analyst roles that they're actually a fit for. Their search query is filtering them out of half the market.

The fix is dumb but very effective imo. Search for the titles employers actually use, not the titles you think the job should be called. If you're a data person, search "Analyst" not just "Data Scientist." If you're early career, search "Specialist" and "Associate" and "Coordinator" alongside "Junior." If you're technical, search "Technician" because in 2026 a lot of what gets posted as "Technician" is actually pretty technical work that used to be called "Engineer."

I'd bet that a candidate who runs three or four extra title searches alongside their primary one doubles the number of relevant openings they see. Possibly triples it. The listings are there. They're just hiding behind words nobody thinks to type.

The 100-hour job hunt

Last thing, and this is the one I think is least understood by people actually job hunting right now.

Getting a startup job in 2026 is not a couple-of-weekends activity anymore. It's a part-time job that takes about 100 hours over three months, and most candidates allocate maybe 20 hours total before they give up and conclude the market is broken.

The math is rough but it goes like this. Average time to fill a startup role is around 44 days, which means any given application you send sits in a queue for over a month before you get a real signal. To have something happening at all times, you need overlapping pipelines. A reasonable rule is that to land one offer in a quarter, you want maybe 8-12 active interview loops running, which means applying to about 150-200 roles, because most applications go nowhere.

Each application, done properly (light resume customization, a real look at the company, a tailored cover line or two), takes 20-30 minutes. So 150 applications is roughly 60-75 hours just on applying. Then each loop you actually get into is 5-7 rounds at this point, which is another 5-8 hours per loop in prep and interviewing. If you get 8 loops, that's another 40-60 hours.

Add it up and you're at 100-130 hours over three months to give yourself a reasonable shot at one offer. That's about 8-10 hours a week, which is a real second job.

What I see most candidates actually do: send 25-40 applications over a couple of weeks, mostly to roles where they meet 90%+ of the listed requirements, get rejected or ghosted on most of them, conclude the market is impossible, and stop. They allocated maybe 15-20 hours total. They were doing roughly 15% of the volume the math says they needed.

I feel like the market isn't still fully broken but it's just very much calibrated for a level of effort that nobody talks about, because admitting "getting a job now takes 100 hours of focused work" sounds defeatist. But the candidates I see actually landing offers in 2026 are putting in the hours. The ones complaining loudest are usually the ones who haven't started running the right number of pipelines.

One thing I'll add to all of this. If you do put in the 100 hours and you actually get an offer, do not wing the comp conversation. The number of candidates I see grind through three months of job hunting and then accept the first number the recruiter says is genuinely depressing. Look up what the role pays in your market before the offer call, not after. (We keep salary data by role and location on our salary page if you need a starting reference.)

Anyway, that's what the listings look like right now. Mostly I just wanted to flag the manager number because it's been stuck in my head for a week.