Entry-Level Roles Now Want a PMP. The Job Description Is Lying. Here's How to Find Hiring Manager for a Job and Ask.

To find the hiring manager for a job whose posting asks for more than it needs, identify the person two steps above the role and ask them directly whether the requirement is real. PMI’s eligibility rules require 36 months of project leadership experience for the PMP (with a four-year degree), so an “entry level” role that demands the cert can’t be entry level.

A r/jobs post in late April put a clean point on a problem every job seeker has noticed. The title: “What’s up with these entry level Project Management roles requiring a PMP cert?” The poster’s point is right on the technical detail. PMI’s eligibility rules require either 36 months of project leadership experience (for candidates with a four-year degree) or 60 months (for those with a high school diploma or associate’s degree), plus project management education hours. An “entry level” role that requires the cert is not, by definition, entry level. Commenters on the thread raised the other obvious possibility, that such postings are ghost jobs and impossible qualifications make it easier to reject candidates. Both observations hold up, and both are reasons to learn how to find hiring manager for a job and ask what the role actually needs, rather than self-screening out of postings that probably don’t mean what they say.

This is not a complaint piece. The credential mismatch in job postings is real and well-documented, but it cuts both ways. Listed requirements often overstate what the company will actually accept. And the candidates who get hired into those roles tend to be the ones who got in front of the person making the call.

Why do job postings list requirements that don’t match the actual hire?

There are three structural reasons a posting ends up requiring a PMP for an “entry-level” role, and none of them are about the role itself.

First, the posting is a copy-paste artifact. HR or a recruiter pulls the requirements section from the last similar role they posted, which itself was pulled from the one before that. Cert lines like “PMP preferred” or “PMP required” survive across postings because nobody on the requirements side of the chain has a reason to remove them. The hiring manager for the actual role often hasn’t read the final posting.

Second, the requirements line can be a procurement filter, not a hiring filter. Some postings exist because corporate policy requires the role to be advertised externally before being filled internally. Some exist because a vendor SOW or government contract requires “advertised qualifications” at a specified level. These postings are not screening for the best candidate. They’re screening for compliance evidence the company can show to a third party. The PMP requirement on an entry-level posting may be more about a contract clause than about what the team actually needs.

Third, ghost jobs are a real share of the market. Some are old roles that didn’t get taken down, some are pipeline-building exercises, some are competitive intelligence plants. None of them care whether the listed requirements are achievable. These three explanations are not mutually exclusive: an impossible requirement can be a copy-paste artifact, a compliance filter, and a ghost-job tell all at once.

What does the data say actually gets a candidate hired?

Hiring managers can override a listed requirement for a candidate they want. The Burning Glass Institute and Harvard Business School’s Project on Managing the Future of Work published a report in February 2024 called “Skills-Based Hiring: The Long Road from Pronouncements to Practice.” Its main finding is that many companies announced they were dropping degree requirements, but sustained hiring changes remain elusive for most. By the report’s count, the expanded opportunity showed up in not even 1 in 700 hires. The gap between what companies say their requirements are and what they actually use to filter candidates is wider than the public narrative suggests. The same dynamic plausibly applies to certifications. The PMP “required” line on a posting and the PMP “actually screened on” filter inside the ATS can be different things, and a hiring manager who likes a candidate has latitude to override the cert line.

Lightcast’s research on underemployment adds a related picture. In “The Permanent Detour,” four in 10 college graduates are underemployed in their first job, and about two-thirds of those are still underemployed five years later. The picture this paints is a labor market where postings systematically overstate requirements, candidates systematically defer to those overstated requirements, and the people who get into better roles are often the ones who didn’t take the postings at face value.

Referrals are the clearest route around inflated requirements. Ashby’s Q1 2026 benchmarks, as compiled by candidate.fyi, show referred candidates passing the recruiter screen at 52% versus 35% overall. Direct outreach to hiring managers is the cold version of a referral. It has a lower hit rate than a warm intro: Instantly’s 2026 benchmarks put the average cold email reply rate at 3.43% and the top quartile at about 5.5%. But a reply is a human conversation, and the roles filled this way can go to candidates whose resumes wouldn’t have cleared the listed posting requirements, because the hiring manager looked at the candidate’s actual work, heard a specific case for the role, and made the call.

How to find hiring manager for a job in five minutes per posting: what are the steps?

Look two steps above the role, cross-check on LinkedIn, then find a contact channel. Before going around an inflated requirements line, the candidate has to identify the person who will actually make the hiring call. That person is rarely the recruiter named on the listing.

