// FIELD NOTE

Cold outreach when the ATS is a black box

May 24, 2026 · 6 min read · Aayush Baniya

About one in eight of my applications resulted in an interview when I went through the ATS. About one in three did when I sent a thoughtful cold message to someone on the team. The numbers are stark — but only if the message is right.

Who to message

Best target, in order:

The hiring manager.Usually the engineering manager or director one level above the role. Find them via the company's engineering blog (look for the most recent post in your area), the company's GitHub org (look for the maintainer of relevant repos), or LinkedIn (filter by title and team).
An IC on the team.Second-best. They don't make the hire, but a referral from them carries weight. Pick someone whose work you can specifically reference.
A recruiter on the company's talent team. Last resort. They get hundreds of cold messages and triage by gut. Less effective than the other two.

Don't message the CEO. Don't message someone five layers above the role. They'll forward you to a recruiter and you'll be in worse position than if you'd messaged the recruiter directly.

The channel

LinkedIn DM if they're open to it (check “Open to messages” or whether their profile shows “Open to work”-style indicators that suggest they're responsive). Email if you can find it — guess the format using the company's domain conventions and verify with a tool like Hunter. Don't use InMail unless you have credits to burn; the open rate is terrible because every recruiter on LinkedIn floods the same inbox.

The message

Three sentences. No more.

One specific referenceto their work. A talk they gave, a paper they co-authored, a feature they shipped, a line in their engineering blog. Specific enough that they couldn't mistake the message for a template.
One sentenceon why you'd be a fit for the role they're hiring for. Reference the specific role, with a number from your background.
One sentencewith a clear, low-effort ask. “Could you point me to the right person to talk to?” or “Would a 15-minute conversation be possible?”

Example:

Saw your post on cutting Aurora costs by switching the audit-log table to TimescaleDB — the part on compression policies was the most useful thing I've read on Postgres ops this year. I noticed you're hiring a backend engineer for the platform team; I led a similar migration at Acme last year that cut our DB spend by 38%. Open to a 15-minute call to see if there's mutual fit?

Three sentences, 65 words, doesn't feel automated. Response rates on this format run 25-35% in my experience.

What kills the message

Length. Five paragraphs and a CV attached: instant skip.
The phrase “I came across your profile.” Recruiter-speak. Triggers spam pattern-match.
Asking for a job directly.“Can you refer me?” before establishing any context is too much, too fast. Ask for a conversation; the referral comes if the conversation goes well.
Vague specifics.“I really admire the work your team does.” — admire what, specifically? If you can't name the thing, don't fake it.
Multiple asks.“Could you refer me, share advice, and pass my resume to the team?” — pick one.

Timing

Tuesday or Wednesday morning, 9-10am their local time. Avoid Friday afternoons, Monday before 11am, and any time after 6pm. Response rates drop materially at the edges of the week.

Don't follow up more than once. If they didn't respond within 10 days, they're not going to. One follow-up at the 7-10 day mark, terse: “circling back in case the message got buried.” That's it.

How much time to spend

80/20 rule applies inversely. Spend 20% of your search time on cold outreach to 5-10 companies you'd really love to work for. Spend 80% on volume through the ATS for the broad market. Cold outreach is high per-attempt yield but low scale — five thoughtful messages a week, not fifty.

Who to message

Best target, in order:

The hiring manager.Usually the engineering manager or director one level above the role. Find them via the company's engineering blog (look for the most recent post in your area), the company's GitHub org (look for the maintainer of relevant repos), or LinkedIn (filter by title and team).

An IC on the team.Second-best. They don't make the hire, but a referral from them carries weight. Pick someone whose work you can specifically reference.

A recruiter on the company's talent team. Last resort. They get hundreds of cold messages and triage by gut. Less effective than the other two.

Don't message the CEO. Don't message someone five layers above the role. They'll forward you to a recruiter and you'll be in worse position than if you'd messaged the recruiter directly.

The channel

The message

Three sentences. No more.

One specific referenceto their work. A talk they gave, a paper they co-authored, a feature they shipped, a line in their engineering blog. Specific enough that they couldn't mistake the message for a template.

One sentenceon why you'd be a fit for the role they're hiring for. Reference the specific role, with a number from your background.

One sentencewith a clear, low-effort ask. “Could you point me to the right person to talk to?” or “Would a 15-minute conversation be possible?”

Example:

Saw your post on cutting Aurora costs by switching the audit-log table to TimescaleDB — the part on compression policies was the most useful thing I've read on Postgres ops this year. I noticed you're hiring a backend engineer for the platform team; I led a similar migration at Acme last year that cut our DB spend by 38%. Open to a 15-minute call to see if there's mutual fit?

Three sentences, 65 words, doesn't feel automated. Response rates on this format run 25-35% in my experience.

What kills the message

Length. Five paragraphs and a CV attached: instant skip.

The phrase “I came across your profile.” Recruiter-speak. Triggers spam pattern-match.

Asking for a job directly.“Can you refer me?” before establishing any context is too much, too fast. Ask for a conversation; the referral comes if the conversation goes well.

Vague specifics.“I really admire the work your team does.” — admire what, specifically? If you can't name the thing, don't fake it.

Multiple asks.“Could you refer me, share advice, and pass my resume to the team?” — pick one.

Timing

Tuesday or Wednesday morning, 9-10am their local time. Avoid Friday afternoons, Monday before 11am, and any time after 6pm. Response rates drop materially at the edges of the week.

Don't follow up more than once. If they didn't respond within 10 days, they're not going to. One follow-up at the 7-10 day mark, terse: “circling back in case the message got buried.” That's it.