ATS keywords are the words a recruiter types into their search filter: skills, tools, job titles, certifications. There is no secret vocabulary. If the roles you want ask for Kubernetes and your resume says containerization, you will not appear in the search, and that is the entire mechanic. Below is the list by role family, and then the part most keyword posts skip: how to cut it down.
What ATS keywords actually mean
An applicant tracking system is the software recruiters use to collect, parse, search and rank resumes. A keyword is any term that survives that parsing as plain text and can therefore be searched.
That definition has a sharp edge to it. A skill only counts as a keyword if it is readable text. Put “Python” inside a graphic, a skill-bar image, a two-column sidebar or a header, and the software does not have it. You have the skill. Your resume does not.
So when people ask what ATS keywords mean on a resume, the honest answer is boring: they are the ordinary words of your job, in a place the parser can reach.
Why keywords decide whether you appear at all
Applicant tracking systems, and Naukri’s recruiter search, work as filtered databases. A recruiter narrows by skill, experience range, location and notice period, then reads what survives. Your resume is not being judged at that stage. It is being matched, on exact terms, as plain text.
Which means a strong candidate whose skills live inside a graphic is simply absent from the list. Not ranked low. Absent.
The ATS keywords list, by role family
These are the terms that repeat across live Naukri and LinkedIn postings in India for each family. Treat this as the raw pool, not the final resume. The next section cuts it down.
Software engineer, SDE and backend
| Keyword | Why it gets filtered on |
|---|---|
| Java, Python, Go, Node.js, C++ | The primary language filter, usually the first thing a recruiter narrows by |
| Spring Boot, Django, Express, .NET | Framework tells them your stack matches without an interview |
| REST API, GraphQL, gRPC | Signals service work rather than scripting |
| Microservices | Common shorthand for the architecture the team already runs |
| SQL, PostgreSQL, MySQL, MongoDB | Database experience is filtered separately from language |
| Data Structures, Algorithms | Screens for interview readiness at product companies |
| System Design | The senior-versus-mid divider on most JDs |
| Git, CI/CD, Jenkins | Baseline engineering hygiene |
| Docker, Kubernetes | Increasingly a hard filter, not a nice-to-have |
| AWS, Azure, GCP | Named cloud, not “cloud technologies” |
| Unit Testing, JUnit, PyTest | Rarely searched alone, often used to break a tie |
| Agile, Scrum | Process filter, cheap to include if true |
Data analyst and data scientist
| Keyword | Why it gets filtered on |
|---|---|
| SQL | The single most-filtered term in this family, above Python |
| Python, R | Language filter |
| Pandas, NumPy, scikit-learn | Distinguishes hands-on modelling from reporting |
| Power BI, Tableau, Looker | Named BI tool, and companies filter on the one they own |
| Excel, Advanced Excel | Still filtered constantly in India, do not skip it out of pride |
| Data Visualization | Broad, but appears in a majority of JDs |
| Machine Learning, Deep Learning | Separates analyst roles from science roles |
| Statistics, A/B Testing, Hypothesis Testing | Product-analytics filter |
| ETL, Data Pipeline, Airflow | Signals engineering-adjacent work |
| Snowflake, BigQuery, Redshift | Warehouse names, filtered individually |
| NLP, Computer Vision | Only if genuinely yours, these get probed hard |
| Dashboarding, Reporting | Low-value alone, useful in a bullet with a number |
DevOps, cloud and SRE
| Keyword | Why it gets filtered on |
|---|---|
| AWS, Azure, GCP | Named cloud, and the certification names are searched too |
| Kubernetes, Docker | The two terms that define the family |
| Terraform, Ansible, Pulumi | Infrastructure as code, usually a hard requirement |
| CI/CD, Jenkins, GitHub Actions, GitLab CI | Pipeline tooling, filtered by the specific tool |
| Linux, Shell Scripting, Bash | Baseline, and its absence is noticed |
| Monitoring, Prometheus, Grafana, Datadog | Observability stack |
| Site Reliability Engineering, SRE | Title filter as much as a skill filter |
| Networking, Load Balancing, DNS | Appears in infra-heavy JDs |
| Helm, Istio, Service Mesh | Senior-level differentiator |
| Cost Optimization, FinOps | Rising fast in Indian JDs, few resumes carry it |
QA and test automation
| Keyword | Why it gets filtered on |
|---|---|
| Selenium, Cypress, Playwright | The tool filter, and companies search only the one they use |
| Automation Testing, Manual Testing | Recruiters filter these as two different jobs |
| TestNG, JUnit, PyTest | Framework filter |
| API Testing, Postman, RestAssured | Now standard on most QA JDs |
| Test Cases, Test Plan, Test Strategy | Process vocabulary that parses as experience level |
| JIRA, TestRail, Zephyr | Tooling that signals real team process |
| Performance Testing, JMeter, LoadRunner | A distinct sub-family, filtered separately |
| Appium, Mobile Testing | Only include if genuine, it is a narrow pool |
| SDET | Title filter that pays better than “QA Engineer” and is searched separately |
| CI/CD, Jenkins | Increasingly expected of QA, not just engineering |
HR and recruitment
Recruiters searching for recruiters are unusually literal, so titles matter more here than tools. The pool: Talent Acquisition, Recruitment, Technical Recruitment, End-to-End Recruitment, Sourcing, Boolean Search, Stakeholder Management, HRBP, Employee Engagement, Onboarding, HRMS, Payroll, Performance Management, PMS, Naukri RMS, LinkedIn Recruiter, Workday, SuccessFactors, Compensation and Benefits, Exit Formalities, Labour Law Compliance.
The two that move Indian HR shortlists most reliably are the named systems, so if you have used Workday or SuccessFactors, put it in the skills line rather than burying it in a bullet.
Sales and business development
The pool: B2B Sales, Inside Sales, Field Sales, Lead Generation, Cold Calling, Pipeline Management, Salesforce, HubSpot, Zoho CRM, CRM, Account Management, Key Account Management, Client Retention, Upselling, Cross-selling, Target Achievement, Quota, Channel Sales, Distributor Management, SaaS Sales, Enterprise Sales, Revenue Growth.
Sales is the one family where numbers beat vocabulary. “Achieved 118% of a ₹4 crore annual target” outperforms any keyword you could add next to it, because it is the only line a sales recruiter reads twice.
Finance and accounts
The pool: Accounts Payable, Accounts Receivable, General Ledger, Bank Reconciliation, GST, TDS, Income Tax, Statutory Compliance, Financial Reporting, Balance Sheet, P&L, Budgeting, Forecasting, Variance Analysis, Tally ERP, SAP FICO, Oracle Financials, Advanced Excel, Internal Audit, Statutory Audit, Ind AS, IFRS, CA, CMA, MBA Finance.
Indian finance JDs filter on the compliance terms far more than on the soft ones. GST and TDS are close to mandatory keywords for domestic roles, and they are the first thing missing from resumes written for an international template.
Digital marketing
The pool: SEO, SEM, Google Ads, Meta Ads, PPC, Performance Marketing, Google Analytics, GA4, Google Tag Manager, Keyword Research, On-Page SEO, Off-Page SEO, Link Building, Content Marketing, Email Marketing, Marketing Automation, HubSpot, Social Media Marketing, Conversion Rate Optimization, CRO, ROAS, CAC, Campaign Management.
Note the acronym pairs. Recruiters search “CRO” and “Conversion Rate Optimization” at different rates, so spell it out once and use the acronym once. That is not stuffing, it is coverage.
Customer support and operations
The pool: Customer Support, Customer Service, Voice Process, Non-Voice Process, Chat Support, Email Support, International BPO, Domestic BPO, Zendesk, Freshdesk, Salesforce Service Cloud, CRM, Ticketing, SLA, CSAT, NPS, First Call Resolution, Escalation Management, Query Resolution, Shift Flexibility.
Voice versus non-voice is a genuine hard filter in Indian support hiring. If your resume does not say which one you did, you drop out of both searches.
Freshers and entry level
Freshers have the opposite problem: not enough real terms, so the temptation is to pad. Do not. The pool that actually works is small: your degree and branch written in full (B.Tech Computer Science, B.Com, MBA Marketing), your core technical skills, your internship with the company name, your project titles with the stack named, plus Git, SQL, Excel or whatever your branch expects, and any certification by its exact name (AWS Certified Cloud Practitioner, Google Data Analytics Certificate).
The single highest-value fresher keyword is the branch spelled out, because recruiters filter campus hiring by branch before they filter by anything else. There is more on this in ATS score for freshers and resume for freshers with no experience.
The keywords recruiters actually search
Worth understanding the other side of the screen, because it explains why the list above is ordered the way it is.
A recruiter on Naukri does not read resumes. They open resume search, type a skill, add an experience range, add a location, sometimes add a notice period and a CTC band, and get a list sorted with recent profiles near the top. Then they open maybe the first twenty.
Three consequences, and they are the whole game:
- Skills get searched as tags, not as prose. A skill named only inside a paragraph in your summary matches less reliably than the same skill in a skills line.
- Titles are searched as often as skills. “SDET”, “HRBP”, “Key Account Manager” are searched directly. If your official designation was something internal like “Engineer II”, add the market-standard title next to it.
- Certifications are searched by their exact name. “AWS Certified Solutions Architect” matches. “AWS certification” does not.
That last one costs people interviews quietly, every week.
How to cut the pool down to your list
Here is the part I actually believe: the list above is a starting pool, not a resume. Copying twenty terms out of it is how you end up with a resume that matches everything and convinces nobody.
The cut:
- Pull up five to ten current postings for the exact role and seniority you are targeting, in your city or the cities you would move to.
- Write down every skill, tool, framework and title mentioned.
- Keep everything that appears in more than half of them. That is your list.
- Drop anything you cannot talk about for two minutes in an interview.
The half-of-postings rule matters. A term appearing once is one hiring manager’s preference. A term appearing in six out of ten is what the market is filtering on.
Step 4 is not optional, whatever the internet says. Every term on your resume is a question you have agreed to answer.
Where to put them so they parse
| Location | Does it parse? | Worth using |
|---|---|---|
| Plain-text skills section | Yes | Yes, this is the primary place |
| Inside dated role bullet points | Yes | Yes, this is where it becomes evidence |
| Resume headline or title line | Yes | Yes, one or two core terms |
| Header or footer | Often skipped | No |
| Inside an image, chart, or skill bar | No | No |
| Text box or sidebar in a two-column layout | Unreliable | No |
| White text hidden on the page | Extractable but detectable | No, this gets resumes rejected |
The pairing that works is a skills line for coverage plus the same term inside a bullet point with a number attached: “Migrated 40 services to Kubernetes, cutting deploy time 35%”. The skills line makes you findable. The bullet makes you credible.
Two placement questions come up constantly:
Keywords for the skills section. Write them as a comma-separated plain-text list, grouped loosely (languages, then frameworks, then tools, then cloud). Skip the skill bars and the five-star ratings. They parse as nothing, and no recruiter has ever believed a four-out-of-five in Python.
Personal details and soft skills. Name, email, phone and city belong in plain text at the top, not in a header, because contact parsing is the single most common thing a checker flags. Soft skills like “communication” and “leadership” are almost never filtered on, so they cost space and earn nothing. One line at most, and only if the JD names them.
Why stuffing fails
Two reasons, and neither is that a machine punishes you.
First, the machine hands you to a human. A recruiter reading a paragraph of forty unconnected tools cannot tell what you actually did, so they move to the next resume. The parse succeeded and the application still died.
Second, repetition is mostly not measured. Systems generally care whether a term is present and where it sits, not how many times you managed to fit it in. Saying Python nine times gets you the same match as saying it twice, at the cost of a resume nobody wants to read.
The version that genuinely backfires is white text and hidden keyword blocks. Parsers extract them and the text is trivially visible the moment anyone selects the page or opens the parsed view. It reads as an attempt to game the process, which is a much worse first impression than a missing skill.
How many keywords is enough
Eight to fifteen distinct skills for a technical resume. Six to ten for non-technical. That is not a rule from a spec sheet, it is just what fits in a skills line plus a set of bullets without the page turning into a tag cloud.
If your list runs longer, the problem is usually that you are targeting three different roles with one resume. Two focused versions beat one that covers everything.
Tailoring per job, without rewriting everything
Full rewrites per application are not sustainable, and they are not necessary. Keep one strong base resume that covers the repeated terms for your role. Then, for roles you genuinely care about, adjust two things only: the skills line order, so the posting’s core requirement sits first, and one bullet point that speaks directly to the main responsibility named in the posting.
That is a ten-minute edit rather than an evening, which matters because the number of applications you send has more effect on outcomes than the polish of any single one.
Rule of thumb: if a term is in more than half your target postings and you could be interviewed on it, it belongs in your skills line and in one bullet. Everything else is decoration.
A checker will confirm your skills are being read at all: run your resume through the free checker and look at the skills check specifically. For what the resulting number means, see what is a good ATS score and the full ATS score explainer. For the wider fix list beyond keywords, see how to make your resume ATS-friendly.
ApplyCove reads each job description before applying and answers screening questions for you, on Naukri and LinkedIn, up to 200 applications a day by plan. From Rs 349/month with a free plan always available. See how it works.