HN Debrief

Please don't spam people looking for employment. It's just cruel

  • AI
  • Careers
  • Startups
  • Developer Tools
  • Security

The post is a plea from someone unemployed for months who shared their background in a public "Who Wants to Be Hired" thread and then got what looked like a promising response, only to discover it was a canned pitch for LLM integration services. The point was not that one bad email is catastrophic. It is that when you are under real financial and emotional strain, every fake lead extracts attention and hope you do not have to spare.

If you use public hiring threads, treat any exposed email as burned and isolate it with aliases, filters, or throwaway inboxes. More broadly, do not rely on public inbound for recruiting or job search anymore. Warm intros and vetted channels are now doing the real work.

Discussion mood

Strongly negative and weary. People were sympathetic to the author and angry that AI makes already-bad outreach cheaper, more targeted, and more emotionally draining. The strongest frustration was not with generic spam alone but with predatory job-search scams and the collapse of trust in public hiring channels.

Key insights

  1. 01

    Job-search spam now shades into criminal scams

    What starts as annoying outreach can quickly become identity laundering, sanctions evasion, or malware delivery. Multiple people described offers to let someone else do the coding while you front client meetings and accounts, or to hand over remote access and payment rails. One commenter linked a Department of Justice case showing this can end in prison, not just a bad freelance gig. That changes the frame from inbox hygiene to legal and operational risk.

    Treat unsolicited work-sharing, interview-assistance, or account-rental offers as hostile by default. Do not lend your identity, laptop, bank account, PayPal, or Upwork account to anyone promising a revenue split.

      Attribution:
    • satvikpendem #1
    • DamnInteresting #1
    • goolz #1
    • rl1987 #1
    • csomar #1
    • moomin #1
  2. 02

    Public hiring threads are losing their utility

    Several people said they have stopped posting in open hiring threads because the legitimate response rate no longer justifies the spam load. The damage cuts both ways. Employers reported being buried under generated applications and sales junk, while job seekers said real progress now comes from referrals and direct network intros rather than public inboxes. That makes these threads less a market and more a scraper feed.

    Use public hiring posts as a side channel, not your core funnel. Put most effort into referrals, direct outreach to known companies, and communities with some access control.

      Attribution:
    • gloosx #1
    • bityard #1
    • unforswearing #1
    • devy #1
    • mildzebrataste #1
  3. 03

    Third-party recruiters are uneven but not useless

    The loud anti-recruiter sentiment got corrected by people who hire through agencies and by someone who ran a recruitment firm. The useful distinction is not "recruiter" versus "no recruiter". It is whether the recruiter has an actual client relationship and enough leverage to move your application, give compensation guidance, and get feedback a cold applicant will never see. In a market clogged with AI applications, curated pipelines still have value.

    Do not dismiss recruiters wholesale. Test whether they can name the company early, explain their mandate, and show they can get you to a real hiring manager instead of farming your resume.

      Attribution:
    • dheera #1
    • dsr_ #1
    • petesergeant #1
    • toomuchtodo #1
    • rgbrgb #1
  4. 04

    Hiding email in profiles only delays scraping

    One workaround was to keep your email out of the post body and leave it in your profile or linked site, on the theory that lazy scrapers only parse thread text. Others said that window is closing. Recruiting tools are already scraping profiles, GitHub commit addresses, and other public traces, then matching them back to HN activity. The tactic may still reduce volume today, but it is not durable protection.

    Assume any email tied to a public identity will eventually be harvested. Rely on aliases and revocable addresses, not obscurity, when posting publicly.

      Attribution:
    • codeforafrica #1 #2
    • neilv #1
    • danillonunes #1
    • ibejoeb #1
  5. 05

    Write outreach with the ask first

    One concrete communication fix stood out. Start with the bottom line up front. Say exactly what you want, what role this is about, or why the message is relevant before any pitch language. In this context, the sin was not just automation. It was making recipients spend emotional energy decoding whether a message is real. Clear subject lines, company names, and compensation ranges do more than etiquette here. They let people triage without getting baited by false hope.

    If you send recruiting or sales outreach, front-load company, role, and purpose in the first line. If you receive outreach, filter aggressively against messages that bury the ask.

      Attribution:
    • runjake #1
    • moralestapia #1
    • ilreb #1

Against the grain

  1. 01

    AI did not invent this, it scaled it

    The older hands pushed back on the idea that this is a wholly new pathology. They argued that semi-personalized form-letter outreach has been around for decades and the current wave is structurally the same. The real change is volume and slightly better targeting. That matters because it suggests the fix is not waiting for AI etiquette to improve. It is rebuilding channel defenses for a spam problem that keeps getting cheaper.

    Do not frame this as a temporary LLM manners issue. Build durable filters, aliases, and posting practices that assume outreach automation will keep improving.

      Attribution:
    • chrismorgan #1
    • HeyLaughingBoy #1
    • insane_dreamer #1
  2. 02

    Some of this spam is just bad targeting

    A few people read the original email less as cruelty aimed at the unemployed and more as dumb automation scraping the wrong thread. The likely failure mode was a bot that confused "Who Wants to Be Hired" with "Who's Hiring" and blasted anyone it found. That does not excuse the behavior, but it does change the lesson. A lot of harm is coming from careless systems, not only malicious ones.

    When you build outbound automation, test targeting and negative cases before sending anything at scale. A simple thread or intent mix-up can turn routine growth spam into reputational damage.

      Attribution:
    • baobabKoodaa #1
    • happytoexplain #1
  3. 03

    The real driver is a broken market

    A smaller set of comments put less blame on individual spammers and more on the incentives around them. In that view, weak hiring markets, collapsed trust in public channels, and cheap automation combine to push everyone into worse behavior. The point is not to excuse spam. It is to recognize that more desperate sellers and applicants will keep reaching for these tools as long as normal matching channels fail.

    Expect outreach quality to stay poor while hiring remains tight and public channels stay open to automation. Budget more time for trust-building and verification at the top of every hiring interaction.

      Attribution:
    • varispeed #1
    • rvz #1
  4. 04

    Resilience matters even when the spam is real

    A few commenters rejected the moral framing and said the internet will stay hostile, so job seekers need thicker skin and better expectation management. That landed badly, but it surfaces a practical truth. You cannot make open channels humane by asking. Even if the sender is wrong, emotional triage is now part of using public job markets.

    Set up your search process to protect your attention, not just your inbox. Separate public-facing addresses from personal mail and batch-review messages so random outreach does not dictate your mood.

      Attribution:
    • dostick #1
    • notsure357 #1
    • torben-friis #1

In plain english

Department of Justice
The United States federal department responsible for law enforcement and prosecution of federal crimes.
GitHub
A platform for hosting code and collaborating on software projects.
LLM
Large language model, a machine learning system trained on large amounts of text that can generate and analyze language and code.
Upwork
An online freelancing marketplace where clients hire contractors for projects.

Reference links

Scam and security references

Spam examples and tools

Books and writing frameworks

  • Rejection Proof
    Mentioned as a book recommendation about dealing with rejection, in a comment arguing for thicker skin.

Historical and cultural references

  • RMS vs. Doctor
    Referenced during a side discussion about calling software a child and broader norms around personal announcements.