惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - 聂微东
GbyAI
GbyAI
G
Google Developers Blog
大猫的无限游戏
大猫的无限游戏
H
Hackread – Cybersecurity News, Data Breaches, AI and More
博客园 - 叶小钗
A
About on SuperTechFans
M
MIT News - Artificial intelligence
宝玉的分享
宝玉的分享
雷峰网
雷峰网
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Martin Fowler
Martin Fowler
Google DeepMind News
Google DeepMind News
博客园 - Franky
B
Blog RSS Feed
Y
Y Combinator Blog
Stack Overflow Blog
Stack Overflow Blog
MongoDB | Blog
MongoDB | Blog
Last Week in AI
Last Week in AI
T
The Blog of Author Tim Ferriss
The GitHub Blog
The GitHub Blog
S
SegmentFault 最新的问题
罗磊的独立博客
Apple Machine Learning Research
Apple Machine Learning Research

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I Built a Job Description Keyword Extractor (and Here's W...
charlie-morr · 2026-04-29 · via DEV Community

Every job description is a cheat sheet. The hiring manager already told you exactly what they want — it's just buried under corporate filler.

I got tired of manually highlighting keywords in job postings, so I built a tool that does it automatically: Job Description Keyword Extractor. Paste a posting, get categorized keywords. Technical skills, soft skills, tools, certifications — all sorted by how often they appear.

Building it taught me a few things about how ATS systems actually work.

Most resumes fail on keywords, not formatting

Everyone worries about fonts and columns and whether their PDF will parse correctly. That stuff matters, but it's not what kills most applications.

The real filter is keyword matching. ATS systems score resumes based on how many keywords from the job description appear in your resume. Not synonyms. Not related terms. The exact words.

If the posting says "Kubernetes" and your resume says "container orchestration" — that's a miss. If it says "cross-functional collaboration" and you wrote "worked with different teams" — miss again. The machine doesn't understand meaning. It counts matches.

Frequency tells you priority

When a keyword shows up three times in a job description, that's not sloppy writing. That's emphasis. The hiring manager really wants that skill.

My tool highlights these: keywords mentioned 3+ times get green tags, 2 times get yellow. If Python shows up five times and Go shows up once, you know where to focus your resume's real estate.

The categories matter for resume structure

Most people dump all their skills into one section. But job descriptions naturally split into:

  • Technical skills (programming languages, frameworks, concepts)
  • Tools and platforms (Jira, AWS, Figma, Salesforce)
  • Soft skills (leadership, communication, stakeholder management)
  • Certifications (AWS Certified, PMP, specific degrees)

Your resume should mirror this structure. A skills section with 40 random technologies tells the ATS nothing about priority. But "Core Skills: Python, Django, PostgreSQL" followed by "Tools: AWS, Docker, Terraform" maps directly to how the job was written.

What I actually built

The tool runs entirely in your browser. No backend, no API calls, no data collection. You paste text, JavaScript parses it against ~500 known skill/tool patterns, and you get a categorized breakdown.

It's not perfect — natural language is messy, and some keywords are ambiguous ("Go" the language vs. "go" the verb). But for the core use case of "what keywords should I make sure are in my resume" — it works.

The killer feature (for me at least) is the copy button. Extract keywords, copy the list, open your resume, and check them off one by one. Five minutes of work that can make the difference between your application reaching a human or getting filtered out.

The workflow I'd recommend

  1. Find a job you want to apply for
  2. Paste the description into the keyword extractor
  3. Copy the high-priority keywords
  4. Update your resume to include those exact terms (naturally — don't keyword-stuff)
  5. Run it through the ATS checker with the same job description
  6. If your score is below 70%, keep tweaking

This is what targeted applications look like. One resume per job posting, customized for that specific role. More work than spray-and-pray, but the response rate is incomparable.


The tool is at charliemorrison.dev/job-keywords. There's also a resume checker, cover letter generator, and a few others — all free, all browser-based.

Curious what keywords you find in your current target role?