Look at the org chart. For a “Project Management Specialist” or “Project Coordinator” role, the hiring manager is the Director of Project Management, the Head of Operations, or the team lead the role would report to. For a software engineering role, it’s the engineering manager. For a product role, it’s the head of product or the VP of product. The pattern: two steps above the role and one team over from HR. LinkedIn’s company-page employee search filters by job title, which gets most candidates most of the way there in five minutes.

Cross-check the candidate. Look at the person’s recent LinkedIn posts, the company’s leadership page, and any press where someone got named. If a candidate is unsure between two possible managers, the senior of the two is the safer bet; senior managers route messages down faster than junior managers route messages up.

Find a contact channel. LinkedIn is the most reliable, especially with a connection request that includes a short note. Email is faster if the address is available; predictable patterns at many companies (firstname.lastname@, firstinitiallastname@, first@) work for a lot of corporate domains, and tools like Hunter or Apollo can verify addresses for many public-facing managers. The goal isn’t perfect attribution. It’s a real channel that puts a message in front of the actual decision-maker.

The full process, end-to-end, takes about five to fifteen minutes per posting once a candidate has done it a few times. The bulk of that time is reading enough about the manager to write a non-generic message; the address-finding part is mechanical.

What should you ask once you have them?

The four-sentence message that works for an inflated-requirements posting opens with a specific reference (a talk, a blog post, a recent company announcement), connects it to the candidate’s actual experience in the relevant area, asks one specific question about the role, and signs off cleanly. The specific question is the lever for the requirements problem.

Good versions of the question, for an entry-level role with a PMP requirement: “I noticed the posting lists PMP as a requirement, but the responsibilities read like a coordinator role; is the cert a hard requirement or a preference for this seat?” Or: “Would the team consider a candidate with three years of PM experience but no PMP, given the rest of the job description?” Or: “I’d love to understand whether the PMP line reflects a contract requirement or a screening preference; happy to discuss either way.”

These questions are direct, they don’t ask the manager for a favor, and they give the manager an easy out if the cert really is required. Some managers will say the cert line was a copy-paste artifact and they’re open to the right candidate without it. Others will say the cert is genuinely required (often for contract or compliance reasons) and the candidate now knows to skip the role rather than burn a week applying. Either answer is more useful than self-rejecting based on the posting.

The contrast with the standard application path is worth being explicit about. The candidate who applies through the portal with no PMP may get auto-rejected, learns nothing, and moves on. The candidate who messages the hiring manager either learns the cert is negotiable (and has now started a conversation) or learns the cert isn’t, and has saved the time. Same starting position, different information, different outcome.

When is the requirement real, so you should not go around it?

When it is a legal or regulatory license. This advice has limits, and they matter. Some certifications and licenses are non-negotiable, and they should be. Registered Nurses without an active RN license cannot practice as a nurse. Certified Public Accountants signing off on audits need the CPA. Practicing attorneys need a JD and bar admission. Securities license requirements (Series 7, Series 63) for client-facing brokerage roles are regulated. Commercial Driver’s License roles require the CDL. In these cases, the requirements line on the posting reflects an actual legal or regulatory constraint, and going around it would put both the candidate and the hiring manager in a bad position.

The PMP, by contrast, is not a license. It’s a vendor-issued certification with no legal status. Many “entry-level” certs that come up in discussions like the Reddit thread (PMP, SHRM-CP, AWS Solutions Architect) sit in the same category. They confer credibility, they can be required by some contracts, and they signal a certain training experience, but they do not legally gate the work the way a state-issued professional license does. The judgment for the candidate: if the cert is regulatory, the posting is probably accurate; if the cert is vendor-issued, the posting is more likely to be inflated and the message to the hiring manager is the right next step.

When in doubt, the question to ask the hiring manager is the question itself. “Is this requirement a regulatory matter, a contract requirement, or a preference?” The honest manager will tell you, and the answer determines whether the posting is worth pursuing.

Is there a faster way to do all of this?

The friction in this whole process is the research per posting: finding the right hiring manager, finding their email or LinkedIn, finding one specific recent thing to reference, and drafting a message that doesn’t read as generic. Done by hand, that’s 15-25 minutes per role. Done at a volume that gives you a few real conversations a week, the time investment becomes a problem most candidates can’t carry while also working a current job.

If the process described above sounds like a lot of manual work, it is. That’s why tools like Angld.AI exist: to compress the research-to-outreach pipeline from twenty-plus minutes into about sixty seconds. Paste a job posting; the tool identifies the likely hiring manager for the role, surfaces specific recent context they have produced (LinkedIn posts, talks, releases, articles), and drafts a personalized message you can edit before sending. The five-step process above collapses into two: read the suggested context, edit the draft, hit send. The credential inflation problem doesn’t go away. It just stops being the thing that ends a candidate’s interest in the role. The posting can still lie about the PMP. The hiring manager can still tell you the truth.