Insights from over 10,000 comments on "Ask HN: Who Is Hiring" using GPT-4o
An analysis of over 10,000 Hacker News “Ask HN: Who Is Hiring?” comments using GPT‑4o reveals which programming languages, JavaScript tools, and databases are most in demand, with React and web-focused stacks standing out. Commenters probe the limits of these findings, noting HN’s bias compared to mainstream job boards, the ambiguity of “remote” roles, and the presence of compliance-only or pre-filled postings. Much of the debate centers on whether large language models are an appropriate and cost‑effective tool for this kind of labor market analysis versus traditional NLP or simpler keyword methods.
Overall reception
- Many commenters praise the analysis, visualizations, and creative use of GPT‑4o, calling it a fun and insightful “Sunday project.”
- Some emphasize it’s exploratory rather than production-grade; doing the same at scale with paid LLM APIs is considered impractical.
React, JS frameworks, and tech demand
- Several are surprised by how dominant React appears; some joke it looks like a “red giant” ready to peak.
- Confusion/critique around mixing true frameworks (e.g., Angular, Next.js) with libraries (React, Redux) and even runtimes (Node.js) in the same “frameworks” chart.
- Redux’s prominence surprises people given its reputation as “old” compared to Zustand/Jotai, but others note legacy codebases still need Redux skills.
- Multiple nitpicks about duplicate or split labels (React Native vs React‑Native, Node.js vs NodeJS, Vue.js vs VueJS, etc.).
Representativeness of HN job data
- Several note HN jobs are skewed toward web dev, deeper systems/infra, and away from domains like gaming and IT.
- Comparisons to LinkedIn/Indeed suggest HN is not representative of overall language popularity (e.g., Rust vs Go).
- Some argue HN “Who’s Hiring” posts sometimes function as marketing/compliance posts with no real hiring intent; others share success stories of actually getting hired.
Data collection & methodology
- Multiple people point out the author could have used the HN API or existing public datasets instead of Selenium+Google.
- Suggestions to use named-entity recognition (NER) and predefined enums to normalize technologies and remote categories.
- Some argue smaller/cheaper models or local models (e.g., via Ollama) would likely have worked for extraction; others say paying for a strong model to avoid edge-case errors is worth it.
Visualizations & chart design
- Positive feedback for the 3D/bubble visualizations, but many advocate for simpler tables or histograms.
- Debate about stacked vs side‑by‑side bar charts; stacked is good for totals, but makes comparison of subcomponents harder.
Remote work & job market nuance
- Commenters note “remote” is often actually hybrid or geographically constrained; propose more granular categories (city, country, timezone, global remote).
- Some describe shifts in applicant volume (e.g., sudden surges in candidates) and debate macro explanations, including interest rates, layoffs, and trustworthiness of official job statistics.