Ask HN: Who is hiring? (June 2026)

Hacker News Discussion ↗

Overview of roles and sectors

  • Thread is dominated by hiring posts across many domains: AI/LLMs, healthcare, gov/fintech, infra/SRE, devtools, robotics, quantum, defense, logistics, education, and proptech.
  • Roles span IC and leadership: full‑stack, backend, infra, ML/AI, data, product, design, GTM, and founding/first‑engineer seats.
  • Many companies highlight being profitable or having strong traction (ARR, unicorn valuations, series funding) and emphasize “real problems” vs. demos.

AI and “agentic” engineering expectations

  • Strong trend toward “AI‑native” or “agentic” roles: building coding agents, multi‑agent systems, workflow/orchestration, RAG, evals, and AI copilots in production.
  • Several postings explicitly require daily use of AI IDEs (Claude Code, Cursor, etc.) and expect engineers to treat agents as force multipliers, not side experiments.
  • Some companies take the opposite stance, explicitly de‑emphasizing AI‑generated code and prioritizing full understanding of systems.

Remote, location, and visa constraints

  • Many postings are remote but often constrained: “US only”, specific time zones, or contractor‑only in parts of Europe.
  • Comments highlight frustration with geo filters (e.g., automatic rejection based on location) and mixed models (onsite + partial remote).
  • A few roles offer relocation and visa sponsorship, but most do not.

Applicant experiences and frustrations

  • Commenters report being rejected early (sometimes attributing it to non‑technical factors like a stutter) despite strong technical fit.
  • Complaints about onerous application funnels: forced app installs, mandatory video submissions, or long multi‑round interview processes that feel performative.
  • Candidates mention ghosting, fake or cancelled roles mid‑process, and lack of feedback as common pain points.

Hiring‑side challenges and spam

  • One employer describes pulling back from posting due to a surge of spam and fraudulent applicants (impersonated LinkedIn profiles, fake resumes).
  • Others corroborate seeing extensive spam from recruiters and candidates; note that inbound hiring and LinkedIn are increasingly polluted.
  • Some argue robust verification and better processes can still surface good candidates, but acknowledge signal‑to‑noise is deteriorating.

Product and posting quality feedback

  • Readers point out broken links (404s, 500s) and confusing application flows on some career sites.
  • UX feedback is mixed: some sites are praised as “droolworthy,” while others are criticized for basic usability issues (scrolling, resizing).
  • A few note small inconsistencies (e.g., unclear working hours, missing “LLM honeytrap” mentioned in instructions), reinforcing that polish on postings and sites matters.