Ask HN: Who is hiring? (July 2025)

Hiring landscape & role types

  • Wide range of roles across startup and mid-sized companies: backend, full‑stack, frontend, infra/SRE, ML/AI, DevOps, product, and design.
  • Strong concentration in:
    • AI/LLM and “agentic” systems (evaluation, orchestration, infra, safety).
    • Devtools and infrastructure (CI/CD, observability, databases, cloud platforms, code editors).
    • Fintech, healthcare/healthtech, industrial/robotics, and security.
  • Many teams emphasize small, senior, “founding” or staff-level hires, high autonomy, and direct product ownership.

Tech stacks and patterns

  • Common stacks: TypeScript/React/Next.js, Python (FastAPI/Django), Go, Rust, Node.js, Java, Kotlin, plus heavy Kubernetes, Terraform, and major clouds (AWS, GCP, Azure).
  • Several posts highlight CUDA/embedded, robotics, real-time systems, or high‑scale data (ClickHouse, Snowflake, Postgres, Elasticsearch).
  • AI work often centers on LLM APIs, RAG, agents, eval harnesses, and MLOps; some also mention vision models and multimodal systems.

Remote vs. onsite & eligibility

  • Many roles are “remote but time‑zone bounded” (e.g., US-only, North America, EU/UTC±3).
  • A number of on‑site‑only or hybrid jobs in SF Bay Area, NYC, London, Berlin, Amsterdam, and other hubs; some offer relocation and visa sponsorship, others explicitly do not.
  • Several clarifications about location: some “remote” postings later specify region restrictions; others confirm relocation is required for non‑EU/US applicants.

Candidate experience & hiring practices

  • Multiple candidates comment on:
    • Friction from gated AI video interviews, with concern that they filter out strong candidates who have options.
    • Frustration with lack of salary transparency in some postings; at least one company is asked to add ranges.
    • Ghosting or generic rejections despite a new guideline that posters should be “committed to responding to applicants”; there’s discussion about how to enforce this.
  • A few companies quickly fix broken links or mistaken “job closed” flags in response to comments.
  • Some job posters explicitly preference or require hands‑on coding (even in leadership roles), and several discourage agency/recruiter contact.