How to Contact Engineering Managers Directly

Send a LinkedIn connection request with a specific note — not InMail spam

LinkedIn caps connection notes at 300 characters, but data on tens of thousands of invites shows notes between 120–180 characters get accepted more often than ones that use the full limit. Skip the generic "I'd love to connect" — name the specific thing you're referencing: a post they wrote, a talk they gave, or a technical decision their team made public. If you're not connected, InMail is an option, but most plans only grant 5–15 InMail credits a month, so treat each one as precious and specific, not a mass-blast tool.

Comment thoughtfully on their technical blog posts or conference talks

Engineering managers who write or speak publicly can tell the difference between "great post!" and someone who actually engaged with the argument. Leave a comment (or reply on X/Twitter) that adds a counterpoint, a related resource, or a question about an edge case in their design. This puts your name in front of them multiple times before you ever ask for anything — which is what makes the eventual outreach feel earned rather than cold.

Contribute to their company's open-source repo and engage the maintainers

Pick a small, well-scoped issue first — a bug fix, a docs improvement, a test — to learn the codebase and its review norms before attempting something bigger. Join the project's Discord/Slack or GitHub Discussions and participate before you need something. Companies have hired contributors specifically because a real PR history removes the guesswork of an interview: they've already seen your code, your communication style, and how you handle review feedback.

Show up where they speak — meetups, conferences, local tech events

Engineering managers who speak at meetups or conferences are explicitly making themselves available for a hallway conversation afterward. Prepare one specific, well-informed question about their talk — not "are you hiring?" Follow up afterward by referencing the exact conversation you had, not a generic "great meeting you." In-person context is the single hardest thing to fake, which is exactly why it works.

Get a warm intro through a mutual connection on GitHub, X, or LinkedIn

Check who you already know that follows, has starred the same repos as, or has publicly interacted with the EM you're trying to reach — a former colleague, a college senior, a fellow contributor. A two-line intro ("X asked me to connect you two — she's shipped similar infra work") converts far better than a cold message, because the EM is borrowing trust from someone they already know.

Cold email with a specific technical observation, not "I'm interested in opportunities"

The engineers who get replies keep it short — roughly 100–150 words, 4–5 lines — and lead with a specific observation about the product: a bug you noticed, a performance characteristic, an architecture choice you'd ask about. End with one clear, low-friction ask (a 15-minute call, a specific question) instead of a vague "let's connect." Most replies to cold outreach don't come from the first email — plan on two or three short, polite follow-ups spaced a few days apart before you conclude there's no interest.

Use engineering-specific communities — Slack groups, Discord servers, HN's hiring thread

Hacker News still runs its monthly "Ask HN: Who is hiring?" thread — company reps post roles directly and are expected to reply to comments, which makes it one of the few channels where you can publicly ask a hiring engineer a question and get a direct, unfiltered answer. Beyond HN, niche Slack and Discord communities built around a specific language, framework, or industry vertical often have dedicated #jobs channels where founders and EMs post and respond directly, without a recruiter layer in between.

Apply through a platform that routes straight to the EM's dashboard — like Switchly

Every tactic above depends on finding the right person and hoping they have time to respond to a stranger. Switchly removes that dependency for the application itself: upload your resume, our AI parses your skills and matches you to open roles, and your application lands directly in the hiring engineering manager's or founder's dashboard — no recruiter pre-screen, no ATS keyword filter deciding whether a human ever sees it. Use it alongside the outreach tactics above, not instead of them — a warm comment or intro plus a direct application is stronger than either alone.

Is it OK to message an engineering manager directly instead of applying through HR?

Yes. Most engineering managers who post jobs want to see strong candidates as early as possible — a well-informed, specific message is rarely unwelcome. What backfires is a generic, mass-copied message with no context. Keep it short, specific, and about their actual work, not a templated pitch.

How many times should I follow up after a cold email or LinkedIn message?

Two to three follow-ups spaced a few days to a week apart is standard practice. A large share of replies to cold outreach come from a follow-up rather than the first message, so don't treat silence after one attempt as a final answer — but stop after three if there's still no response.

Does commenting on someone's blog or talk actually help, or is it just noise?

It helps only if the comment adds something — a counterpoint, a related resource, or a genuine question about a tradeoff they made. A specific, engaged comment is memorable precisely because most comments on technical content are low-effort. Do this multiple times before you ever ask the person for anything.

Is the Hacker News "Who is hiring" thread still worth using?

Yes — it runs every month with company representatives posting roles and answering comments directly, without a recruiter filter. It's a good channel for asking a hiring engineer a direct question in public, though volume varies a lot by month and role type.

How is applying through Switchly different from these outreach tactics?

The tactics above are about getting a person's attention before you've formally applied. Switchly changes what happens after you apply: your AI-parsed profile goes straight to the engineering manager's dashboard, ranked against other applicants, with no recruiter pre-screen or ATS keyword filter in between. It's not a replacement for building a relationship — it's a way to make sure the formal application itself doesn't get lost.

What if the engineering manager doesn't respond at all?

Most outreach — even good outreach — doesn't get a response, and that's normal, not a signal you did something wrong. Don't burn a relationship by over-following-up beyond three attempts. Move on to the next role, and consider applying through a channel like Switchly where a lack of a personal reply doesn't mean your application was never seen.