Applying through a job board puts a resume into a queue a hiring manager may never open. Finding a hiring manager's email address and writing to them directly, before the role disappears under three hundred other applications, changes the odds in a way most job seekers never actually test.
Most people who try this give up after one bad guess. They type firstname.lastname[at]company.com into a browser, send it, get a bounce-back, and conclude that "nobody actually emails hiring managers." The problem usually isn't the idea. It's that email address guessing without a way to check the guess is basically a coin flip, and most companies use a pattern that isn't the obvious one.
Why the hiring manager's inbox matters more than the application portal
An applicant tracking system exists to filter people out, not to find the right one. A recruiter scanning three hundred resumes for a single role is optimizing for speed, which means keyword matching and quick rejections, not careful reading. A hiring manager's inbox has none of that friction. A short, specific, well-timed email lands the same way a referral does: it skips the queue entirely and gets read as a person, not a line item.
This is also why timing works in your favor. Most applicants send an email that says "I saw the posting and am applying" a week after the role opened, once it already has two hundred applicants. The version that works is sent the day the posting appears, or even before there's a public posting at all, because the hiring manager already knows the team needs someone and just hasn't finished writing the job description.
Where to actually find the name first
You cannot find a hiring manager's email address before you know who the hiring manager is. LinkedIn is still the fastest way to identify this. Search for the department at the company ("engineering manager," "director of marketing," "VP of sales") combined with the company name, and look at who has been in the role for at least six months. A manager who started two weeks ago is unlikely to be the one running the hiring process for an open req yet.
The job posting itself is a second source that people skip. It often names the team ("reporting to the Head of Growth") even when it doesn't name a person. Cross-reference that title against the company's LinkedIn page and you usually have a name within a few minutes.
The four patterns that cover almost every company
Once you have a name, the email address is almost always built from one of a small number of formats. In order of how often they show up across small and mid-sized companies:
- first.last[at]company.com — the most common pattern at companies with more than a handful of employees, because it avoids collisions when two people share a first name.
- firstlast[at]company.com — common at startups and smaller teams where the name space is small enough that collisions are rare.
- first[at]company.com — common at very small companies (under twenty or so people), where everyone just uses their first name.
- flast[at]company.com — common at larger, more traditional companies (finance, consulting, some enterprise software) that adopted a formatting convention early and never changed it.
A pattern usually holds across the whole company once it is set, which is the detail that makes this workable at all. If you can find one real email address from that company anywhere public — a press release with a "media contact," a GitHub commit, a conference speaker bio — you can usually infer the pattern for everyone else at the company, including the hiring manager whose email is not published anywhere.
Guessing is not the same as knowing
Here is the part almost everyone skips: a guessed email address, even a well-reasoned one, is still a guess. Sending to a wrong guess doesn't just waste the email — often it produces nothing (a silent drop) rather than an obvious bounce, so you think you reached someone when you didn't, and you never follow up because you assume they read it and ignored you.
SMTP verification checks whether a mail server will actually accept a message for that address without sending anything to the recipient, so you find out before you hit send instead of after. This is the difference between "this email format is probably right" and "this exact address exists." Hesper builds this verification step into the same flow that finds the domain and guesses the pattern, so a name goes to a hiring manager's email address you know is real, not one you're hoping is real.
What to actually send
The subject line and first line matter more than anything else in the message, because they decide whether the email gets opened at all versus archived on sight. A subject like "Application for Marketing Role" reads as a form letter before it's even opened. A subject like "Quick question about the growth team" reads as a person.
The body should do three things in under 150 words: say specifically why you're writing to this person and not a generic recruiter inbox, reference something real about the team or the company (a product launch, a specific project, something from their own LinkedIn post — not "I love your company's mission"), and ask for something small. "Do you have 15 minutes this week" gets answered far more often than "I'd love to be considered for any open roles," because the first is a specific, low-cost yes and the second is an open-ended commitment.
A useful benchmark: cold outreach that is generic and mass-sent tends to see reply rates in the low single digits. Outreach that is personalized to a specific person, a specific team, and a specific reason for reaching out routinely sees reply rates several times higher, because the recipient can tell in the first sentence whether the sender did any homework. The gap isn't about volume. It's about whether the email reads like it was written for one person.
Why most people quit before this compounds
The uncomfortable part of cold email is that most messages, even good ones, don't get a reply. That's true of every channel, not just email — most job seekers who rely purely on networking and referrals face the same math, just with fewer attempts because sending twenty personalized LinkedIn messages a day is much slower than sending twenty verified emails a day. The people who actually land the introduction are usually the ones who kept the volume up long enough for the odds to catch up with them — the same case The Value of Networking makes about networking generally.
The mechanical parts of this — finding the name, guessing the pattern, checking whether the guess is real — are exactly the parts that are tedious enough that most people do them once, get a bounce, and stop. Automating just that part, so a job seeker can spend their time on the fifteen emails that matter instead of the domain-hunting and pattern-guessing behind each one, is the entire reason hespercareers.com exists.
If you're at the point of building a list of specific people to reach at specific companies, that's the workflow worth setting up at hespercareers.com before you send the first message, not after the tenth bounce.
No comments yet.