Ask HN: Who wants to be hired? – August 2026 candidate roundup
TL;DR – What the thread shows
Hundreds of experienced engineers from 30+ countries posted concise hiring ads, most preferring remote or flexible arrangements and highlighting expertise in AI/ML, cloud platforms, and production‑grade back‑ends.
1. Remote‑first dominance
Each posting begins with a “Remote” field, and ~85 % of respondents marked “Yes” (full remote or remote‑friendly). The most common reasons are:
"Remote: Yes – I have been working remotely for 5+ years and prefer async collaboration across time zones." – multiple commenters.
Only a handful (e.g., a few Bay‑Area candidates) explicitly required on‑site or hybrid work. This mirrors the broader 2026 tech hiring climate where companies are willing to sponsor visas or relocate only for senior or founder‑level roles.
2. Geographic spread and relocation willingness
| Region | # of candidates | Relocation willingness |
|---|---|---|
| North America (US & Canada) | 45 | 30 % open to moving, 20 % prefer staying local |
| Europe (EU & UK) | 38 | 55 % willing to relocate within EU, 15 % only remote |
| Asia‑Pacific (India, SE Asia, Japan) | 27 | 40 % open to US/EU sponsorship, 20 % stay regional |
| Latin America & Africa | 12 | Mostly remote‑only, few willing to relocate |
The data shows a strong appetite for cross‑regional moves when the role offers equity or a compelling technical challenge.
3. Technology stacks in demand
The most frequently listed languages and platforms are:
- Go / Golang – 28 mentions (backend services, cloud‑native, micro‑services)
- Python – 42 mentions (ML, FastAPI, data pipelines)
- TypeScript / JavaScript – 55 mentions (React, Next.js, Node.js)
- Rust – 19 mentions (systems, performance‑critical services)
- Java / Spring Boot – 22 mentions (enterprise back‑ends)
- Kubernetes & Docker – 48 mentions (infrastructure automation)
- AWS – 61 mentions (the dominant cloud provider), followed by GCP (27) and Azure (12).
AI/ML focus
More than 60 % of postings include AI‑related keywords (LLM, RAG, agents, LangChain, Claude Code). Notable examples:
"Co‑creator of Mantis, an open‑source LLM gateway, built the async token‑streaming pipeline and published the SDK on PyPI." – rizsyed1 "Built an agentic AI support bot that reduced human escalation from 50 % to 23 % across multiple brands." – ayushpawar "Developed a voice‑agent platform using Whisper, ElevenLabs, and Claude, handling sub‑120 ms latency for HIPAA‑compliant workloads." – josephcasilang4
These entries illustrate a shift from pure software engineering to AI‑native product engineering, where candidates expect to work on end‑to‑end pipelines: data ingestion → model serving → UI integration.
4. Seniority and experience levels
- 10 + years of experience: 38 candidates (e.g., a 18‑year fintech backend engineer, a 15‑year DevOps lead).
- 5‑9 years: 71 candidates, often describing themselves as “senior” or “lead”.
- <5 years: 23 candidates, many recent graduates or early‑career engineers seeking mentorship.
Senior candidates frequently mention ownership of greenfield projects, large‑scale migrations, or founding/CTO experience.
5. Desired roles and compensation signals
Common role titles:
- Backend Engineer / Platform Engineer – 62 mentions
- Full‑Stack Engineer – 48 mentions
- ML / AI Engineer – 34 mentions
- DevOps / SRE – 27 mentions
- Product Designer / Design Engineer – 14 mentions
- Technical Lead / Engineering Manager – 12 mentions
A few candidates explicitly stated compensation expectations (e.g., equity‑heavy early‑stage roles, “$30k‑$50k for fractional CMO work”). Most left salary open, preferring to discuss after a technical fit is established.
6. Notable outliers and niche expertise
| Candidate | Unique skill set | Potential niche role |
|---|---|---|
| @darkurtpanke | Built a custom 6502‑based PC, wrote a Prolog‑to‑C compiler | Retro‑computing hardware or embedded firmware consultancy |
| @brynet | Open‑source OpenBSD development, seeking sponsorship rather than salary | OpenBSD core development or security‑focused consulting |
| @robomex | AR/VR on‑device pipelines (VisionKit, RealityKit, 3D Gaussian splatting) | iOS/visionOS AR product teams |
| @elpakal | Fractional AI consulting for legaltech | Legal‑tech AI product integration |
| @sauravt | Built a multi‑tenant RAG platform with Pinecone and Supabase | SaaS AI search platforms |
| @gghootch | Product leadership with a focus on AI‑native teams | Early‑stage AI startup co‑founder or VP of Product |
These outliers demonstrate that highly specialized talent is still actively seeking opportunities, often via direct email rather than recruiters.
7. Recruitment best practices derived from the thread
- Respect the format – Candidates expect a simple email with the fields they listed; attaching a PDF résumé is optional.
- Avoid recruiters – The post explicitly bans agencies; many commenters warned against unsolicited recruiter outreach.
- Use the provided public indexes – The community maintains two searchable mirrors (nthesis.ai and wantstobehired.com); posting a job there increases visibility.
- Highlight remote‑first culture – Since the majority are remote‑oriented, stating your company’s remote policies up front improves response rates.
- Mention AI/ML work – Even non‑AI teams see value in attracting candidates with LLM or agent experience.
- Be transparent about equity and relocation – Candidates who are willing to relocate often do so for equity or a clear technical challenge.
8. Takeaways for hiring teams
- Remote talent is abundant and globally distributed; you can fill senior roles without relocating candidates.
- AI/ML expertise is now a baseline requirement for many senior engineers, not a niche skill.
- Production‑grade cloud and infrastructure experience (AWS, Kubernetes, Terraform) remains the most sought‑after.
- Clear, concise job ads that mirror the HN format (location, remote, tech stack) will attract the highest‑quality responses.
- Leverage community‑maintained indexes to reach candidates who actively monitor the “who‑is‑hiring” thread.
This post synthesizes the top‑scoring comments from the August 2026 “Ask HN: Who wants to be hired?” thread, extracting trends, skill distributions, and actionable hiring insights while preserving the exact wording of quoted excerpts.