[No.128] 359 HN Hires — Claude Code Portfolio Practical Pack
In the June 2026 secondary analysis, posts on the Hacker News "Who is Hiring?" thread were organized as 359, the lowest level since 2015.
On the other hand, Refolk analysis reports that the remaining JDs increasingly name-drop Claude Code, Cursor, and Codex, and include descriptions of the "directs an agent" type.
A decrease in the number of posts does not mean the market has disappeared; it is worth reading as a phase where the density of surviving JDs has increased.
This article is a deep dive compiled as copy-paste assets to ensure you don't end on a pessimistic note, but rather add one line of achievement "made with Claude Code" to your GitHub README and submit one PR by the weekend.
What this article includes
How to read the reports — A two-sided organization of the 359 HN minimum and AI-native JD density
3-element framework for agent evidence — A model for making "what you had it build" more valuable than your resume
README achievement one-liner template — How to write about using Claude Code / Cursor
Weekend PR script — Steps to release small features by directing an agent
JD reading checklist — How to distinguish between named tools and "directs an agent"
Portfolio self-assessment sheet — Narrowing down to one weakness this week
30-day roadmap — From README to PR to interview talking points
What you can take away from this article
The sharp drop in HN hiring posts is organized in secondary reports not as the disappearance of all seats, but as a signal that the remaining JDs have shifted toward senior + AI-native roles. There is also a general theory that LinkedIn skill sections lag about 12 months behind JDs, so it is more practical to accumulate evidence in READMEs and PRs first.
One move to try this week: Add "one line of achievement made with Claude Code (or Cursor)" to the top of your GitHub README (copy and fill in the template below).
What is happening — 359 HN posts and changes in JDs
Refolk's analysis article provides the following organization.
Number of posts
Secondary reports state there were 359 posts in the June 2026 HN "Who is Hiring?" thread, the lowest since 2015.
JD content
Analysis shows an increase in the explicit mention of Claude Code, Cursor, and Codex in remaining job openings, as well as an increase in "directs an agent" type descriptions.
Gap with skill sections
The general theory is that LinkedIn skills lag about 12 months behind JDs (not a personal guarantee).
The report is about the entire thread. There is no guarantee your application will pass. What you should take away is the direction that evidence of what you had an agent build is becoming a currency.
3-element framework for agent evidence
1. Specify the tool name
Change 'Used AI' to 'Implemented ( ) and submitted a PR using Claude Code / Cursor'.
2. Include command verbs
Change 'Wrote' to 'Directed the agent through prompt design, iterative refinement, and test instructions'.
3. State the result in one line
Place Before/After or a PR link at the beginning of the README.
Common Misconceptions and Rebuttals
Misconception 1: '359 hires = The hiring market is over'
Rebuttal: Secondary analysis shows a decrease in volume alongside an increase in JD density. The argument is that it is not disappearing.
Misconception 2: 'A resume with only Python is enough'
Rebuttal: The pattern shown in the plot suggests that named tools and agent direction are what remain in JDs.
Misconception 3: 'Just touching Copilot is enough to meet named requirements'
Rebuttal: JDs are increasingly requiring results and PRs. A one-line README + a weekend PR is the minimum cost.
README One-Line Result Template (For Copying)
Paste this directly under the project overview in your repository README and fill in the parentheses.
One-line result (Claude Code version)
This feature was designed and implemented with Claude Code, and (e.g., added authorization middleware) was completed up to PR # ( ). (Time required: 2 hours on the weekend)
One-line result (Cursor version)
Cursor Directed the agent to reduce ( ) to (e.g., 3 days of manual estimation to 6 hours). The diff is in PR # ( ).
One-line supplement (Optional)
Verification performed by human: (e.g., added 12 unit tests, 1 security review).
Definition of done: The above is included within the first 3 lines of the README.
Weekend PR Script (One small feature)
How to choose a topic
A small improvement to a repository close to production (adding logs, adding tests, 1 CLI command)
Within a scope that does not violate confidentiality or contracts
Step 1 — Fix requirements in one sentence
"Add ( ) to ( ). Completion criteria is ( )."
Step 2 — Agent session
Pass the above requirements to Claude Code or Cursor
Read the generated diff yourself and run tests
For unclear points, give correction instructions to the agent (note the command log)
Step 3 — PR body template
Overview: Added ( ).
AI Usage: First draft generated with Claude Code / Cursor. Human performed (test/review items).
Risks: ( ).
Step 4 — README update
Add the above "1-line achievement template" to the README.
Definition of Done: One merged or open PR exists.
JD Reading Checklist (for HN / Overseas JDs)
Named tools — Is Claude Code / Cursor / Codex mentioned in the text?
Command verbs — Are words like directs, orchestrates, agents, etc. present?
Seniority — Check the lower limit of years of experience
Deliverables — Requirements like portfolio / GitHub / shipped, etc.
Your README — Is there a line corresponding to 1-4 above?
1-minute interview version (3 lines)
My understanding is that while hiring posts have decreased in HN analysis, AI-native JDs remain.
I used Claude Code / Cursor at ( ) and submitted up to PR # ( ).
This experience is close to the ( ) requirements in your company's JD.
Definition of Done: 5 items on the checklist are Yes.
30-Day Roadmap
Week 1 — Visualization
Add one line of achievement to README
Definition of Done: One screenshot of the public repository README
Week 2 — Evidence
One PR over the weekend (using the script above)
Definition of Done: PR URL can be retrieved
Week 3 — JD Alignment
Save 5 posts on HN / LinkedIn and self-score using the checklist
Definition of Done: Missing items narrowed down to one
Week 4 — Articulation
Speak the 1-minute interview version aloud and edit the README line just once
Definition of Done: Draft for the next application is finalized
Usage by Persona
SWE job hunting — The 1-line README and weekend PR are top priority. GitHub first over the resume skills section.
Currently employed — One PR in an internal OSS or permitted repository. Can be used as a concrete example of 'agent orchestration' in promotion/transfer interviews.
Freelance — Port a one-line README-style achievement into your proposal. This aligns with the trend where clients view experience with specific tools the same way as a job description.
Relationship with short-form videos
Short 0128 uses the hook of a [sharp decline] to convey the 359 HN posts and Claude Code-specific job descriptions in one go. The video is an overview, while this article is for saving the one-line README, weekend PR, JD check, and 30-day strategy. Start with the first line of your README this week.
Reference
Secondary report (Refolk, June 2026 HN 'Who is Hiring?' analysis). 359 posts is the lowest since 2015. Remaining JDs increasingly specify Claude Code, Cursor, and Codex, with a rise in agent-orchestration roles. The general consensus is that LinkedIn skills lag behind JDs by about 12 months. This is not a guarantee for individuals or companies.
Disclaimer
This article is a summary based on secondary reporting and a template for general portfolio and application activities. The number of HN posts and JD trends are a compilation of analysis and reporting and do not guarantee your employment. Please modify the README and PR body to match the facts and use them within the scope that does not violate confidentiality, contracts, or internal company policies.
Edo Tech Kawaraban — Survival Strategy in the AI Era