Updated May 17, 2026
You have one resume. Nine portals. The temptation is to upload the same PDF everywhere and call it done.
That works poorly. Not because each portal needs a completely different document. They do not, but because each platform reads your resume differently, weights different fields, and surfaces different information to recruiters. Knowing what each one looks at changes where you spend your optimisation effort. Start with which job portal to use in India if you have not picked your primary channels yet.
1
base resume
you need exactly one well-formatted PDF
3–4
platform-specific tweaks
per portal, not a full rewrite
90%+
profile completeness
threshold that matters on Naukri and LinkedIn
Run your resume through a free ATS check first. Every portal has an ATS layer. A resume that fails basic parsing fails on all nine platforms simultaneously.
The base resume: what every platform needs
Before thinking about per-platform adjustments, the base document needs to be right. One failure here breaks everything downstream.
Use a text-based PDF. Single column. Standard section headers: Experience, Education, Skills, Certifications. No tables, no text boxes, no headers/footers with critical information. No images or graphics. This format parses correctly on Naukri, Hirist, Indeed, Shine, and TimesJobs. Deviating from it causes misparsing on at least three of the five.
Every platform uses your uploaded resume to auto-fill profile fields. If the PDF misparses, your profile shows wrong data. The problem is invisible, you see a complete profile, the recruiter sees a profile with your company listed as "2019-2023" or your designation listed as blank.
After uploading to any portal, manually verify these fields: current designation, current company, employment dates, education institution and degree, and skills extracted.
Platform-by-platform: what to adjust
Naukri
What it reads: Headline, skills section, current designation, expected salary, location.
What to do beyond the PDF:
- Write a keyword-rich headline manually. Do not accept the default extracted one
- Add skills that appear in your target JDs to the skills section, the PDF extraction misses many of them
- Fill in current and expected salary, blank salary fields make you invisible to salary-filtered searches
- Update the profile every 7-10 days to reset the freshness signal
→ Naukri profile optimization guide
What it reads: Headline, About section, experience bullets, skills, engagement activity.
What to do beyond the PDF:
- LinkedIn does not use your uploaded PDF for ranking. The on-profile text is what gets indexed
- Rewrite your experience bullets in LinkedIn directly, separate from the PDF with more detail, outcome language, numbers
- Write an About section in first person (not a resume summary)
- The PDF download is for recruiters who want to share your profile internally. Make it clean, but it is not the primary matching document
→ LinkedIn job search India guide
Instahyre
What it reads: Current employer, GitHub link, tech stack specificity, project outcomes.
What to do:
- Instahyre does not primarily use your PDF. It builds a structured profile
- Add GitHub link and pin relevant repos
- Replace generic skill tags with version-specific ones in the profile directly
- Write project outcomes with metrics in the project descriptions
The PDF here is a reference document, not the matching signal.
Hirist
What it reads: Standard resume fields, skills section, experience.
What to do:
- Use exactly the format described in the base resume section, Hirist's parser is basic
- List skills as a comma-separated block, not embedded in experience bullets only
- Standard headers are non-negotiable, "Where I've Worked" breaks the parser, "Experience" does not
Hirist is the most format-sensitive portal. A beautifully designed resume with custom headers will parse worse here than a plain text PDF.
Indeed India
What it reads: PDF for initial match, but the Indeed Resume Builder for the Job Match Score.
What to do:
- Complete the Indeed Resume Builder separately from your PDF upload. That feeds the match scoring algorithm
- Fill in both the PDF upload and the builder for full match score coverage
- Add skills manually in the builder. Do not rely on extraction
- Complete the Skills Assessments for your primary hard skill if available
→ Indeed India job search guide
Shine
What it reads: Smart Profile extracted fields, industry, location, salary.
What to do:
- Shine's Smart Profile auto-extracts from your PDF. Always verify every field manually after upload
- Set industry and functional area manually. The extraction is unreliable for these fields
- Set specific location, not just city. Area and zone matter for matching
- Turn on push notifications for job alerts. Shine's best roles move fast
TimesJobs
What it reads: Standard resume fields, domain/industry classification.
What to do:
- Standard format PDF, nothing special
- Manually set your domain and industry after upload. That is the primary matching filter
- Update your profile when you update your other portals. Treat it as part of the same cycle
TimesJobs requires the least platform-specific effort. Format correctly, set domain, stay active.
Job Hai and WorkIndia
What it reads: Location, availability, category, verification status, not a resume.
What to do:
- No PDF upload, profile is built through app forms.
- Set location to specific area (not just city)
- Verify phone number (mandatory on WorkIndia)
- Set availability and shift preference accurately
- Record the video introduction on Job Hai (fewer than 10% of candidates do)
Resume format is irrelevant here. These platforms do not use it.
For management and premium roles, also see the iimjobs guide.
The update cycle: doing this without losing your mind
Nine platforms updated separately is not a realistic workflow. Here is how to make it manageable:
One base document, maintained in one place
Keep a single master resume file. When you update it, that is the source of truth. Every portal gets a fresh export from this file, not separate versions that drift apart.
Group your portals into two update cycles
Traditional portals (Naukri, Indeed, Shine, TimesJobs): update once every 7-10 days, even a minor field change resets freshness. LinkedIn: update when you add a real achievement. Instahyre and Hirist: update when your tech stack or projects change meaningfully.
Platform-specific fields live on the platform, not in the PDF
Your Naukri headline, LinkedIn About section, Instahyre project descriptions, Indeed Resume Builder. These are not in your PDF. They are maintained directly on each platform. Treat them as separate documents that reference your core experience but are optimised for each platform's algorithm.
Verify parsed fields after every upload
Every time you upload a new version of your PDF to any portal, manually check that current designation, company, dates, and education parsed correctly. This takes two minutes and catches misparsing before a recruiter sees wrong data.
What stays the same everywhere
Regardless of platform, five things are consistent:
- Text-based PDF (no exceptions)
- Outcome language in experience bullets: percentages, revenue, scale, users
- Specific skills, not generic: "React 18 + TypeScript" not "ReactJS"
- Complete salary fields: blank salary fields hurt visibility on Naukri, Shine, and Indeed
- Active profile: updating regularly outperforms a static profile on every traditional portal
The per-platform adjustments are real but they are not rewrites. The base document is the same. What changes is the profile you build on top of it, and knowing which layer each platform actually reads.
One well-formatted resume, maintained in one place, uploaded to the right two or three portals with the right platform-specific fields filled in. That is the whole system. Everything else is noise.
Use the JD matching tool to check how well your resume keywords align with the specific roles you are targeting before you upload anywhere.
How does ResumeGrade compare?
